Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access for P9000 and XP A.11.00

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
If Delta Resync pair was deleted in the step Suspending the replication to the recovery cluster of
this section, re-create the Delta Resync pair and assign the remote command device to journal
volumes of Delta Resync pair using XP Remote Web Console. For details on assigning remote
command devices to journal volumes, see “Assigning Remote Command Devices to Journal Volumes”
(page 118).
Configuring the Site Controller Package in the Recovery Cluster
A Site Controller Package in the recovery cluster must be created using Metrocluster 3DC recovery
module dts/recovery_xpca3dc along with the Site Controller module dts/sc.
All 3DC parameters must be configured in the Site Controller Package configuration file. The
Metrocluster environment file need not be edited. The Metrocluster environment file is automatically
generated on all nodes when this package configuration is applied in the cluster. All parameters
that were previously available in the Metrocluster environment file are now configured from the
package configuration file.
CAUTION: Do not delete the Metrocluster environment file that is generated. This file is crucial
for failover and recovery operations in 3DC solution.
136 Designing a Three Data Center Disaster Recovery Solution