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

Cascading Failover in a Continental Cluster
Data Replication Procedures
Chapter 8396
9. Once the data restore completed, split the BCV/R1 devices from the
mirror group. From a host that connects to the recovery Symmetrix:
# symmir -f <secbcvdev_textfile> -sid <secsymid> split
From a host that connects to the secondary Symmetrix:
# symmir -g <secsymdevgrpname> split
10. Set the RDF pairs between primary Symmetrix and secondary
Symmetrix to fail over state. Run the following command on a host
that connects to the secondary Symmetrix:
# symrdf -g <secsymdevgrpname> failover -force
11. Since the recovery cluster has a different cluster ID, the data restore
from the recovery Symmetrix to the secondary Symmetrix also copies
the recovery cluster’s ID to the secondary Symmetrix. Do the
following to change the cluster’s ID on each cluster aware volume
group in the secondary Symmetrix before starting the application
package:
# vgchange -c n /dev/<vg_name>
# vgchange -c y /dev/<vg_name>
12. Start the package application at the primary site. Issue the following
command for all hosts in the primary cluster that may run this
package:
# cmmodpkg -e -n <host_name> <package_name>
Start the package with the following command:
# cmmodpkg -e <package_name>
13. Start the ContinentalClusters monitor package on the recovery
cluster.
14. Use the following command to check the RDF pair state between the
R1 devices in the primary Symmetrix to the R2 devices in the
secondary Symmetrix. From a host that connects to the secondary
Symmetrix:
# symrdf -g <secsymdevgrpname> query
From a host that connects to the primary Symmetrix:
# symrdf -g <prisymdevgrpname> query