Environment File Variables for Serviceguard Integration with Continuous Access XP
Appendix A414
to minimize the down time of the application with the
trade-off of having to manually resynchronize the pairs
while the application is running at the primary site.
If the package has been configured for a three data
center environment, this parameter is applicable only
when the package is attempting to start up in either
the primary (DC1) or secondary (DC2) data center. This
parameter is not relevant in the recovery cluster or the
third data center. Use this parameter’s default value in
the third data center.
AUTO_NONCURDATA (Default=0)
This parameter applies when the package is starting
up with possible non-current data under certain
Continuous Access pair states. During failover, this
parameter will apply when the SVOL is in the PAIR or
PFUL state and the PVOL side is in the PSUE,
EX_ENORMT, EX_CMDIOE or PAIR (for Continuous
Access Journal) state. During failback, this parameter
will apply when the PVOL is in the PSUS state and the
SVOL is in the EX_ENORMT or EX_CMDIOE state.
When starting the package in any of the above states,
you run the risk of losing data.
Values:
0—(DEFAULT) Do NOT startup the application on
non-current data. If Metrocluster/Continuous Access
cannot determine the data is current, it will not allow
the package to start up. (Note: for fence level DATA
and NEVER, the data is current when both PVOL and
SVOL are in PAIR state.)
1—Startup the application even when the data may not
be current.
NOTE When a device group state is SVOL_PAIR on the local
site and EX_ENORMT (Raid Manager or node failure)
or EX_CMDIOE (disk I/O failure) on the remote site
(this means it is impossible for
Metrocluster/Continuous Access to determine if the
data on the SVOL site is current),