The procedures in this section are designed for the Multi-Site/Active-Active topology ONLY. Do NOT use these procedures for Composite Active/Active Clustering uing v6 onwards.
For version 6.x onwards, Composite Active/Active Clustering, please refer to Section 3.4, “Deploying Composite Active/Active Clusters”
To add an entirely new cluster (dataservice) to the mesh, follow the below simple procedure.
There is no need to set the Replicator starting points, and no downtime/maintenance window is required!
Choose a cluster to take a node backup from:
Choose a cluster and Replica node to take a backup from.
Enable maintenance mode for the cluster:
shell>cctrlcctrl>set policy maintenance
Shun the selected Replica node and stop both local and cross-site replicator services:
shell>cctrlcctrl>datasource {replica_hostname_here} shunreplica shell>trepctl offlinereplica shell>replicator stopreplica shell>mm_trepctl offlinereplica; shell>mm_replicator stop
Take a backup of the shunned node, then copy to/restore on all nodes in the new cluster.
Recover the Replica node and put cluster back into automatic mode:
replica shell>replicator startreplica shell>trepctl onlinereplica shell>mm_replicator startreplica shell>mm_trepctl onlineshell>cctrlcctrl>datasource {replica_hostname_here} onlinecctrl>set policy automatic
On ALL nodes in all three (3) clusters, ensure the
/etc/tungsten/tungsten.ini has all three clusters
defined and all the correct cross-site combinations.
Install the Tungsten Clustering software on new cluster nodes to create a single standalone cluster and check the cctrl command to be sure the new cluster is fully online.
Install the Tungsten Replicator software on all new cluster nodes and start it.
Replication will now be flowing INTO the new cluster from the original two.
On the original two clusters, run tools/tpm update from the cross-site replicator staging software path:
shell>mm_tpm query stagingshell>cd {replicator_staging_directory}shell>tools/tpm update --replace-releaseshell>mm_trepctl onlineshell>mm_trepctl services
Check the output from the mm_trepctl services command output above to confirm the new service appears and is online.
There is no need to set the cross-site replicators at a starting position because:
Replicator feeds from the new cluster to the old clusters start at seqno 0.
The tungsten_olda and tungsten_oldb database schemas will contain the correct starting points for the INBOUND feed into the new cluster, so when the cross-site replicators are started and brought online they will read from the tracking table and carry on correctly from the stored position.