Designing Disaster Recovery Clusters using Metroclusters and Continentalclusters, Reprinted October 2011 (5900-1881)

12. Using standard Serviceguard commands (cmruncl, cmhaltcl, cmrunpkg, cmhaltpkg),
test the source disk site for cluster and package startup and package failover.
13. Any running package on the source disk site that will have a counterpart on the target disk
site must be halted at this time.
Setting up a Recovery Package on the Recovery Cluster
Use the procedures in this section to configure a recovery package on the target disk site. Consult
the Serviceguard documentation for more detailed instructions on setting up Serviceguard with
packages, and for instructions on how to start, halt, and move packages and their services between
nodes in a cluster.
NOTE: Neither the source disk site nor the target disk site may configure an P9000 or XP series
paired volume, PVOL or SVOL, as a cluster lock disk. A cluster lock disk must always be writable.
Since it cannot be guaranteed that either half of a paired volume is always writable, they may not
be used as a cluster lock disk. Using a disk as a cluster lock disk that is part of a paired volume
is not a supported configuration.
1. Create and test a standard Serviceguard cluster using the procedures described in the
Managing Serviceguard user’s guide.
2. Install Continentalclusters on all the cluster nodes in the target disk site (skip this step if the
software has been pre installed).
NOTE: Serviceguard should already be installed on all the cluster nodes.
Run swinstall(1m)to install Continentalclusters and Metrocluster Continuous Access products
from an SD depot. The toolkit integration scripts, environment file and contributed scripts will
reside in the /opt/cmcluster/toolkit/SGCA and /usr/sbin directories.
3. When swinstall(1m) has completed, create a directory as follows for the new package
in the target disk site.
# mkdir /etc/cmcluster/<package_name>
Create an Serviceguard package configuration file in the target disk site.
# cd /etc/cmcluster/<package_name>
# cmmakepkg -p <package_name>.ascii
Customize it as appropriate to your application. Make 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. Do not usecmmodpkg to enable package
switching on any recovery package. Enabling package switching will automatically start the
recovery package. Package switching on a recovery package will be automatically set by the
cmrecovercl command on the target disk site when it successfully starts the recovery package.
4. Create a package control script.
# cmmakepkg -s pkgname.cntl
Customize the control script as appropriate to your application using the guidelines in the
Managing 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 LV_UMOUNT_COUNT to 1 or greater.
Completing and Running a Continentalclusters Solution with Continuous Access P9000 or XP 203