Designing Disaster Tolerant High Availability Clusters, 10th Edition, March 2003 (B7660-90013)

Building a Continental Cluster
Preparing the Clusters
Chapter 5208
2. For new clusters, install minimum required versions of HP-UX and
MC/ServiceGuard. For existing clusters, perform a rolling upgrade to
the minimum required versions of HP-UX and MC/ServiceGuard if
necessary. Coordinate with the other site to make sure the same
versions and patches are installed at both sites. This may include
coordinating between HP support personnel if the sites have
separate support contracts.
3. Configure logical volumes, using the same names on both the
clusters whenever possible. If your cluster uses a physical data
replication method and if data replication between the disk arrays at
the different data centers has already taken place, vgimport and
vgchange can be used to help configure the logical volumes on the
Recovery Cluster.
4. Use cmgetconf to capture the other cluster’s configuration. Then use
cmquerycl on this cluster to generate a new ASCII file for the
recovery configuration. Modify the node names, volume group
names, resource names, and subnets as appropriate so that the two
clusters will be consistent. See chapter 5 in Managing
MC/ServiceGuard manual for details on cluster configuration.
5. Set up the recovery package(s):
a. Copy the package files from the other cluster for all mission
critical applications to be monitored by ContinentalClusters. In
the sample configuration this means copying the ASCII files
salespkg.config and custpkg.config, and the control scripts
salespkg.cntl and custpkg.cntl. (You may want to rename
the package configuration files using a naming convention that
lets you know that a package is a ContinentalClusters monitored
package. For example, you may want to 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 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: