Disaster recovery rehearsal in Continentalclusters

4. Prepare the replication environment for DR rehearsal:

a) In case of a 3DC CAJ/CAJ Tri-Link configuration using Delta Resync, delete the Delta Resync

pair from a node in the recovery cluster. Otherwise, go to step b:

# pairsplit –g <Delta Resync-pair> -R

b) Manually suspend the Active-CAJ pair and enable write access to recovery disk at the

recovery cluster:

# pairsplit -g <Active-CAJ-pair> -rw -P

c) 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

recovery 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

recovery cluster to change the cluster ID:

# vgchange -c n -S n <vg_name>

# vgchange -c y -S y <vg_name>

d) Split the business copy pair at recovery cluster, if configured for the Active-CAJ pair:

# export HORCC_MRCF=1

# pairsplit -g <Active-CAJ-pair>

# unset HORCC_MRCF

5. Start the rehearsal:

# cmrecovercl -r -g <recovery_group>

Verify that the rehearsal package starts up successfully in the recovery cluster using cmviewcl.

Note: Before starting rehearsal, make any application configuration required due to change in the client access

IP address which is now the rehearsal package IP address.

6. Stop rehearsal package:

# cmhaltpkg <rehearsal_package>

7. Restore replication environment for recovery:

a) Resume replication from the primary cluster to the recovery cluster.

Run the following commands from DC3 node to re-synchronize the recovery

cluster disk array and resume the replication:

# pairresync –g <Active-CAJ-pair>

b) If Delta Resync pair is deleted as the part of step (4.a), Re-create the Delta Resync pair using

the paircreate command from DC3 node:

# paircreate -g <Delta Resync-pair> -vr –f async –jp

<Journal_id> -js <Journal-id> -nocsus