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

The Site Controller Package starts up on a node in the remote site and starts the complex-workload
packages that are configured.
Restarting a Failed Site Controller Package
If the running Site Controller Package fails because of transient error conditions, restart the Site
Controller package on a node in the site where it was previously running.
Complete the following steps to restart the failed Site Controller Package:
1. Determine the error message logged in the package log, and fix the problem. The error
messages, causes and resolution are described in the Troubleshooting section of this chapter.
2. Ensure that the Site Controller Package is enabled on all nodes in the site where it was failed.
cmmodpkg –e –n <siteA node 1> —n <siteB node 2>\
<site_controller_package_name>
3. Start the Site Controller Package on a node in the same site where it was previously running.
cmrunpkg <site_controller_package_name>
Migrating Complex Workloads Using Legacy SG SMS CVM/CFS Packages to Modular SG SMS
CVM/CFS Packages with Minimal Downtime
Complete the following procedure to migrate all the legacy SG SMS CVM/CFS packages managed
by a Site Controller package to modular SG SMS CVM/CFS packages:
1. Halt the Site Controller that is running on the primary site in DETACH mode. When the Site
Controller package is halted in the DETACH mode, the Site Controller package will go down
without bringing down the complex workload packages. This is done by creating a file
"DETACH" in the Site Controller's package directory on the node where the Site Controller
package is running, and then executing the cmhaltpkg command:
cd <site_controller_pkg_dir>
touch DETACH
cmhaltpkg <site_controller_package_name>
2. Complete the following steps on the recovery site where the complex workload packages are
not running:
a. Take a backup of the application package configurations and delete the application
packages managed by the Site Controller on the recovery site. After completing this step,
there would be no dependents on the legacy CFS mount point MNP packages. In case
CFS mount point MNP packages have not been configured, this step will ensure that there
are no dependents on the legacy CVM diskgroup MNP packages:
cmgetconf -p <application_pkg_name> > <backedup_appl_config>
cmdeleteconf -p <application_pkg_name>
b. Use the cfsmntadm command to delete all the legacy disk group and mount point MNP
packages managed by the Site Controller from a node in the recovery site. Use the
cfsdgadm command if there are no CFS mounts configured.
cfsmntadm delete <mount point>
or
cfsdgadm delete <cvm_diskgroup_name>
c. Configure all the CVM diskgroups and the mount points required by an application in a
single modular SMS CFS /CVM package. Add the EMS resource and apply the
configuration.
cmapplyconf -P <modular_cfs_package_file>
d. Edit the application's configuration file and change its dependency from legacy CFS
mount point or CVM disk group MNP packages to the newly created modular SMS
CFS/CVM package. Apply this package configuration:
Administering the Site Aware Disaster Tolerant Metrocluster Environment 399