HP Serviceguard Metrocluster with EMC SRDF for Linux B.01.00.00

Table 5 Package startup behavior in various failure scenarios (continued)
Metrocluster
behaviourAUTO parameters
SRDF
StatesFailover/Failback
the package
directory and restart
the package. To
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 not
AUTO_NO_REPLICATIONPartitionedNARWsync or
async
Failover
within the
allowed to start asprimary site
R1 side is normal(R1) when the
state, even thoughrecovery site
state of Symmetrix(R2) or the
on R2 could not beSRDF link is
down. verified. To start the
package
automatically, set
AUTO_NO_REPLICATION
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
AUTO_NO_REPLICATIONSuspendedWDRWsync 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
AUTO_NO_REPLICATION
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
AUTO_NO_REPLICATIONSplitRWRWsync or
async
Failover
within the
start in thisprimary site
condition. To start(R1) when the
32 Understanding Failover/Failback scenarios