HP Serviceguard Metrocluster with EMC SRDF for Linux B.01.00.00

4 Understanding Failover/Failback scenarios
Table 5 (page 31) 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 5 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
N/ASynchronizedWDRWsyncFailover to
recovery site
swapped during
failover.
(R2) due to
application
NOTE: In case of
consistency groups,
role swap is not
done automatically.
failure in all
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
AUTO_NONCURDATAPartitionedWDNAsync 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
AUTO_NONCURDATA
to 0.
By default, the
package fails to
AUTO_NO_REPLICATIONPartitionedRWNAsync 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
AUTO_NO_REPLICATION
to 1.
By default, the
package fails to
N/AR1
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
31