Building Disaster Recovery Serviceguard Solutions Using Metrocluster with EMC SRDF

5 Understanding Failover/Failback scenarios
Table 6 (page 55) describes the package startup behavior in various failure scenarios depending
on the AUTO parameters and the presence of FORCEFLAG file in the package directory.
Table 6 Package startup behavior in various failure scenarios
Metrocluster
behaviourAUTO parameters
SRDF
StatesFailover/Failback
Link stateR2 stateR1 stateReplication
Mode
By default, R1 and
R2 roles are not
AUTOSWAPR2SynchronizedWDRWsyncFailover to
recovery site
swapped during(R2) due to
failover. To swapapplication
the roles afterfailure in all
failover, set this
variable to 1.
the nodes on
the primary
site (R1).
ConsistententWDRWasync
Package fails to
start. Wait till the
N/ASyncInProgWDRWsync or
async
synchronization
completes and then
restart the package.
By default, the
package fails to
AUTOR2WDNLPartitionedWDNAsync or
async
Failover to
recovery site
start in this(R2) when the
condition. To startprimary site is
down. the package, create
a FORCEFLAG in
the package
directory and restart
the package. To
automate failover,
set AUTOR2WDNL
to 0.
By default, the
package fails to
AUTOR2WDNLPartitionedRWNAsync or
async
Local failover
within the
start in thisrecovery site
condition. To start(R2) when the
the package, createprimary site is
down a FORCEFLAG in
the package
directory and restart
the package. To
automate failover,
set AUTOR2RWNL
to 0.
By default, the
package fails to
AUTOR1UIPR1
UpdInProg
RWWDsync or
async
Failback to
the primary
site(R1) from start in this
the recovery condition because
site(R2) after the data will be
the primary inconsistent. To start
site is
restored.
the package, create
a FORCEFLAG in
the package
directory and restart
the package. To
55