Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access for P9000 and XP A.11.00

NOTE: If you do not use a package name as a filename for the package control script, you
must follow the convention of the environment file name. This is the combination of the file
name of the package control script without the file extension, an underscore and type of the
data replication technology (xpca) used. The extension of the file must be env. The following
examples demonstrate how the environment file name must be chosen.
For example,
If the file name of the control script is pkg.cntl, the environment file name is pkg_xpca.env.
For example,
If the file name of the control script is control_script.sh, the environment file name is
control_script_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.
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 every 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 metro for Metrocluster .
8. After customizing the control script file and creating the environment file, and before starting
up the package, do a syntax verify on the control script using the following command (be sure
to include the -n option to perform syntax verifying only):
# sh -n <pkgname.cntl>
If any messages are returned, you must correct the syntax errors.
9. Verify the configuration using the cmcheckconf -P <pkgname>.config, then apply the
Serviceguard configuration using the cmapplyconf -P <pkgname>.config command
or SAM.
10. 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.
174 Legacy packages