will be consistent. See chapter 5 in the Managing Serviceguard user’s guide for details on cluster configuration.

5.Set up the recovery package(s).

Starting with Continentalclusters A.08.00, packages in Continentalclusters can be configured as modular packages. HP recommends configuring this as a modular package. For information about configuring primary and recovery packages as modular, see “Configuring Primary and Recovery Packages as Modular Packages” (page 67).

For configuring recovery packages using legacy style, perform the following tasks:

a.Copy the package files from the other cluster in the recovery pair for all mission critical applications to be monitored by Continentalclusters. In the sample configuration this means copying the ASCII files salespkg.configand custpkg.config, and the control scripts salespkg.cntl and custpkg.cntl. (If preferred rename the package configuration files using a naming convention that identifies a package is a Continentalclusters monitored package. For example, if preferred, name the sample package salespkg_bak.config to indicate that it is the backup or recovery package.)

b.Edit the package configuration files, replacing node names, subnets, and other elements as needed. For all recovery packages, be sure that AUTO_RUN (PKG_SWITCHING_ENABLED used prior to Serviceguard A.11.12) is set to NO in the configuration file. This will ensure that the recovery packages will not start automatically when the recovery cluster forms, but only when the cmrecovercl command is issued.

The following elements should be the same in the package configuration for both the primary and recovery packages:

•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 may 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.

6.Apply the configuration using cmapplyconf and test the cluster.

IMPORTANT: You must halt the primary package and the data sender packages before you attempt to run or test any recovery packages.

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.

# 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. Be sure to set LV_UMOUNT_COUNT to 1 or greater.

The New York cluster is shown in Figure 16.

Preparing the Clusters

57