Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access EVA A.05.01

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.

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>

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 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

To administer Metrocluster or the packages configured under Metrocluster using Serviceguard

Manager:

1. Access one of the node’s System Management Home Page at http://<nodename>:2301.

2. Click Tools, if Serviceguard is installed, one of the widgets will have Serviceguard as an

option. Click Serviceguard Manager link within the widget.

3. On the Cluster’s Home Page, click the Administration Tab and choose the available options

when required. Choose appropriate packages for the required option.

64 Administering Metrocluster