12.2 Special Considerations for Replicated VOBs

If you are moving a VOB replica to a new host, take the following steps first:

1. Make sure the replica masters its own replica object. For a replica named portland:

1. Check which replica has mastership of the portland replica object:

cleartool describe replica:portland@\libpub

...

master replica: west




2. If the replica object is not self-mastered, change its mastership. At the replica that masters the replica object:

multitool chmaster replica:portland@\libpub replica:portland@\libpub




This step is not mandatory, but it is generally recommended that all replicas master their own replica objects. (You can make this change at any time, as long as the replicas are synchronized.) For the purposes of moving a replica, this self-mastership prevents your team from having to diagnose and repair misdirected packet problems that may result after the move. If the replica object names the wrong host, packets are sent to that host. (If this happens, move misdirected packets to the correct host and then import them.)

2. Change the replica's host name property. After the last export from the replica's current location, use multitool chreplica to update the replica's host name. You must run this command from the site that masters the replica, which is the current site in most cases:

multitool chreplica -host target-host replica:portland@\libpub
Updated replica information for "portland".

NOTE: All replicas that export to the replica to be moved must be updated after the move through synchronizations from the moved replica's site (or from the site that executed the chreplica command in Step #2, if it was not the current site).