Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access EVA A.05.01

F Legacy packages
Configuring legacy Metrocluster package
To configure a legacy package:
1. Create a directory /etc/cmcluster/<package_name> for each package.
# mkdir /etc/cmcluster/<package_name>
2. Create a package configuration file.
# cd /etc/cmcluster/<package_name>
# cmmakepkg -p <package_name>.config
Customize the package configuration file as appropriate to your application. Be sure to include
the pathname of the control script (/etc/cmcluster/pkgname/pkgname.cntl) for the
RUN_SCRIPT and HALT_SCRIPT parameters.
3. In the <package_name>.config file, list the node names in the order in which you want
the package to fail over. HP recommends for performance reasons, that you have the package
fail over locally first, and then to the remote data center.
The failover_policy parameter can be set to site_preferred even for legacy
packages.
Set the value of RUN_SCRIPT_TIMEOUT in the package configuration file to NO_TIMEOUT
or to a large enough value to take into consideration the extra startup time required to obtain
status from the WMS servers.
NOTE: If you use the EMS disk monitor as a package resource, do not use NO_TIMEOUT.
Otherwise, package shutdown will hang if there is no access from the host to the package
disks.
4. Create a package control script.
# cmmakepkg -s <package_name>.cntl
Customize the control script as appropriate to your application using the guidelines in the
latest version of the Managing Serviceguard manual available at http://www.hp.com/go/
hpux-serviceguard-docs —> HP Serviceguard. Standard Serviceguard package customizations
include modifying the VG, LV, FS, IP, SUBNET, SERVICE_NAME, SERVICE_CMD, and
SERVICE_RESTART parameters. Be sure to set FS_UMOUNT_COUNT to 1.
5. Add customer-defined run and halt commands according to the needs of the application. See
the latest version of the Managing Serviceguard manualavailable at http://www.hp.com/
go/hpux-serviceguard-docs —> HP Serviceguard for more detailed information on these
functions.
6. Copy the environment file template /opt/cmcluster/toolkit/SGCAEVA/caeva.env
to the package directory, naming it pkgname_caeva.env:
# cp /opt/cmcluster/toolkit/SGCAEVA/caeva.env \
/etc/cmcluster/<pkgdir>/<package_name>_caeva.env
92 Legacy packages