Sustaining a smoothly functioning MultiSite environment requires
dedicated administration. Many administrative processes can drastically change
your environment and require careful consideration and planning.
Rename replicas and sites
To change the name of a database replica, you must delete
the replica and create a new replica using a different name. Renaming
sites requires planning and coordination between sites in the clan,
particularly the site that is designated for renaming and the working
master site. Synchronize all sites before renaming.
Moving a replica or changing vendor database software
Moving a replica or changing vendor database software involves
the same tasks that must be performed on a non-replicated Rational® ClearQuest® database set. The additional
step for replicated database sets is to synchronize all sibling replicas
once the move process is complete.
Moving or renaming a synchronization server
You can change the synchronization server associated with
a replica when, for example, the machine you are using has a hardware
failure, or you must rename the existing synchronization server. You
must update the properties of the replica associated with that host
so that the store-and-forward facility can determine how to route
updates to the replicas.
Replica deletion
To remove a replica, you must complete all the necessary
steps; if you do not, synchronization and mastership problems can occur in
other replicas in the family.
Upgrading a schema version
This procedure describes how to introduce a new schema version
to a Rational ClearQuest MultiSite
clan by synchronizing the new schema to all sites before upgrading any user
databases. You must follow this procedure to help ensure a stable and reliable Rational ClearQuest MultiSite
environment.
Database record ID management
Database record IDs are allocated to replicas in ID blocks. The
range of record IDs (for both stateful and stateless records) is broken into
blocks that are assigned to each replica to be allocated locally within those
replicas.