User's Guide

NOTE: Some of the control script variables, such as VG and LV, on the target disk site must
be the same as on the source disk site. Some of the control script variables, such as, FS,
SERVICE_NAME, SERVICE_CMD and SERVICE_RESTART are probably the same as on the
source disk site. Some of the control script variables, such as IP and SUBNET, on the target
disk site are probably different from those on the source disk site. Make sure that you review
all the variables accordingly.
5. Add customer-defined run and halt commands in the appropriate places according to the
needs of the application. See the Managing Serviceguard user’s guide for more information
on these functions.
6. Copy the environment file template /opt/cmcluster/toolkit/SGCA/
xpca.env to the package directory, naming it pkgname_xpca.env.
# cp /opt/cmcluster/toolkit/SGCA/xpca.env \
/etc/cmcluster/pkgname/pkgname_xpca.env
7. Edit the environment file <pkgname>_xpca.env as follows:
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 you are 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 Continentalclusters/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.
204 Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access for P9000 and XP