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

NOTE: Ensure that the SG-CFS-PKG (system multi-node) package is running for the CFS/CVM
environment.
6. Startup the Oracle RAC instance packages on the primary cluster. If you have configured CFS
or CVM in your environment, issue the following command from the master node:
# /opt/cmconcl/bin/ccrac_mgmt.ksh start
Alternatively, you can run the command on any node in the primary cluster.
This command fails back all of the RAC instance packages configured to adopt to this cluster
as the primary cluster.
To failback only a specific set of the Oracle RAC instance package set.
# /opt/cmconcl/bin/ccrac_mgmt.ksh [-i <indexNumber>] \ start
<indexNumber> is the index used in the/etc/cmconcl/ccrac/ccrac.config file for the
target set of the Oracle RAC instance packages.
Rehearsing Oracle RAC Databases in Continentalclusters
Special precaution is required for running disaster recovery (DR) rehearsal for Oracle RAC
databases. For information on configuring and running rehearsal for RAC databases, see Disaster
Recovery Rehearsal in Continentalclusters whitepaper available at: http://www.hp.com/go/
hpux-serviceguard-docs.
Support for Complex Workloads in a Continentalclusters Environment using
SADTA
Site Aware Disaster Tolerant Architecture (SADTA) enables deploying complex workloads in a
cluster. Complex workloads are applications configured using multi-node and failover packages
with dependencies. SADTA includes crucial components such as the Site Controller Package and
the Site Safety Latch that manage the complex workload configuration. The Site Controller Package
is a special failover package that is created using the dts/sc module to collectively manage the
complex workload. The Site Safety Latch prevents the inadvertent simultaneous startup of the
workload configuration on both sites. The Site Safety Latch is an internal mechanism that is created
for each Site Controller Package.
For an overview of SADTA, and to understand its components, see the “Overview of Site Aware
Disaster Tolerant Architecture” (page 337).
Continentalclusters is configured with two clusters - a primary cluster, and a recovery cluster. When
configuring complex workload in Continentalclusters with SADTA, each cluster is configured with
one site in the cluster configuration file. The complex workload is configured in packages at both
the primary and recovery cluster. A Site Controller Package is created at each cluster to collectively
start, halt, and monitor the complex workload packages. Starting the Site Controller Package in
a cluster starts the corresponding complex workload packages in the cluster. The Site Safety Latch
prevents inadvertent simultaneous startup of complex workload packages at both the primary and
recovery clusters.
A Continentalclusters recovery group for a complex workload is configured with the corresponding
Site Controller Package in the primary cluster as a primary package and the Site Controller Package
in the recovery cluster as a recovery package. Figure 24 (page 126) illustrates the package view
of a complex workload configuration in Continentalclusters with SADTA.
Support for Complex Workloads in a Continentalclusters Environment using SADTA 125