Security Solutions

Shutting Down a Complex Workload
The complex workload in SADTA can be shut down 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, verify 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 Recovery Cluster
To perform maintenance operations that require the entire site to be down, you can move the
disaster tolerant complex workload to a remote cluster. To move the complex workload to a remote
cluster, the local complex workload configuration must be first shut down and then the remote
complex workload configuration must be started.
The procedure to move a complex workload to the recovery cluster as follows:
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 recovery cluster.
# cmrunpkg <site_controller_package_name>
The Site Controller package starts up on a node in the recovery cluster 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 cluster where it was previously running.
To restart the failed Site Controller Package as follows:
1. Determine the error message logged in the package log, and fix the problem.
2. Ensure that the Site Controller package is enabled on all the nodes in the site where it was
failed.
# cmmodpkg –e –n <node 1> —n <node 2> <site_controller_package_name>
3. Start the Site Controller package on a node in the same cluster where it was previously running.
# cmrunpkg <site_controller_package_name>
70 Administering Continentalclusters