User's Guide

to yes, will automatically start. If the auto_run flag set to no, then these instances must be
manually started on the restarted node.
Prior to halting a node in the cluster, the Site Controller Package must be moved to a different node
in the site. However, if the node that needs to be halted in the cluster is the last surviving node in
the site, then the Site Controller Packages running on this node fail over to the other site. In such
scenarios, the site aware disaster tolerant workload must be moved to the remote site before halting
the node in the cluster. For more information on moving a site aware disaster tolerant complex
workload to a remote site, see “Moving a Complex Workload to the Remote Site” (page 398).
Maintaining the Site
Maintenance operation at a site might require that all the nodes on that site are down. In such
scenarios, the site aware disaster tolerant workload can be started on the other site to provide
continuous service. For more information on moving a site aware disaster tolerant complex workload
to a remote site, see “Moving a Complex Workload to the Remote Site” (page 398).
Maintaining the Metrocluster Environment File
The Metrocluster environment file is available in the package directory of the Site Controller Package.
Follow all the rules and guidelines of Metrocluster while modifying the environment file. The changes
you make to the environment file must be repeated on all the appropriate nodes.
Moving the Site Controller Package to a Node at the Local Site
To complete maintenance operations on a node, there could be instances where a node in the
cluster needs to be brought down. In such cases, the Site Controller Package that is running on the
node needs to be moved to another node in the local site.
Complete the following procedure to move the Site Controller Package to another node in the local
site:
1. Login to the node where the Site Controller Package is running and go to the Site Controller
Package directory.
cd <dts/dts/dts_pkg_dir>
2. Run the HP-UX touch command with the DETACH flag, in the Site Controller Package directory.
touch DETACH
3. Halt the Site Controller Package.
cmhaltpkg <site_controller_package_name>
4. Login to the other node in the local site, and start the Site Controller Package.
cmrunpkg <site_controller_package_name>
Maintaining Site Controller Package
The Site Controller Package is a Serviceguard failover package. The package attributes that can
be modified online can be modified without halting the Site Controller Package. Certain package
attributes require that the Site Controller Package is halted. Halting the Site Controller Package
halts the workload packages and closes the Site Safety Latch on the site. The DETACH mode flag
allows the Site Controller Package to halt without halting the workload packages.
Complete the following steps to halt the Site Controller Package in the DETACH mode:
1. Identify the node where the Site Controller Package is running.
cmviewcl –p <site_controller_package_name>
2. Login to the node where the Site Controller Package is running and go to the Site Controller
Package directory.
cd <dts/dts/dts_pkg_dir>
396 Designing a Disaster Recovery Solution Using Site Aware Disaster Tolerant Architecture