Designing Disaster Tolerant High Availability Clusters, 10th Edition, March 2003 (B7660-90013)

Physical Data Replication for ContinentalClusters Using EMC SRDF
Failback Scenarios
Chapter 7352
Dev RDev Typ:G SA RA LNK Mode Dom ACp Tracks Tracks Dev
RDev Pair
--- ---- ----- --------- ------------ ------ ------ ---
----------------
000 000 R2:2 RW WD RW SYN DIS OFF 0 0 WD
RW Synchronized
001 001 R2:2 RW WD RW SYN DIS OFF 2 0 WD
RW SyncInProg
9. Halt the recovery cluster and restart it:
# cmhaltcl -f (if not already down)
# cmruncl
10. Verify the data for data consistency and currency.
Scenario 2
The primary site Symmetrix experienced a catastrophic hardware failure
and all data was lost on the array.
After reception of the ContinentalClusters alerts and alarm, the
administrators at the recovery site follow prescribed processes and
recovery procedures to start the protected applications on the recovery
cluster. The ContinentalClusters control file will evaluate the status of
the Symmetrix SRDF paired volumes. Since the systems at the primary
site are accessible, but the Symmetrix is not, the control file will evaluate
the paired volumes with a local status of failed over. The control file
script is programmed to handle this condition and will enable the volume
groups, mount the logical volumes, assign floating IP addresses and start
any processes as coded into the script.
After the primary site Symmetrix is repaired and configured
appropriately use the following procedure to move the application
package back to the primary site.
1. Manually create the Symmetrix device groups and gatekeeper
configurations device groups. Rerun the scripts mk3symgrps* and
mk4gatekpr* which do the following:
# date >ftsys1.group.list
# symdg create -type RDF1 pkgCCA_r1
# symld -g pkgCCA_r1 add pd /dev/rdsk/c7t0d0