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

Table 11 Configuration rules for using Modular style packages in Continentalclusters packages
(continued)
Logical Replication
3PAR Remote
Copy
Continuous
Access SRDF
Continuous Access
EVA
Continuous Access
P9000 or XP
Continentalclusters
Package Type
Continentalclusters
specific module
required.
Use any
Serviceguard
Data Receiver
Package
supported module.
No
Continentalclusters
specific module
required.
Editing the Continentalclusters Configuration File
First, on one cluster, generate an ASCII configuration template file using the cmqueryconcl
command. The recommended name and location for this file is /etc/cmcluster/
cmconcl.config. (If preferred, choose a different name.) Example:
# cd /etc/cmcluster
# cmqueryconcl -C cmconcl.config
This file has three editable sections:
• Cluster information
• Recovery groups
• Monitoring definitions
Customize each section according to your needs. The following are some guidelines for editing
each section.
Editing Section 1—Cluster Information
Enter cluster-level information as follows in this section of the file:
1. Enter a name for the Continentalclusters on the line that contains the
CONTINENTAL_CLUSTER_NAME keyword. Choose any name, but it cannot be easily changed
after the configuration is applied. To change the name, it is required to first delete the existing
configuration as described in “Renaming a Continentalclusters” (page 112).
Continentalclusters provides an optional maintenance feature for recovery groups. This feature
is enabled by configuring an absolute path to a file system for the
CONTINENTAL_CLUSTER_STATE_DIR parameter. If this feature is not required, this parameter
can be omitted.
2. Enter the name of the first cluster after the first CLUSTER_NAME keyword followed by the
names of all the nodes within the first cluster. Use a separate NODE_NAME keyword and HP-UX
host name for each node.
3. Enter the domain name of the cluster’s nodes following the DOMAIN_NAME keyword.
4. Optionally, enter the name of the monitor package on the first cluster after the
MONITOR_PACKAGE_NAME keyword and the interval at which monitoring by this package
will take place (minutes and/or seconds) following the MONITOR_INTERVAL keyword.
The monitor interval defines how long it can take for Continentalclusters to detect that a cluster
is in a certain state. The default interval is 60 seconds, but the optimal setting depends on
your system’s performance. Setting this interval too low can result in the monitor’s falsely
reporting an Unreachable or Error state. If this is observed during testing, use a larger value.
76 Designing Continentalclusters