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

NOTE: Starting with Continentalclusters A.08.00, the monitor package can be configured as a
modular package. In addition, the existing monitor package configured as a legacy package can
be migrated to a modular style package. HP recommends configuring this as a modular package.
For information on configuring the monitor package as a modular package or for migrating an
existing monitor package from the legacy package style to the modular style, see “Configuring
the Monitoring Daemon as a Modular Package” (page 65).
Configuring Modular Packages in Continentalclusters
With HP Serviceguard A.11.18 and later, modular packages can be created using building block
modules that consist of only those functions that are required for the package. This new modular
method of creating packages provides the following benefits:
• All package parameters are configured in one place - the package configuration file.
• Separate package control files need not be created and distributed in the cluster.
Starting with Continentalclusters A.08.00, packages in Continentalclusters can be configured as
modular packages. The Continentalclusters monitor package on the recovery cluster can be
configured as a modular package using the supplied template configuration file. Other packages
in the primary and recovery cluster which are configured in a recovery group as
primary_package, recovery_package, rehearsal_package, data_sender or
data_receiver package can also be configured as modular packages using the required
modules. When using any of the pre-integrated physical replication such as Continuous Access
P9000 or XP, Continuous Access EVA, 3PAR Remote Copy or EMC Symmetrix SRDF, modular
packages configured as primary or recovery packages must include the appropriate replication
specific module for the Continentalclusters environment.
The subsequent topics describes the steps and the rules for configuring modular packages in
Continentalclusters. The following topics are covered in this section:
• Configuring the Monitoring Daemon as a Modular Package
• “Configuring Primary and Recovery Packages as Modular Packages” (page 67)
• “Configuring Continentalclusters Data Sender and Data Receiver Packages as Modular
Packages” (page 74)
• “Configuring Continentalclusters Rehearsal packages as Modular Packages” (page 74)
Configuring the Monitoring Daemon as a Modular Package
With Continentalclusters versions prior to A.08.00, the monitoring package can only be configured
as a legacy style package. Starting with Continentalclusters version A.08.00, the monitoring
package can be configured as a modular package. The template file for creating a modular style
ccmonpkg is available in the /opt/cmconcl/scripts directory. This package configuration
file includes the Continentalclusters monitoring daemon /usr/lbin/cmclsentryd as a
pre-configured service.
To configure the monitoring daemon as a modular package:
1. On any node in the monitoring cluster, create a directory to store the configuration file of the
monitor package. For example, /etc/cmcluster/ccmonpkg/
2. Copy the modular package template file, /opt/cmconcl/scripts/
ccmonpkg_modular.config to the directory created in step 1.
cp /opt/cmconcl/scripts/ ccmonpkg_modular.config
/etc/cmcluster/ccmonpkg/ccmonpkg.conf
Building the Continentalclusters Configuration 65