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

Figure 56 Sample Mutual Recovery Configuration of Continentalclusters with 3PAR Remote Copy
A Serviceguard cluster is configured with the nodes at Site1. A separate Serviceguard cluster is
configured with the nodes at Site2. A Continentalclusters is configured using the clusters at Site1
and Site2. Each cluster is configured with either a cluster lock disk or a quorum server as a
tie-breaker. There is a HP 3PAR storage system at each site, and they are connected to each other
through Remote Copy links.
In Figure 56, the application A is running on the cluster at Site1 can be recovered by the cluster
at Site2. Similarly, the application B is running on the cluster at Site2 can be recovered by the
cluster at Site1. The recovery of an application at the other cluster is automated, but must be
manually triggered upon notification. For each application, a synchronous replication using Remote
Copy Volume Group is configured to replicate the data between the two sites. Each cluster is
running a monitor package (ccmonpkg) that checks the status of the alternate cluster.
Each cluster runs, like any Serviceguard cluster, with applications configured in packages that may
fail from node to node as necessary. Each cluster is configured with a recovery version of the
packages that are running on the alternate cluster. These packages do not run under normal
circumstances, but are set to start up when they are needed. In addition, either cluster may run
other packages that are not involved in Continentalclusters operation.
Setting up a primary and recovery packages when using 3PAR Remote Copy
When using 3PAR Remote Copy in Continentalclusters, the primary and recovery packages must
be created using the dts/cc3parrc module. To use this module, Metrocluster with 3PAR Remote
Copy must be installed on all nodes in the Continentalclusters. For more information on configuring
primary and recovery packages using the dts/cc3parrc module, see “Configuring primary and
recovery packages as modular packages using 3PAR Remote Copy” (page 74).
Completing and Running a Continentalclusters Solution with 3PAR Remote Copy 327