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

C Legacy packages
Configuring legacy Metrocluster package
To configure a legacy package:
1. Create a directory /etc/cmcluster/<pkgname> for every package.
# mkdir /etc/cmcluster/<pkgname>
2. Create a package configuration file.
# cd /etc/cmcluster/<pkgname>
# cmmakepkg -p <pkgname>.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 <pkgname>.config file, list the node names in the order in which you want the
package to fail over. It is recommended for performance reasons, to have the package fail
over locally first, 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 P9000 or XP Series disk array.
If you are using a fence level of ASYNC, then the RUN_SCRIPT_TIMEOUT must be greater
than the value of HORCTIMEOUT in the package environment file (see step 7h below).
NOTE: If you are using the EMS disk monitor as a package resource, you must not use
NO_TIMEOUT. Otherwise, package shutdown will hang if there is no access from the host to
the package disks.
This toolkit might increase package startup time by 5 minutes or more. Packages with many
disk devices will take longer to start up than those with fewer devices due to the time required
to get device status from the P9000 or XP Series disk array. Clusters with multiple packages
that use devices on the P9000 or XP Series disk array will all cause package startup time to
increase when more than one package is starting at the same time.
4. Create a package control script.
# cmmakepkg -s <pkgname>.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 in the appropriate places according to the
needs of the application. Refer to the latest version of the Managing Serviceguard manual
available 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/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
Configuring legacy Metrocluster package 173