Appendix B Environment File Variables for Metrocluster CA EVA

This parameter defines the clustering environment in which the script is used. Should be set to “metro” if this is a Metrocluster environment and “continental” if this is a Continentalclusters environment. A type of “metro” is supported only when the HP Metrocluster product is installed. A type of “continental” is supported only when the HP Continentalclusters product is installed.

Contains the full path name of the package directory. This directory must be unique for each package to prevent the log file from being overwritten when there are multiple packages. This directory is also the place where the operator creates the FORCEFLAG file to force a package to start under certain circumstances. The file is deleted after the cmrunpkg packagename is running, so it must be re-created each time if you wish to start packages under these circumstances.

This parameter defines the preferred policy in allowing the application to start with respect to the state of the data in the local volumes. It should be set to one of the following three policies:

Availability_Preferred: The user chooses this policy if he prefers application availability. Metrocluster software will allow the application to start as long as the data is consistent; even though, it may not be current.

Data_Currency_Preferred: This policy is chosen if it is preferred the application operates on consistent and current data. Metrocluster software will only allow the application to start if it can tell for sure that the data the application will operate on is current. This policy only focuses on the state of the local data (with respect to the application) being consistent and current.

(0 or greater than 0 (in minutes))

This parameter defines the timeout, in minutes, to wait for completion of the data merging or copying for the DR group before startup the package on destination volume.

If WAIT_TIME is greater than zero, and if the state of DR group is “merging in progress” or “copying in progress” state, Metrocluster software will wait up till WAIT_TIME value for the merging or copying completion. If WAIT_TIME expires and merging or copying is still in progress, the package will fail to start with an error not to starting on any node in the cluster.

If WAIT_TIME is 0 (default value), and if the state of DR group is “merging in progress” or “copying in progress” state, Metrocluster software will not wait and will return an exit 1 code to Serviceguard package manager. The package will fail to start with an error not to starting on any node in the cluster.

The name of the DR group used by this package. The DR group name is defined when the DR group is created.

The world wide name of the EVA storage system that resides in Data Center 1. This storage system name is defined when the storage is initialized.

A list of the SMA servers that reside in Data Center 1. Multiple names can be defined by using commas as separators.

A list of the clustered nodes that reside in Data Center 1. Multiple names can be defined by using commas as separators.

The world wide name of the EVA storage system that resides in Data Center 2. This storage system name is defined when the storage is initialized.

A list of the SMA servers that reside in Data Center 2. Multiple names can be defined by using commas as separators.

A list of the clustered nodes that reside in Data Center 2. Multiple names can be defined by using commas as separators.

Sets the time in seconds to wait for a response from the SMI-S CIMOM in storage management appliance. The minimum recommended value is 20 seconds. If the value is set to be smaller than 20 seconds, Metrocluster software may time out before getting the response from SMI-S, and the package will fail to start with an error, not starting on any node in the cluster.