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

Cascading Failover in a Continental Cluster
Data Replication Procedures
Chapter 8 393
# symmir -g <secsymdevgrpname> -full restore
8. Use the following command to check the data restore from the
BCV/R1 devices in the R2 standard devices in the secondary
Symmetrix. If the “RDF Pair STATE” column shows the state
"Restored" for all the devices, the data restore completed. The
following shows the command if run on a host that connects to the
recovery Symmetrix:
# symmir -f <secbcvdev_textfile> -sid <secsymid> query
The following shows the command if run on a host that connects to
the secondary Symmetrix:
# symmir -g <secsymdevgrpname> query
9. Once the data restore completed, split the BCV/R1 devices from the
mirror group. The following shows the command if run on a host that
connects to the recovery Symmetrix:
# symmir -f <secbcvdev_textfile> -sid <secsymid> split
The following shows the command if run on a host that connects to
the secondary Symmetrix:
# symmir -g <secsymdevgrpname> split
10. Re-establish the BCV/R1 devices as mirrors of the standard devices.
The following shows the command if run on a host that connects to
the recovery Symmetrix:
# symmir -f <secbcvdev_textfile> -sid <secsymid> est
The following shows the command if run on a host that connects to
the secondary Symmetrix:
# symmir -g <secsymdevgrpname> est
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>