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

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, neither half
may be used as a cluster lock disk. A configuration with 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 source 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
(Continuous Access) products from an SD depot. To configure modular packages in a
Continentalclusters environment, see “Configuring Modular Packages in Continentalclusters”
(page 65).
3. When swinstall(1m) has completed, create a directory as follows for the new package
in the source disk site.
# mkdir /etc/cmcluster/<package_name>
Create an Serviceguard package configuration file in the source disk site.
# 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 source disk site disaster, resulting in the recovery package
starting and running on the target disk site, the primary package should not be started until
after first stopping 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 user’s guide. Standard Serviceguard package customizations include
modifying the VG, LV, FS, IP, SUBNET, SERVICE_NAME, SERVICE_CMD, and
SERVICE_RESTART parameters. 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 the Managing Serviceguard user’s guide 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:
Completing and Running a Continentalclusters Solution with Continuous Access P9000 or XP 201