To distribute the Metrocluster environment file to other nodes in the cluster, you can also use the Command Fanout utility that is available from the Distributed Systems Administration Utilities (DSAU) application. The Command Fanout utility uses SSH. DSAU can be opened from the HP System Management Homepage (HP SMH), the single-system management application that is available with the HP-UX Operating Environment. For more information on the Command Fanout utility, see the Distributed Systems Administration Utilities User's Guide available at the HP Technical Documentation Website at http://www.hp.com.

7.Check the configuration using the cmcheckconf -P temp.config, and then apply the Serviceguard configuration using the cmapplyconf -P temp.config command or HP SMH.

NOTE: If external_pre_script is specified in a Metrocluster package configuration, the external_pre_script will be executed after the execution of Metrocluster module scripts in package startup. Metrocluster module scripts are always executed first during package startup.

To view a sample Metrocluster XPCA modular package configuration file, see Appendix A (page 475).

Migrating Legacy Packages to Modular Packages with Metrocluster with Continuous Access XP A.09.00

Serviceguard Legacy packages usually use application toolkits along with Metrocluster. Therefore, migration from a Legacy Metrocluster package to a Metrocluster Modular package must account for the application toolkits also. HP Serviceguard A.11.19 supports migration of the Serviceguard packages using application toolkits to Modular packages. The migration for Metrocluster must always occur after the application toolkits have been migrated. After it has been ascertained that the application toolkits have been migrated, complete the following steps to migrate the Legacy package to a Modular Metrocluster package.

1.At this juncture, only the ECM toolkits are migrated. The package configuration file contains the ECM toolkit information as toolkit modules and its attributes. So the Metrocluster module must be added to this configuration file.

2.The cmmakepkg command provides an -ioption that helps to add new modules to an existing package configuration file. Use this -ioption to include the Metrocluster module into the package configuration file.

The cmmakepkg command provides an -ioption that helps add new modules to an existing package configuration file. The mcxpca module is included into the package configuration file using this option of the cmmakepkg command.

3.The package configuration file now contains the module attribute dts/dts/dts_pkg_dir. The Metrocluster environment file location directory must be provided as a value to this attribute.

4.This package configuration file is applied using the cmapplyconf command and with this the migration is completed.

The following example elaborates on the migration of a Metrocluster package that uses Oracle toolkit for Oracle single instance applications:

1.Migrate the Oracle toolkits from legacy to modular by creating the intermediate modular ASCII file from the pre-existing legacy package configuration file.

#cmmigratepkg –p legacy_pkgname [-s] -o modular_pkgname1.ascii

The –sis optional and is provided to comment out the service part from the configuration file, so that the pre-configured service parameters from the toolkit modules, can be included into the package configuration file.

A modular ASCII file is created by taking input parameters from the Oracle toolkit configuration file, the toolkit module, and the originally created modular package configuration file.

184 Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access for P9000 and XP