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

# srvctl add database -d hrdb -o <Oracle_Home_directory>
# srvctl add instance -d hrdb -i hrdb1 -n <site 3 node 1>
# srvctl add instance -d hrdb -i hrdb2 -n <site 3 node 2>
After registering the database with the CRS cluster in the recovery cluster, you can run the srvctl
status command to view the health of the database.
Configure the RAC MNP Stack at the recovery cluster
The RAC database must be packaged as a Serviceguard MNP package. You must configure the
RAC MNP package to have a dependency on the Clusterware MNP package in the recovery
cluster. This step creates the RAC MNP stack at the recovery cluster that will be configured to be
managed by the Site Controller Package. For more information on configuring the RAC database
in MNP packages, see the Serviceguard Extension for Oracle RAC toolkit README.
Test the RAC database in the recovery cluster
It is recommended that you test the RAC database startup in the recovery cluster after the RAC
MNP stack is configured by completing the following tasks:
1. Halt the Site Controller Package in the primary cluster
2. Start the RAC database in the recovery cluster
3. Halt the RAC database in the recovery cluster
4. Start the Site Controller Package in the primary cluster
Halt the Site Controller Package in the primary cluster
You must halt the Site Controller Package and the RAC database in the primary cluster before
testing the RAC database startup in the recovery cluster. Halt the Site Controller Package running
on the primary cluster using the cmhaltpkg command. This command halts the RAC database
running in the primary cluster.
Start the RAC database in the recovery cluster
After halting the RAC database in the primary cluster, you can start the RAC database in the
recovery cluster. Start the RAC database package in the recovery cluster using the cmrunpkg
command. After the RAC database package is up and running, you can run the srvctl status
command to view the health of the RAC database in the recovery cluster.
Halt the RAC database in the recovery cluster
You must halt the RAC database in the recovery cluster so that it can be restarted at the primary
cluster site. Use the cmhaltpkg command to halt the RAC MNP stack in the recovery cluster.
Deport the disk groups in the recovery cluster using the vxdg deport command.
Start the Site Controller Package in the primary cluster
After halting the RAC database in the recovery cluster, you can start the Site Controller Package
and the RAC database in the primary cluster. Start the Site Controller Package on a node in the
primary cluster where it was previously running using the cmrunpkg command. This command
starts the RAC database in the primary cluster.
Resume replication to the recovery cluster
After ensuring that the RAC MNP stack is halted and the CVM disk groups are deported on the
recovery cluster, you must 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 step
“Suspending the replication to the recovery cluster” of this section. Run the following command to
resynchronize the Continuous Access Journal device group, which will start replicating the data
from the primary cluster to the recovery cluster:
# pairresync -g <Continuous Access Journal device group name> -c15
Deploying a Complex Workload in Three Data Center Solution using SADTA 457