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

Environment File Variables for MetroCluster/CA
Appendix A 401
secondary site, the PVOL will become PSUE and the
SVOL will become PSUS(SSWS). When we fail back to
the primary site, any differential data that was on the
PVOL prior to failover will be lost during
resynchronization.
NOTE This variable is also used for the combination of
PVOL_PFUS and SVOL_PSUS. When the side file has
reached side file threshold timeout, the PVOL will
become PFUS. If there is a CA link, or some other
hardware failure, and we fail over the secondary site,
the SVOL will become PSUS(SSWS) but the PVOL will
remain PFUS. Once the hardware failure has been
fixed, any data that is on the MCU bit map will be lost
during resynchronization. This variable will allow
package startup if changed from default value of 0 to 1.
Values:
0—(DEFAULT) Do NOT failback to the PVOL side
after an outage to the PVOL side has been fixed. This
will protect any data that may have been in the MCU
side file or differential data in the PVOL when the
outage occured.
1—Allow the package to startup on the PVOL side. We
failed over to the secondary (SVOL) side due to an error
state on the primary (PVOL) side. Now we're ready to
failback to the primary side. The delta data between
the MCU and RCU will be resynchronized. This
resynchronization will over write any data that was in
the MCU side file prior to the primary (PVOL) side
failure.
AUTO_PSUSSSWS (Default=0)
This parameter applies when the PVOL is in the
suspended state PSUS, and SVOL is in the failover
state PSUS(SSWS). When the PVOL and SVOL are in
these states, it is hard to tell which side has the good