User's Guide

B Environment File Variables for Metrocluster Continuous
Access EVA
This appendix lists all Environment File variables that have been modified or added for Metrocluster
with Continuous Access EVA. It is recommended that you use the default settings for most of these
variables, so exercise caution when modifying them:
CLUSTER_TYPE 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.
PKGDIR If the package is a legacy package, then this variable
contains the full path name of the package directory. If the
package is a modular package, then this variable contains
the full path name of the directory where the Metrocluster
caeva environment file is located.
DT_APPLICATION_STARTUP_POLICY 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
two 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.
A package can be forced to start on a node by creating the
FORCEFLAG in the package directory.
WAIT_TIME (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 of 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.
487