Building Disaster Recovery Serviceguard Solutions Using Metrocluster with EMC SRDF

Run the following command to enable global switching for the Site Controller Package.
# cmmodpkg –e <site_controller_package_name>
When the Site Controller package is halted in the DETACH mode, the active complex workload
configuration on the site can be halted and restarted at the same site as the Site Safety Latch is
still open in the site.
Deleting the Site Controller package
To delete Site Controller package in a cluster:
1. Halt the Site Controller package.
2. Remove all the Site Safety Latch dependencies configured for the packages managed by the
Site Controller package. In addition to this, 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, remove the site safety
latch (EMS resource) details from the package configuration file and re-apply the package
managing the CVM/CFS diskgroups.
3. Delete the Site Controller package.
Run the cmdeleteconf command to delete the Site Controller package configuration on all
the nodes.
Starting a complex workload
You can start the complex workload in SADTA in a Metrocluster by starting the Site Controller
package.
To start the complex workload:
1. Ensure that the Site Controller Package is enabled on all the 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, examine the package log files for any errors that
could have occurred at startup.
Shutting down a complex workload
You can shutdown the complex workload in SADTA 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, examine the Site Controller package log file and the workload package log
files to ensure that the complex workload has shutdown appropriately.
Moving a complex workload to a 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.
66 Administering Metrocluster