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

1. Identify the node where the Site Controller Package is running.
cmviewcl –p <site_controller_package_name>
2. 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>
3. Run the HP-UX touch command with the DETACH flag, in the Site Controller Package directory.
touch DETACH
4. Halt the Site Controller Package.
cmhaltpkg <site_controller_package_name>
The Site Controller Package halts without halting the complex workload packages. The Site Controller
Package leaves the Site Safety Latch open on this site. The DETACH mode file is automatically
removed by the Site Controller Package when it halts. After the maintenance procedures are
complete, restart the Site Controller Package on the same site where it was previously halted in
the DETACH mode. You cannot start the Site Controller Package on a different site node. Run the
following command to start the Site Controller Package:
cmrunpkg <site_controller_package_name>
Run the following command to enable global switching for the Site Controller Package.
cmmodpkg –e <site_controller_package_name>
When the Site Controller Package is halted in the DETACH mode, the active complex workload
configuration on the site can be halted and restarted at the same site as the Site Safety Latch is
still open in the site.
Deleting the Site Controller package
To delete Site Controller package in a cluster:
1. Halt the Site Controller Package.
2. Remove all the Site Safety Latch dependencies configured for the packages managed by the
Site Controller Package. In addition to this, remove the Site Controller EMS resource
dependency from packages managed by the Site Controller Packages on both sites and
re-apply the package configuration.
3. Delete the Site Controller Package.
Run the cmdeleteconf command to delete the Site Controller Package configuration on all
the nodes.
Starting a complex workload
You can start the complex workload in SADTA in a Metrocluster by starting the Site Controller
Package.
To start the complex workload:
1. Ensure that the Site Controller Package is enabled on all the nodes in the site where the complex
workload must be started.
cmmodpkg –e –n <site A node 1> –n <site A node 2>\
<site_controller_package_name>
2. Start the Site Controller Package by enabling it.
cmmodpkg –e <site_controller_package_name>
The Site Controller Package starts on the preferred node at the site. At startup, the Site Controller
Package starts the corresponding complex-workload packages that are configured in that site.
76 Administering Metrocluster