Building Disaster Recovery Serviceguard Solutions Using Metrocluster with EMC SRDF

avoid contention when more than one package is starting on a node. RETRY * RETRYTIME
must be approximately five minutes to keep package startup time under 5 minutes.
RETRYRETRYTIME
60 attempts5 secondspkgA
43 attempts7 secondspkgB
33 attempts9 secondspkgC
g. Uncomment the CLUSTER_TYPE variable and set it to metro. (The value continental
is only for use with the Continentalclusters product.
h. If using an M by N configuration, be sure that the variable CONSISTENCYGROUPS is set
to 1 in the environment file.
CONSISTENCYGROUPS=1
9. Distribute Metrocluster with EMC SRDF configuration, environment, and control script files to
other nodes in the cluster by using ftp, rcp, or scp:
# rcp -p /etc/cmcluster/pkgname/* \
other_node:/etc/cmcluster/pkgname
See the example script Samples/ftpit to see how to semi-automate the copy using ftp.
This script assumes the package directories already exist on all the nodes.
Using ftp might be preferable in your organization, since it does not require the use of
a.rhosts file for root. Root access via .rhosts can create a security issue.
10. Verify that each node in the Serviceguard cluster has the following files in the directory
/etc/cmcluster/pkgname:
pkgname.cntl Serviceguard package control script
pkgname_srdf.env Metrocluster EMC SRDF environment file
pkgname.ascii Serviceguard package ASCII configuration file
pkgname.sh Package monitor shell script, if applicable
other files Any other scripts that you use to manage Serviceguard packages
The Serviceguard cluster is ready to automatically switch packages to nodes in remote data
centers using Metrocluster/SRDF.
11. Verify the configuration using the cmcheckconf -P package_name.ascii, then apply
the Serviceguard configuration using the cmapplyconf -P package_name.ascii
command or SAM.
12. Restore the SRDF logical links for the disks associated with the application package. See the
script Samples/post.cmapply for an example of how to automate this task. The script
must be customized with the Symmetrix device group names. Redirect the output of this script
to a file for debugging purposes.
Migrating legacy packages to modular packages using Metrocluster with
EMC SRDF A.09.00 or later
To get the benefits of Modular style packages, existing Legacy Metrocluster packages can be
migrated to use the modular style. However, the migration steps vary based on the HP Serviceguard
version and the Legacy package configuration. While completing the migration procedure, multiple
package configuration files are created. Only the final package configuration file that is created
at the end of the procedure must be applied.
To migrate Legacy packages to Modular packages using Metrocluster with SRDF A.09.00 or later:
1. Create a Modular package configuration file for the Metrocluster Legacy package.
# cmmigratepkg -p <package_name> [-s] -o <modular_sg.conf>
Migrating legacy packages to modular packages using Metrocluster with EMC SRDF A.09.00 or later 93