Designing Disaster Tolerant High Availability Clusters, 10th Edition, March 2003 (B7660-90013)

Environment File Variables for MetroCluster/CA
Appendix A404
1—Startup the package after making the SVOL
writeable. The risk of using this option is the SVOL
data may be inconsistent and the application may fail.
However, there is also a chance that the data is
actually consistent, and it is okay to startup the
application.
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.
DEVICE_GROUP
Specifies the Raid Manager device group for this
package.
FENCE
Fence level. Possible values are NEVER, DATA, and
ASYNC. Use ASYNC for improved performance over
long distances.
If a Raid Manager device group contains multiple items
where either the PVOL or SVOL devices reside on more
than a single XP Series array, then the Fence level
must be set to “data” in order to prevent the possibility
of inconsistent data on the remote side if an CA link or
an array goes down. The side effect of the “data” fence
level is that if the package is running and a link goes
down, an array goes down, or the remote data center
goes down, then write(1) calls in the package
application will fail, causing the package to fail.
HORCMINST
This is the instance of the Raid Manager that the
control script will communicate with. This instance of
Raid Manager must be started on all nodes before this