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

Checking the Version Number of the Continentalclusters Executables
In Continentalclusters version prior to A.08.00, some components of Continentalclusters are executed
from Java .jar files. To obtain version information about these files, use the what.sh script
provided in the /opt/cmconcl/jar directory. Example:
# /opt/cmconcl/jar/what.sh configcl.jar
For Continentalclusters version A.08.00 use the what command to get the versions of the
executables:
#what /usr/sbin/cmviewconcl
Next Steps
To implement the Continentalclusters design using physical data replication, use the procedures
described in the following sections:
• Chapter 3: “Building Disaster Recovery Serviceguard Solutions Using Metrocluster with
Continuous Access for P9000 and XP” (page 153)
• Chapter 4: “Building Disaster Recovery Serviceguard Solutions Using Metrocluster with
Continuous Access EVA” (page 211)
• Chapter 5: “Building Disaster Recovery Serviceguard Solutions Using Metrocluster with EMC
SRDF” (page 255)
• Chapter 6: “Building Disaster Recovery Serviceguard Solutions Using Metrocluster with 3PAR
Remote Copy” (page 310)
Support for Oracle RAC Instances in a Continentalclusters Environment
Support for Oracle RAC instances means that the RAC instances running on the primary cluster
will be restarted by Continentalclusters on the recovery cluster to continue serving the clients'
databases requests upon a primary cluster failure. Figure 21 is a sample of Oracle RAC instances
running in the Continentalclusters environment.
Figure 21 Oracle RAC Instances in a Continentalclusters Environment
As shown in the above example, Oracle RAC instances are configured to run in Serviceguard
packages. The instance packages are running on the primary cluster and will be recovered on the
Support for Oracle RAC Instances in a Continentalclusters Environment 113