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

1. Halt the Site Controller Package.
2. Remove all the Site Safety Latch dependencies configured for the packages managed by the
Site Controller Package.
Also remove the Site Controller EMS resource dependency from packages managed by the
Site Controller Packages on both sites.
For example, if you have CVM or CFS configured in your environment, run the following
commands from a node on both sites:
cfsdgadm delete_ems pkg1dg /dts/mcsc/cw_sc
3. Delete Site Controller Package.
Run the cmdeleteconf command to delete the Site Controller Package configuration on all
the nodes.
Starting a Complex Workload
The complex workload in SADTA can be started in a Metrocluster by starting the Site Controller
Package. Complete the following procedure to start the complex workload:
1. Ensure that the Site Controller Package is enabled on all nodes in the site where the complex
workload must be started.
cmmodpkg –e –n <site A node 1> –n <site A node 2>\
<site_controller_package_name>
2. Start the Site Controller Package by enabling it.
cmmodpkg –e <site_controller_package_name>
The Site Controller Package starts on the preferred node at the site. At startup, the Site Controller
Package starts the corresponding complex-workload packages that are configured in that site.
After the complex-workload packages are up, check the package log files for any errors that could
have occurred at startup.
Shutting Down a Complex Workload
The complex workload in SADTA can be shutdown by halting the corresponding Site Controller
Package. To shutdown the complex workload, run the following command on any node in the
cluster:
cmhaltpkg <site_controller_package_name>
This command halts the Site Controller Package and the current active complex-workload packages.
After shutting down, check the Site Controller Package log file and the workload package log files
to ensure that the complex workload has shut down appropriately.
Moving a Complex Workload to the Remote Site
To perform maintenance operations that require the entire site to be down, you can move the
disaster tolerant complex workload to a remote site. To move the complex workload to a remote
site, the local complex workload configuration must be first shut down and then the remote complex
workload configuration must be started.
Complete the following procedure to move a complex workload to the remote site:
1. Halt the Site Controller Package of the complex workload.
cmhaltpkg <site_controller_package_name>
2. Ensure the complex-workload packages are halted successfully.
cmviewcl -l package
3. Start the Site Controller Package on a node in the remote site.
cmrunpkg <site_controller_package_name>
398 Designing a Disaster Recovery Solution Using Site Aware Disaster Tolerant Architecture