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.

For a sample Metrocluster SRDF modular package configuration file, see Appendix C (page 491).

Migrating a Metrocluster Legacy Package to a Metrocluster SRDF A.08.00 Modular Package

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. Serviceguard 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, the following steps must be followed to migrate the Metrocluster legacy package into a modular 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 the -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 mcsrdf 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 –s is 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 in input parameters from the Oracle toolkit configuration file, the toolkit module and the originally created modular package configuration file.

#cmmakepkg –i modular_pkgname1.ascii -m ecmt/oracle/oracle -t\ haoracle.conf modular_pkgname2.ascii

2.Include the Metrocluster SRDF module into this modular package configuration file. Use the following command to include Metrocluster module.

"#cmmakepkg –i modular_pkgname2.ascii -m dts/mcsrdf modular_sg_ecm_mc.ascii

The new modular package configuration file will contain the dts/dts/dts_pkg_dir attribute unassigned.

278 Building Disaster Recovery Serviceguard Solutions Using Metrocluster with EMC SRDF