Implementing disaster recovery for HP Integrity Virtual Machines with Metrocluster and Continentalclusters on HP-UX 11i

Table Of Contents

Appendix I

1. Sample legacy style package configuration file vmmetro.config for the example used in this

white paper (a few parameters are listed; for others, defaults are assumed):

# **********************************************************************

# Confidential commercial computer software. Valid license required.

########################################################################

# ****** HIGH AVAILABILITY PACKAGE CONFIGURATION FILE (template) *******

# **********************************************************************

# ******* Note: This file MUST be edited before it can be used. ********

# * For complete details about package parameters and how to set them, *

# * consult the Serviceguard Extension for RAC manuals.

# **********************************************************************

# @(#) $Id: hpvmtemplate.config 4656 2006-06-14 04:11:33Z tharple $

# Enter a name for this package. This name will be used to identify the

# package when viewing or manipulating it. It must be different from

# the other configured package names.

PACKAGE_NAME vmmetropkg

...

# Enter the names of the nodes configured for this package. Repeat

# this line as necessary for additional adoptive nodes.

# NOTE: The order is relevant.

# Put the second Adoptive Node after the first one.

# Example : NODE_NAME original_node

# NODE_NAME adoptive_node

# If all nodes in the cluster are to be specified and order is not

# important, "NODE_NAME *" may be specified.

# Example : NODE_NAME * NODE_NAME Node1

NODE_NAME Node2

NODE_NAME Node3

NODE_NAME Node4

...

# Enter the complete path for the run and halt scripts. In most cases

# the run script and halt script specified here will be the same script,

# the package control script generated by the cmmakepkg command. This

# control script handles the run(ning) and halt(ing) of the package.

# Enter the timeout, specified in seconds, for the run and halt scripts.

# If the script has not completed by the specified timeout value,

# it will be terminated. The default for each script timeout is

# NO_TIMEOUT. Adjust the timeouts as necessary to permit full

# execution of each script.

# Note: The HALT_SCRIPT_TIMEOUT should be greater than the sum of

# all SERVICE_HALT_TIMEOUT values specified for all services.