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

7. Test local failover of the packages. In our sample case, this would mean enabling package
switching for salespkg (cmmodpkg -e salespkg) and then testing that salespkg fails
over from LAnode1 to LAnode2.
8. If using logical data replication, configure and test the data sender package if one is needed.
NOTE: If you are configuring Oracle RAC instances in Serviceguard packages in a CFS or CVM
environment, do not specify the CVM_DISK_GROUPS, and CVM_ACTIVATION_CMD fields in the
package control scripts as CVM disk group manipulation is addressed by the disk group multi-node
package.
The primary cluster is shown in Figure 15.
Figure 15 Sample Local Cluster Configuration
Configuring a Cluster with Recovery Packages
Use the following steps and the instructions in chapters 4 through 7 of the Managing Serviceguard
user’s guide as guidelines for creating a new Recovery Cluster or preparing an existing cluster to
run in a Continentalclusters environment:
1. Configure all hardware. Make sure the cluster hardware is able to handle the task of running
any or all packages it supports in the Continentalclusters configuration:
a. If this is a new cluster, make sure the hardware is similar to that of the other cluster. The
recovery cluster must be built using servers of sufficient size and resources so that they
can take over packages on recovery and also be able to run their own packages, if
required.
b. If this is an existing cluster, determine whether it is necessary to add disks for data
replication. This is needed to ensure that there is enough capacity from system resources
to run all packages if applications fail over to the other cluster. If not, either add nodes
to the existing cluster, or move less critical packages to another cluster.
2. For new clusters, install minimum required versions of HP-UX and Serviceguard. For existing
clusters, perform a rolling upgrade to the minimum required versions of HP-UX and 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. 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
56 Designing Continentalclusters