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

After the node maintenance procedures are complete, join the node to the cluster using the
cmrunnode command. If the Site Controller package is running on the site that the node belongs
to, the active complex-workload package instances on the site that have the auto_run flag set
to yes, will automatically start. If the auto_run flag is set to no, these instances must be manually
started on the restarted node.
Before halting a node in the cluster, the Site Controller Package must be moved to a different node
in the site. See “Moving the Site Controller package to a node at the local site” (page 62). However,
if the node that needs to be halted in the cluster is the last surviving node in the site, 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 64).
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 64).
Moving the Site Controller package to a node at the local site
To complete maintenance operations on a node, a node in the cluster might be required 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.
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 then start the Site Controller package.
# cmrunpkg <site_controller_package_name>
Maintaining Site Controller package
The Site Controller package is a Serviceguard failover package. 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.
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>
62 Administering Metrocluster