Building Disaster Recovery Serviceguard Solutions Using Metrocluster with EMC SRDF

Table 6 Package startup behavior in various failure scenarios (continued)
Metrocluster
behaviourAUTO parameters
SRDF
StatesFailover/Failback
automate failover,
set AUTOR1UIP to
0. However, it is
better to wait for the
update to complete
before starting up
the package.
By default, the
package is allowed
AUTOR1RWNLPartitionedNARWsync or
async
Failover
within the
to start as R1 side isprimary site
normal state, even(R1) when the
though state ofrecovery site
Symmetrix on R2(R2) or the
could not beSRDF link is
down. verified. To require
operator
intervention before
starting, set
AUTOR1RWNL to
1.
This state can occur
when the domino
N/APartitionedNANRsync or
async
mode is set. The
administrator must
manually fix the
state before
attempting to start
the package.
By default, the
package fails to
AUTOR1RWSUSPSuspendedWDRWsync or
async
Failover
within the
start in thisprimary site
condition. To start(R1) when the
the package, createSRDF Links
a FORCEFLAG inare
suspended the package
directory and restart
the package. To
automate failover,
set
AUTOR1RWSUSP
to 1.
Package will not be
started in this case.
N/ASuspendedWDRWsync or
async
Failover to the
recovery site
Administrator must(R2) when the
fix the SRDF linksSRDF Links
before attempting to
start the package.
are
suspended
and the
application
fails on all the
nodes in the
primary site
(R1)
By default, the
package fails to
AUTOSPLITR1SplitRWRWsync or
async
Failover
within the
start in thisprimary site
condition. To start(R1) when the
the package, createSRDF links
are split. a FORCEFLAG in
56 Understanding Failover/Failback scenarios