2.5 Responsibilities of MultiSite Administrators

A MultiSite administrator must do the following:

• Help determine and implement the ClearCase and MultiSite use models

When a new project is set up, the administrator works with project managers to determine which replicas master various objects. The administrator also changes mastership when necessary, schedules merges, copies triggers from replica to replica, and monitors label creation.

• Monitor MultiSite synchronization and replica creation

Administrators must check the storage bays to make sure that packets are not accumulating. On UNIX, include the administrator's e-mail address in the ADMINISTRATOR entry in the shipping.conf file. On Windows, include the administrator's e-mail address in the MultiSite Control Panel.

It is important to prevent two or more replicas of the same VOB from being mounted on the same host-one host can belong to only one region and each region can contain only one replica. Accordingly, do not assign public VOB-tags in the same ClearCase registry region to multiple replicas of the same VOB.

See VOB Objects and Replica Objects for information about how VOBs and VOB replicas are listed in the ClearCase storage registry and Chapter 12, Using MultiSite for Interoperability for information about using multiple replicas at one site.

• Monitor ClearCase and system log files

Error and status messages are written to the shipping_server_log file and (on Windows) the Event Viewer. For more information about error logs, see Troubleshooting Tips.

• Install new versions of ClearCase and MultiSite and new patches

Patches and information about new versions are available on the Rational Software Web site. Install the Mandatory and Recommended patches for your architecture.

Compatibility issues for versions of ClearCase and MultiSite are described in the Release Notes for Rational ClearCase and ClearCase MultiSite.

• Coordinate issues with all other MultiSite administrators responsible for replicas in the VOB family

After initial setup and synchronization of replicas, administrators also must coordinate recovery efforts, which may involve exchanges of update packets, and changes of mastership, which require the administrator at the master replica to transfer mastership to the replica that needs to master the objects.

We recommend that you create a representation of your MultiSite deployment. For example, Figure 17 shows information and the synchronization pattern for a VOB family.

Figure 17 VOB Family Information

• Ensure that VOB replicas receive any necessary special handling

Restoring a VOB replica's storage directory from backup is a significant event in the life of a VOB family. Failure to follow the procedure described in the section Restoring a Replica from Backup leads to irreparable inconsistencies among the VOB's replicas.

There are no special requirements for backing up a VOB replica's storage directory. Use the instructions in the Administrator's Guide for Rational ClearCase for backing up a VOB.

Other ClearCase administrative procedures require special steps for replicated VOBs. The procedures in the Administrator's Guide for Rational ClearCase describe these steps.