Designing Disaster Recovery Clusters using Metroclusters and Continentalclusters, Reprinted October 2011 (5900-1881)

Combined with the DT_APPLICATION_STARTUP_POLICY and the presence or absence of the
FORCEFLAG, Metrocluster with Continuous Access EVA handles failover scenarios in different ways
when the replication mode is set to Asynchronous or Synchronous. Table 40 describes how failover
scenarios are addressed in different replication modes and when the FORCEFLAG is present.
Table 40 Replication Modes and Failover Scenarios
DT_APPLICATION_STARTUP_POLICY
Replication Mode
Failover
Scenario
FORCEFLAG is present.Data_Currency_PreferredAvailability_Preferred
Failover is issued
immediately and the
package is started .
Failover is issued
immediately and the
package is started.
Failover is issued immediately
and the package is started.
SynchronousRemote failover
during normal
operations
(planned
failover)
Same behavior as in
Synchronous mode.
Same behavior as in
Synchronous mode.
Same behavior as in
Synchronous mode.
Asynchronous
Failover is issued
immediately and the
package is started
Failover is not issued,
and the package will
not start.
Failover is issued immediately
and the package is started.
SynchronousRemote failover
with the link
down
Same behavior as in Synchronous mode.Asynchronous
If the Merge operation
completes before the
If the Merge operation
completes before the
If the Merge operation
completes before the time
SynchronousRemote failover
during merging
time specified for thetime specified for thespecified for the WAIT_TIME
WAIT_TIME parameter,WAIT_TIME
parameter, then the package
then the package isparameter, then theis started. If not, then the
package start-up fails. started. If not, then the
package start-up fails.
package is started. If
not, the package
start-up fails.
There is no impact to the
behavior when
FORCEFLAG is set or not
set.
Failover is issued
immediately and the
package is started .
Same behavior as in
Synchronous mode.
Irrespective of whether the
merging operation is
complete before or after the
Asynchronous
WAIT_TIME parameters, the
package is started.
If the full copy operation is complete before the time specified for the WAIT_TIME
parameter, then the package is started. If not, the package start-up fails.
SynchronousRemote failover
during copying
Same behavior as in Synchronous mode.Asynchronous
Failover is not issued, and the package does not start.SynchronousRemote failover
during manual
suspend
Failover is issued.Same behavior as in
Synchronous mode.
Failover is issued.Asynchronous
Failover is issued
immediately and the
package is started.
If the merge operation
is complete before the
time specified for the
Irrespective of whether the
merging operation is
complete before or after the
AsynchronousRemote failover
during rundown
and link up
WAIT_TIMEWAIT_TIME parameters, the
package is started. parameter, then the
package is started. If
not, the package
start-up fails.
Failover is issued
immediately, and the
package is started.
Failover is not issued,
and the package does
not start.
Failover is issued immediately
and the package is started.
AsynchronousRemote failover
during rundown
and link down
490 Environment File Variables for Metrocluster Continuous Access EVA