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

Environment File Variables for MetroCluster/CA
Appendix A 403
This parameter applies when the PVOL and SVOL
both have the state of PSUE. This state combination
will occur when there is an CA link, or other hardware
failure, or when the SVOL side is in a PSUE state
while we can not communicate with the PVOL side.
This will only apply while in the Asynchronous mode.
The SVOL side will become PSUE after the CA link
timeout value has been exceeded at which time the
PVOL side will try and flush any data in the side file to
the SVOL side. If this flush is unsuccessful, then the
data on the SVOL side will not be current.
Values:
0—(Default) Do NOT startup the package at the
secondary site and allow package to try another node.
Require user intervention to either fix the problem by
resynchronizing the PVOL and SVOL or force the
package to start on this node by creating the
FORCEFLAG file.
1—Startup the package on the SVOL side. The risk of
using this option is that the SVOL data may actually
be non-current and the data written to the PVOL side
after the hardware failure may be loss.
AUTO_SVOLPSUS (Default=0)
This parameter applies when the PVOL and SVOL
both have the state of suspended (PSUS). The problem
with this situation is we cannot determine the previous
state: COPY or PAIR. If the previous state was PAIR,
it is completely safe to startup the package at the
remote site. If the previous state was COPY, the data
at the SVOL site is likely to be inconsistent
Values:
0—(DEFAULT) Do NOT startup the package at the
secondary site. Require user intervention to either fix
the problem by resynchronizing the PVOL and SVOL
or force the package to start on this node by creating
the FORCEFLAG file.