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

Using ftp might be preferable at your organization, because it does not require the use of
a.rhosts file for root. Root access via the .rhosts might create a security issue.
11. Verify that every node in the Serviceguard cluster has the following files in the directory /etc/
cmcluster/<pkgname>.
<pkgname>.cntl Seviceguard package control script
<pkgname>_xpca.env Metrocluster/Continuous Access environment file
<pkgname>.config Serviceguard package ASCII configuration file
<pkgname>.sh Package monitor shell script, if applicable
other files Any other scripts you use to manage Serviceguard packages
The Serviceguard cluster is ready to automatically switch packages to nodes in remote data centers
using Metrocluster/Continuous Access.
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 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 for
P9000 and XP:
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 about 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, then 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
3. Create a Metrocluster Modular package configuration file using the package configuration
file created in step 1.
When using HP Serviceguard A.11.18, to include Metrocluster modules in the new modular
package configuration file:
a. Include the Metrocluster modules in the new configuration file
# cmmakepkg –i <modular_sg_ecm.conf> -m dts/mcxpca\
<modular_sg_ecm_mc.conf>
b. Copy the environment variable values from the Metrocluster environment file present in
the package directory, to the variables present in the newly created modular package
configuration file.
When using HP Serviceguard A.11.19, run the following command to include the Metrocluster
modules in the new modular package configuration file:
# cmmakepkg –i <modular_sg_ecm.conf> -m dts/mcxpca -t\
<path_to_env_file><modular_sg_ecm_mc.conf>
4. Halt the package.
# cmhaltpkg <package_name>
Migrating legacy to modular packages 175