Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access EVA A.05.01

Table 7 Replication Modes and Failover Scenarios (continued)
ResolutionDT_APPLICATION_STARTUP_POLICYReplication
Mode
Failover
Scenario
the package is NOT
allowed to start up.
The package can be
manually restarted
DR Group does not fail over and the package does not start
because data is not consistent on the destination storage.
Synchronous
or Enhanced
Asynchronous
Remote failover
when CA link
down and when successfully on remote
The following log message appears in the package log :
full copy was in
progress
site after a consistent
snapclone/snapshot
The role of the device group on this site is "destination".
The state of the data may be inconsistent due to replication
of the destination
link is down while data copying from source to destination
is still in progress. The package is NOT allowed to start up.
Vdisk is restored. HP
recommends to take a
snapshot/snapclone
of the destination
Vdisks before the copy
starts so that there is
consistent copy
available for recovery.
Resume the link, and
then start up the
package
DR Group does not fail over and the package does not start.
The behavior is not affected by the presence of the
FORCEFLAG file.
SynchronousRemote failover
when the link is
manually
suspended
The following log message appears in the package log :
Error - The replication link is in suspend mode. The DR group
cannot be failed over.
To forcefully start up
the package, create a
DR Group does not fail
over and the package does
not start.
DR Group fails over and the
package is started.
Enhanced
Asynchronous
FORCEFLAG file in the
The following log message
appears in the package log
:
package directory,
and then restart the
package.
The replication link of this
DR group is in suspend
mode.
The replication link state is
good and the role of the
device group on this site is
"destination". Because the
state of the data may not
be current and the package
startup policy is
DATA_CURRENCY_PREFERRED,
the package is NOT
allowed to start up.
N/ASynchronousRemote failover
when DR Group
To forcefully start up
the package, create a
If the Merge operation
completes before
Waits until the WAIT_TIME for
the Merge operation is
Enhanced
Asynchronous
is in
RUNDOWN
“FORCEFLAG” file inWAIT_TIME expires, thecomplete. The package starts
even if merge is not complete
within this time.
state and the
link is up
package directory and
restart the package.
package is started.
Otherwise, the package
startup fails.
Package does not wait
for the merge to
The following log message
appears in the package log
:
complete. It starts up
immediately.
The replication link state is
good, the role of the device
group on this site is
destination" and the data
Metrocluster package failover/failback scenarios 55