Building Disaster Recovery Serviceguard Solutions Using Metrocluster with EMC SRDF

The value of RUN_SCRIPT_TIMEOUT in the package ASCII file must be set to NO_TIMEOUT
or to a large enough value that takes into consideration the extra startup time because of
getting status from the Symmetrix.
4. Create a package control script.
# cmmakepkg -s pkgname.cntl
Customize the control script as appropriate to your application using the guidelines in the
Managing Serviceguard user’s guide. Standard Serviceguard package customizations include
modifying the VG, LV, FS, IP, SUBNET, SERVICE_NAME, SERVICE_CMD, and
SERVICE_RESTART parameters. Be sure to set LV_UMOUNT_COUNT to 1 or a value greater
than 1.
5. Add customer-defined run and halt commands in the appropriate places based on the
requirements of the application. For more information about these functions, see the Managing
Serviceguard user’s guide.
6. In the package_name.ascii file, list the node names in the order in which you want the
package to fail over. For performance reasons, let the package fail over locally first, then to
the remote data center. For the MAX_CONFIGURED_PACKAGES parameter, the minimum value
is 0 and maximum default value is 150 (depending on the number of packages that will run
on the cluster).
7. Copy the environment file template /opt/cmcluster/toolkit/SGSRDF/srdf.env to
the package directory, naming it pkgname_srdf.env:
# cp /opt/cmcluster/toolkit/SGSRDF/srdf.env \
/etc/cmcluster/pkgname/pkgname_srdf.env
NOTE: If you use a package name as a filename for the package control script, it is necessary
to 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 (srdf) used. The extension .env of the file must be used. The following
examples demonstrate how the environment file name must be chosen:
Example 1: If the file name of the control script is pkg.cntl, the environment file name would
be pkg_srdf.env.
Example 2: If the file name of the control script is control_script.sh, the environment
file name would be control_script_srdf.env.
8. Edit the environment file as follows:
a. Add the path where the EMC Solutions Enabler software binaries are installed to the
PATH environment variable. If the software is installed in the default location,/usr/
symcli/bin, there is no need to set the PATH environment variable in this file.
b. Uncomment the environment variables prefixed with AUTO_. HP recommends that you
retain the default values of these variables unless there is a specific business requirement
to change them. See Appendix B 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 is located. This directory must be unique for each package, and is used
for status data files. For example, set PKGDIR to/etc/cmcluster/package_name,
removing any quotes around the file names.
d. Uncomment the RDF_MODE variables and set it to the RDF mode for RDF pairs in the
device group to be Synchronous (sync) or Asynchronous (async).
e. Uncomment the DEVICE_GROUP variables EMC Symmetrix for the local disk array and
set it to the Symmetrix device group names given in the symdg list command. If you
are using an M by N configuration, configure the DEVICE_GROUP variable with the
name of the consistency group.
f. Uncomment the RETRY and RETRYTIME variables. These variables are used to decide
how often and how many times to retry the Symmetrix status commands. The defaults
must be used for the first package. For other packages, RETRYTIME must be altered to
92 Legacy packages