User's Guide

# vgchange -c n -S n <vg_name>
# vgchange -c y -S y <vg_name>
5. Start the recovery package on a DC3 node using the cmrunpkg command.
6. Verify that the application starts up successfully in the recovery cluster.
7. Halt the recovery package using the cmhaltpkg command.
8. Resume replication from the primary cluster to the recovery cluster. Run the following commands
from DC3 node to overwrite any changes on the recovery cluster disk array and resume the
replication:
# pairsplit -g <Active-CAJ-pair> -RB
# pairresync -g <Active-CAJ-pair> -c 15
These commands discard changes that were done at the recovery cluster and start synchronizing
the Continuous Access Journal group data.
9. If Delta Resync pair is deleted as part of Step 2, follow the below steps:
• Re-create the Delta Resync pair, if deleted in the step 1, using the paircreate
command from DC3 node:
# paircreate –g <Delta Resync-pair> -vr –f async –jp <Journal_id>
-js <Journal-id> -nocsus
• Assign Remote Command devices to journal volumes of Delta Resync pair using
Remote Web Console. For details on assigning remote command devices to journal
volumes, see “Assigning Remote Command Devices to Journal Volumes” (page 440).
10. Start the primary package in the primary cluster. When complex workloads are used, the Site
Controller package is started which brings up the corresponding complex workload stack in
DC1.
Testing Continentalclusters Recovery Using cmrecovercl in the Recovery Cluster
Complete the following procedure to test the recovery of the application using cmrecovercl in
the recovery cluster:
1. Halt the primary cluster using the cmhaltcl command.
2. This step is required only if you are using 3DC CAJ/CAJ Tri-Link configuration. Else, go to
step 3.
Delete the Delta Resync pair from DC3 node:
# pairsplit –g <Delta Resync-pair> -R
3. Split the Active-CAJ pair to make it read-write at the recovery cluster. For suspending replication,
split the Continuous Access journal device group pair, over which the replication is happening
to DC3 currently, using the pairsplit –RS command from a node in DC3:
# pairsplit –g <Active-CAJ-pair>-RS
4. Change the Cluster ID of all LVM and SLVM volume groups managed by the package. For
LVM volume groups, run the following commands from a node in the primary cluster to change
the cluster ID:
# vgchange -c n <vg_name>
# vgchange -c y <vg_name>
For SLVM volume groups, run the following commands from a node in the primary cluster to
change the cluster ID:
# vgchange -c n -S n <vg_name>
# vgchange -c y -S y <vg_name>
5. Wait until you receive the Continentalclusters alarm notification that the primary cluster is
DOWN and the recovery is enabled for the primary cluster. Use the cmviewconcl command
to check if the recovery is enabled for the primary cluster.
6. Run the cmrecovercl command:
Verifying the Three Data Center Environment 463