Designing Disaster Tolerant High Availability Clusters, 10th Edition, March 2003 (B7660-90013)

Building a Metropolitan Cluster Using MetroCluster/SRDF
Configuring MC/ServiceGuard Packages for Automatic Disaster Recovery
Chapter 4168
# cd /etc/cmcluster/pkgname
# cmmakepkg -p pkgname.ascii
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>.ascii file, list the node names in the order in
which you want the package to fail over. It is recommended for
performance reasons, that you have the package fail over locally
first, then to the remote data center.
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 not access from the host to the package disks.
This toolkit may 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 needed to get device
status from the EMC Symmetrix disk array. Clusters with multiple
packages that use devices on the EMC Symmetrix disk array will
cause package startup time to increase when more than one package
is starting at the same time.
The value of RUN_SCRIPT_TIMEOUT in the package ASCII file should
be set to NO_TIMEOUT or to a large enough value to take into
consideration the extra startup time due to getting status from the
Symmetrix.
4. Create a package control script with the command:
# cmmakepkg -s pkgname.cntl
Customize the control script as appropriate to your application using
the guidelines in Managing MC/ServiceGuard. Standard
MC/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 greater.