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

After the complex-workload packages are up, examine the package log files for any errors that
will 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 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.
To move a complex workload to the remote site:
1. Halt the Site Controller Package of a 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>
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.
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 the 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>
Administering Metrocluster with Serviceguard Manager
Follow the steps described here to administer Metrocluster or the packages configured under
Metrocluster using Serviceguard Manager.
Administering Metrocluster with Serviceguard Manager 77