Using the CLI and native GUIs
You can use the command line or the native DevOps Code ClearCase® and MultiSite GUIs to administer replicas.
- Displaying properties of a VOB replica
You can display properties of a VOB replica using the describe command or the ClearCase Properties Browser. - Listing the synchronization history of a VOB replica
The lshistory command and the History Browser (lshistory –graphical) list the synchronization history of a replica. - Changing preservation mode for a VOB family
You can change the preservation mode of a replica using the chreplica command. - Changing the host name for a VOB replica
You can use the chreplica command (or the Property Browser on Windows) to change the host name for a VOB replica. - Setting the connectivity property for a VOB replica
To indicate whether a sibling replica has IP connectivity to your current replica, use the chreplica command with the –isconnected or –nconnected option. - Renaming a VOB replica
You can change the name of a VOB replica using either the cleartool rename command or the DevOps Code ClearCase Properties Browser. - Moving a VOB replica
Moving a VOB replica is similar to moving an unreplicated VOB. However, there are special considerations when you move a replicated VOB. - Changing mastership of a VOB replica
You can use the chmaster command to change the mastership of a VOB replica. - Deleting a replica
This topic describes how to remove a replica. You must complete all steps; if you do not, synchronization and mastership problems can occur in other replicas in the family. When you remove a replica, the replicas in its family stop tracking epoch numbers for that replica. Removing a replica does not delete the VOB database or Rational® ClearQuest® database it replicates. Removing a replica requires two synchronization cycles: one to transfer mastership of all of the replica's objects to another replica, and one to inform all other replicas that the removed replica is no longer participating in the update process. Because this information can be communicated only through the synchronization process, you cannot remove a replica at its own site, because doing so prevents the replica from creating update packets. After a replica is removed from a family, it no longer participates in synchronization activities. The replica no longer updates its oplog, and you cannot transfer mastership of any object in that replica.
Parent topic: Administering replicas