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

Cascading Failover in a Continental Cluster
Data Storage Setup
Chapter 8374
c. Use the following command to check the data synchronization
from the BCV/R1 devices to the R2 devices. If the “RDF Pair
STATE” column shows the state “Synchronized” for all the
devices, the copying completed.
# symrdf -g <prisymdevgrpname> query -rbc
d. Once the copy completes, split the SRDF link between the
secondary Symmetrix and the recovery Symmetrix:
# symrdf -g <prisymdevgrpname> split -rbcv
e. Fully establish the BCV devices in the recovery Symmetrix as
mirrors of the standard devices:
# symmir -f <bcvdev_textfile> -sid <recsymid> -full
est
The <bcvdev_textfile> is a file that contains a list of the standard
device and BCV device pair in the recovery Symmetrix.
f. Re-establish the BCV/R1 devices to the mirror group as a mirror
of the standard device. This would make the devices invisible to
the systems so the vgimport would work properly. Use the
command:
# symmir -f <prisymdevgrpname> est -rdf
5. Generate a map file by exporting the VGs on the node that was used
to create the VGs without removing the special device files. Uses the
commands:
# vgchange -a n <vgname>
# vgexport -s -p -m <mapfilename <vgname>
Make sure to copy the mapfiles to all of the host systems.
6. Import the VGs on all of the other systems that might run the
MC/ServiceGuard package and back up the LVM configuration. Do
this on both the primary and recovery cluster nodes. Make sure the
SRDF link between the primary Symmetrix and the secondary
Symmetrix is split before importing the VGs.
Use the following commands:
# symrdf -g <prisymdevgrpname> split -v
# vgimport -s -m <mapfilename> <vgname>
# vgchange -a y <vgname>