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

Building a Metropolitan Cluster Using MetroCluster/CA
Preparing an MC/ServiceGuard Cluster for MetroCluster /CA
Chapter 3 103
Make sure that you copy the map files to all of the nodes. The sample
script Samples/ftpit shows a semi-automated way (using ftp) to
copy the files. You need only enter the password interactively.
Importing Volume Groups on Other Nodes
Use the following procedure to import volume groups. The sample script
mk2imports can be modified to automate these steps.
1. Split the Raid Manager device groups to enable read/write on the
SVOL before doing the import by using the following command:
# pairsplit -g devicegroupname -rw
2. Import the VGs on all of the other systems that will run the
MC/ServiceGuard package, and back up the configuration. Use the
following command:
# vgimport -v -s -m mapfilename vgname
3. Back up the configuration. Use the following commands:
# vgchange -a y vgname
# vgcfgbackup vgname
# vgchange -a n vgname
See the sample script Samples/mk2imports.
4. Resynchronize the CA pair device. Use the following commands:
# pairresync -g devicegroupname -c 15
NOTE Exclusive activation must be used for all volume groups associated with
packages that use the XP Series disk array. The design of
MetroCluster/CA assumes that only one system in the cluster will have a
VG activated at a time.
Configuring PV Links
The examples in the previous sections show the use of the vgimport and
vgexport commands with the -s option. Also, the mk1VGs script uses a -s
in the vgexport command, and the mk2imports script uses a -s in the
vgimport command. You may wish to remove this option from both