Designing Disaster Recovery Clusters using Metroclusters and Continentalclusters, Reprinted October 2011 (5900-1881)

a. If necessary, add the path where the Raid Manager software binaries have been installed
to the PATH environment variable. If the software is in the usual location, /usr/bin,
you can just uncomment the line in the script.
b. Uncomment the behavioral configuration environment variables starting with AUTO_. It
is recommended that you retain the default values of these variables unless you have a
specific business requirement to change them. See Appendix A for an explanation of
these variables.
c. Uncomment the PKGDIR variable and set it to the full path name of the directory where
the control script has been placed. This directory, which is used for status data files, must
be unique for each package. For example, set PKGDIR
to/etc/cmcluster/package_name, removing any quotes around the file names.
d. Uncomment the DEVICE_GROUP variable and set it to this package’s Raid Manager
device group name, as specified in the Raid Manager configuration file.
e. Uncomment the HORCMPERM variable and use the default value MGRNOINST if Raid
Manager protection facility is not used or disabled. If Raid Manager protection facility
is enabled set it to the name of the HORCM permission file.
f. Uncomment the HORCMINST variable and set it to the Raid Manager instance name used
by Metrocluster/Continuous Access.
g. Uncomment the FENCE variable and set it to either ASYNC, NEVER, or DATA according
to your business requirements or special Metrocluster requirements. This variable is used
to compare with the actual fence level returned by the array.
h. If using asynchronous data replication, set the HORCTIMEOUT variable to a value greater
than the side file timeout value configured with the Service Processor (SVP), but less than
the RUN_SCRIPT_TIMEOUT set in the package configuration file. The default setting is
the side file timeout value + 60 seconds.
i. Uncomment the CLUSTER_TYPE variable and set it to continental.
8. Distribute Metrocluster/Continuous Access 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 nodes.
Using ftp may be preferable at your organization, since it does not require the use of
a.rhosts file for root. Root access via .rhosts may create a security issue.
9. Verify that each node in the Serviceguard cluster has the following files in the directory
/etc/cmcluster/pkgname:
pkgname.cntl Metrocluster/Continuous Access package control script
pkgname_xpca.env Metrocluster/Continuous Access environment file
pkgname.ascii Serviceguard package ASCII configuration file
pkgname.sh Package monitor shell script, if applicable
other files Any other scripts you use to manage Serviceguard packages.
The Serviceguard cluster is ready to automatically switch packages to nodes in remote data
centers using Metrocluster/Continuous Access.
10. Apply the Serviceguard configuration using the cmapplyconf command or SAM.
11. Edit the file /etc/rc.config.d/raidmgr, specifying the Raid Manager instance to be
used for Continentalclusters, and specify the instance is to be started at boot time.
The appropriate Raid Manager instance used by Continentalclusters must be running before
the package is started. This normally means the Raid Manager instance must be started before
starting Serviceguard.
202 Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access for P9000 and XP