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

Physical Data Replication for ContinentalClusters Using Continuous Access XP
Setting up a Primary Package on the Primary Cluster
Chapter 6304
Create an MC/ServiceGuard package configuration file in the
primary cluster with the commands:
# cd /etc/cmcluster/<package_name>
# cmmakepkg -p <package_name>.ascii
Customize it as appropriate to your application. Be sure to include
the pathname of the control script (/etc/cmcluster/<package_name>/
<package_name>.cntl) for the RUN_SCRIPT and HALT_SCRIPT
parameters.
Set the AUTO_RUN flag to NO. This is to ensure the package will not
start when the cluster starts.
Only after primary packages start, use cmmodpkg to enable package
switching on all primary packages. Enabling package switching in
the package configuration would automatically start the primary
package when the cluster starts. However, had there been a primary
cluster disaster, resulting in the recovery package starting and
running on the recovery cluster, the primary package should not be
started until after first stopping the recovery package.
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.
5. Add customer-defined run and halt commands in the appropriate
places according to the needs of the application. See Managing
MC/ServiceGuard for more 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
7. Edit the environment file <pkgname>_xpca.env as follows: