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

Environment File Variables for MetroCluster/CA
Appendix A 399
A Environment File Variables for
MetroCluster/CA
This appendix lists all Environment File variables that have been
modified or added for MetroCluster with Continuous Access XP. It is
recommended that you use the default settings for most of these
variables, so exercise caution when modifying them:
AUTO_FENCEDATA_SPLIT (Default=1)
This parameter applies only when the fence level is set
to DATA, which will cause the application to fail if the
CA link fails or if the remote site fails.
Values:
0—Do NOT startup the package at the primary site.
Require user intervention to either fix the hardware
problem or to force the package to start on this node by
creating the FORCEFLAG file. Use this value to
ensure that the SVOL data is always current with the
tradeoff of long application downtime while the CA link
and/or the remote site are being repaired.
1—(DEFAULT) Startup the package at the primary
site. Request the local disk array to automatically split
itself from the remote array. This will ensure that the
application will be able to startup at the primary site
without having to fix the hardware problems
immediately. Note that the new data written on the
PVOL will not be remotely protected and the data on
SVOL will be non-current. When the CA link and/or
the remote site is repaired, the user must manually use
the command "pairresync" to re-join the PVOL and
SVOL. Until that command successfully completes,
the PVOL will NOT be remotely protected and the
SVOL data will not be consistent. Use this value to
minimize the down time of the application with the
tradeoff of having to manually resynchronize the pairs
while the application is running at the primary site.