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

Once 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, start automatically. If the auto_run flag set to no, then 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. 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 about moving a site aware disaster tolerant complex
workload to a remote site, see “Moving a complex workload to remote site” (page 77).
Maintaining the site
Maintenance operation at a site might require that all the nodes on that site are down. In such a
case, the site aware disaster tolerant workload can be started on the other site and kept running.
For more information about moving a site aware disaster tolerant complex workload to a remote
site, see “Moving a complex workload to remote site” (page 77).
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 might be instances where a node in the
cluster must be brought down. In such cases, the Site Controller Package that is running on the
node must be moved to another node in the local site.
To move the Site Controller Package to another node in the local site:
1. Log in 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. Log in 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.
To halt the Site Controller Package in the DETACH mode:
Administering the SADTA configuration 75