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”
In the event of a failure within one host in the service where you need to reprovision the host from another running Replica:
Identify the servers that are failed. All servers that are not the Primary for their region can be re-provisioned using a backup/restore of the Primary (see Section 6.10, “Creating a Backup” or using the tungsten_provision_slave script.
To re-provision an entire region, follow the steps below. The
east region is used in the
example statements below:
To prevent application servers from reading and writing to the failed service, place the Tungsten Connector offline within the failed region:
cctrl [east]> router * offline
On all servers in other regions
(west{1,2,3}):
shell>/opt/replicator/tungsten/tungsten-replicator/bin/trepctl -service east offlineshell>/opt/replicator/tungsten/tungsten-replicator/bin/trepctl -service east reset -all -y
On all servers in the failed region
(east{1,2,3}):
shell>/opt/replicator/tungsten/tungsten-replicator/bin/replicator stopshell>/opt/replicator/tungsten/tools/tpm resetshell>/opt/continuent/tungsten/tungsten-replicator/scripts/tungsten_provision_slave \ --direct --source=west1
Check that Tungsten Cluster is working correctly and all hosts are up to date:
cctrl [east]> lsRestart the Tungsten Replicator service:
shell> /opt/replicator/tungsten/tungsten-replicator/bin/replicator start
On all servers in other regions
(west{1,2,3}):
shell> /opt/replicator/tungsten/tungsten-replicator/bin/trepctl -service east online