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

It is suggested to use the name “ccmonpkg” for all Continentalclusters monitors. Create this
package on each cluster containing a recovery package. If it is not desired to monitor a cluster,
which does not containing a recovery package, it is required to delete or comment out the
MONITOR_PACKAGE_NAME line and the MONITOR_INTERVAL line. For mutual recovery,
create the monitor package on both the first and second clusters.
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. 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).
• Monitoring of a cluster not containing recovery packages is optional. For example, set
up monitoring of such a cluster to be able to check the status of the data replication
technology being used.
5. Repeat steps 2 through 4 for the other participating cluster or clusters.
NOTE: The monitor package is sensitive to system time and date. If you change the system time
or date either backwards or forwards on the node where the monitor is running, notifications of
alerts and alarms may be sent at incorrect times.
A printout of Section 1 of the Continentalclusters ASCII configuration file follows.
################################################################
#### #### Continentalclusters CONFIGURATION FILE #### ####
#### #### This file contains Continentalclusters #### ####
#### #### configuration data. #### ####
#### #### The file is divided into three sections, #### ####
#### #### as follows: #### ####
#### #### 1. Cluster Information #### ####
#### #### 2. Recovery Groups #### ####
#### #### 3. Events, Alerts, Alarms, and #### ####
#### #### Notifications #### ####
#### #### #### ####
#### #### For complete details about how to set the #### ####
#### #### parameters in this file, consult the #### ####
#### #### cmqueryconcl(1m) manpage or your manual. #### ####
################################################################
#### #### Section 1. Cluster Information #### ####
#### #### This section contains the name of the #### ####
#### #### Continentalclusters,name of the state #### ####
#### #### directory, followed by the names of member #### ####
#### #### clusters and all their nodes.The #### ####
#### #### Continentalclusters name can be any string #### ####
#### #### you choose, up to 40 characters in length. #### ####
#### #### The continentalclusters state directory #### ####
#### #### must be string containing the directory #### ####
#### #### location. The state directory must be #### ####
#### #### always an absolute path. The state #### ####
#### #### directory should be created on a shared #### ####
#### #### disk in the recovery cluster. This #### ####
#### #### parameter is optional, if maintenance mode #### ####
#### #### feature recovery groups is not required. #### ####
#### #### This parameter is mandatory, if maintenance #### ####
#### #### mode feature for recovery groups is #### ####
#### #### required. #### ####
#### #### Each member cluster name must be the same #### ####
#### #### as it appears in the MC/ServiceGuard cluster ########
#### #### configuration ASCII file for that cluster. #### ####
Building the Continentalclusters Configuration 77