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

Building a Continental Cluster
Preparing the Clusters
Chapter 5 209
• Package services
• Failfast settings
c. Modify the package control script (salespkg_bak.cntl),
checking for anything that may be different between clusters:
• Volume groups (VGs) may be different.
• IP addresses will be different.
• Site-specific customer-defined routines (for example routines
that send messages to a local administrator) may be
different.
• Control script files must be executable.
NOTE If you are using physical data replication on the HP
StorageWorks Disk Array XP Series with Continuous Access XP
or on the EMC Symmetrix using EMC SRDF, use the special
environment file templates that are provided by the separately
purchased MetroCluster/CA and MetroCluster/SRDF products.
6. Apply the configuration using cmapplyconf and test the cluster.
7. Test local failover of the packages. In our sample case, this would
mean enabling package switching for salespkg_bak (cmmodpkg -e
salespkg_bak) and then testing that salespkg_bak fails over from
NYnode1 to NYnode2.
8. If you are using logical data replication, configure, apply, and test
the data receiver package if one is needed.
9. 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.