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

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 done,
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>
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.
Also remove the Site Controller EMS resource dependency from packages managed by the
Site Controller packages on both sites.
For example, if you have CVM or CFS configured in your environment, remove the site safety
latch (EMS resource) details from the package configuration file and reapply the package
managing the CVM/CFS diskgroups.
3. Delete Site Controller package.
Run the cmdeleteconf command to delete the Site Controller package configuration on all
the nodes.
Starting a complex workload
The complex workload in SADTA can be started 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 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.
After the complex-workload packages are up, check the package log files for any errors that have
occurred at startup.
Administering the SADTA configuration 63