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

Cascading Failover in a Continental Cluster
Data Replication Procedures
Chapter 8394
12. Start the application package at the secondary site. Issue the
following command for all hosts in secondary site that may run this
package:
# cmmodpkg -e -n <host_name> <package_name>
Then issue the following command from any node on the primary
cluster:
# cmmodpkg -e <package_name>
13. Start the ContinentalClusters monitor package.
Refer to the sample script recrestoresec in the
/opt/cmcluster/toolkit/SGSRDF/cascade/Samples directory for the
automation of step 3 to step 10. This script is designed to run only on a
node that connects to the secondary Symmetrix.
Data Restore and Failback from the Recovery Site Directly to
the Primary Site in the Primary Cluster
This procedure is used in situation where both the secondary site and the
primary site are fixed and up and running. The package application fails
back directly from the Recover cluster to the primary site in the primary
cluster.
1. Halt the ContinentalClusters monitor package at the recovery site.
2. Halt the ContinentalClusters recovery packages at the recovery site.
3. Split the BCV/R1 from the mirror group if it's not already in the split
state. Use the following command if run on a host that connects to
the recovery Symmetrix:
# symmir -f <secbcvdev_textfile> -sid <secsymid> split
The <secbcvdev_textfile> is a file that contains a list of the standard
device and BCV/R1 device pairs in the secondary Symmetrix.
Use the following command if run on a host that connects to the
secondary Symmetrix:
# symmir -g <secsymdevgrpname> split
4. Re-establish the RDF volume pairs between the recovery Symmetrix
and the secondary Symmetrix. Restore the data from the recovery
Symmetrix and the secondary Symmetrix. Use the following
command if run on a host that connects to the recovery Symmetrix:
# symrdf -g <recsymdevgrpname> -full restore