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

To activate LVM or SLVM volume groups in the recovery cluster, the cluster ID of the LVM or SLVM
volume groups must be changed as shown in the following sample. For LVM volume groups, run
the following commands to modify the cluster ID:
# vgchange -c n <vg_name>
# vgchange -c y <vg_name>
For SLVM volume groups, run the following commands to modify the cluster ID:
# vgchange -c n -S n <vg_name>
# vgchange -c y -S y <vg_name>
Configuring the Identical Complex Workload Stack at the Recovery Cluster
The complex workload must be packaged as Serviceguard MNP or failover packages. This step
creates the complex workload stack at the recovery cluster that will be configured to be managed
by the Site Controller Package. For more information on configuring the complex workload stack,
see the section “Configuring the Complex Workload Stack at the Primary Cluster.
Halting the Complex Workload on the Recovery Cluster
You must halt the complex workload stack on the recovery cluster so that it can be restarted at the
primary cluster. Halt all the packages related to complex workload using the cmhaltpkg command.
Configuring the Site Controller Package in the Recovery Cluster
The procedure for configuring the Site Controller Package in the recovery cluster is identical to
configuring the Site Controller Package in the primary cluster. For information on configuring the
Site Controller Package, see Configuring the Site Controller Package in the Primary Cluster.
Configuring Site Safety Latch Dependencies
The procedure to configure the Site Safety Latch dependencies in the recovery cluster is identical
tot he procedure for configuring the dependencies in the primary cluster. For information on
configuring these dependencies, see Configuring the Site Safety Latch Dependencies in the Primary
Cluster.
Resuming the Replication to the Recovery Cluster
Ensure that the Site Controller package and complex workload are halted on the recovery cluster.
Re-synchronize the replicated disk in the recovery cluster from the source disk in the primary cluster
for the replication that was split using the procedure listed in the “Suspending the Replication to
the Recovery Cluster” (page 136) section. The procedure to resume the replication depends on the
type of arrays that are configured in the environment. Based on the arrays in your environment,
see the respective chapters of this manual to configure replication.
Configuring Continentalclusters
After the Oracle RAC is configured along with the Site Controller Package on both, the primary
and recovery clusters, ensure that the Continentalclusters software is installed in all nodes in both
clusters. The Continentalclusters is configured between primary and recovery clusters. For more
information on configuring Continentalclusters, see “Building the Continentalclusters Configuration”
(page 58).
Migrating an Existing Oracle RAC Configuration to use SADTA
Prior to Continentalclusters Version A.08.00, the /etc/cmconcl/ccrac/ccrac.config file
is used to configure Oracle RAC . Starting with Continentalclusters Version A.08.00, you can use
Support for Complex Workloads in a Continentalclusters Environment using SADTA 139