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

9. Distribute Metrocluster with Continuous Access EVA configuration, environment, and control
script files to other nodes in the cluster by using ftp, rcp or scp.
# rcp -p /etc/cmcluster/<package_name> \
<other_node_name>:/etc/cmcluster/<package name>
See the example script /opt/cmcluster/toolkit/SGCAEVA/Samples/ftpit to see
how to semi-automate the copy using ftp. This script ensures that the package directories
already exist on all nodes. It is preferable to use ftp because, it does not require the use of a
.rhosts file for root. Root access via .rhosts may create a security issue.
10. Verify that each node in the Serviceguard cluster has the following files in the directory
/etc/cmcluster/<package_name>:
Seviceguard package control script<package_name>.cntl
Metrocluster with Continuous Access EVA environment
file
<package_name>_caeva.env
Serviceguard package ASCII configuration file<package_name>.config
Package monitor shell script, if applicable<package_name>.sh
Any other scripts used to manage Serviceguard
packages
other files
11. Check the configuration using the command: cmcheckconf -P <package name>.config,
and then apply the Serviceguard configuration using the command: cmapplyconf -P
<package_name>.config or SAM.
The Serviceguard cluster is ready to automatically switch packages to nodes in remote data
centers using Metrocluster with Continuous Access EVA.
Migrating legacy to modular packages
Metrocluster Legacy packages can be migrated to Modular packages using the procedure listed
in this section. However, the migration steps vary based on the HP Serviceguard version and the
Legacy package configuration. While completing the migration procedure, multiple package
configuration files are created. Only the final package configuration file that is created at the end
of the procedure must be applied.
To migrate Legacy packages to Modular packages using Metrocluster with Continuous Access
EVA:
1. Create a Modular package configuration file for the Metrocluster Legacy package.
# cmmigratepkg -p <package name>[-s] -o <modular_sg.conf>
IMPORTANT: This command generates a package configuration file. Do not apply this
configuration file until you complete the migration procedure.
For more information on the cmmigratepkg command, see Managing Serviceguard manual
available at http://www.hp.com/go/hpux-serviceguard-docs
2. If the Metrocluster Legacy package uses ECM Toolkit, generate a new Modular package
configuration file using the package configuration file generated in the step 1.
For example, if the Metrocluster Legacy package uses the ECM Oracle toolkit, generate a
new Modular package configuration file with the following command:
# cmmakepkg –i modular_sg.conf -m ecmt/oracle/oracle \
–t haoracle.conf modular_sg_ecm.conf
94 Legacy packages