Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access EVA P6000 for Linux B.01.00.00

Table 6 Replication Modes and Failover Scenarios (continued)
ResolutionDT_APPLICATION_STARTUP_POLICYReplication
Mode
Failover
Scenario
progress. Because the
WAIT_TIME is set to xx minutes,
complete. It starts
up immediately.
the program will wait for
completion of the log copy
…
The DR Group is in merging
state.
…
The WAIT_TIME has expired.
Error - Failed to failover and
swap the role of the device
group. The package is NOT
allowed to start up.
Restart the
package when
If full copy operation is complete before WAIT_TIME expires, DR
Group fails over and the package is started. Otherwise, the DR
Synchronous
or Enhanced
Asynchronous
Remote failover
during copying
the full copy is
completed.
Group does not failover and the package is not started. The
behavior is not affected by the presence of the FORCEFLAG file.
The following log message appears in the package log :
The replication link state is good, the role of the device group
on this site is "destination" and the data Track Copy is in
progress. Because the WAIT_TIME is set to xx minutes, the
program will wait for completion of the track copy.
....
The WAIT_TIME has expired. Error - Failed to failover and swap
the role of the device group. The package is NOT allowed to
start up.
To forcefully start
up the package
DR Group does not fail over and
the package does not start.
DR Group fails over and the
package is started.
Synchronous
or Enhanced
Asynchronous
Remote failover
when CA link
down and when even though data
The following log message
appears in the package log :
merge was in
progress
currency cannot
be determined,
Warning - Unable to get remote
DR group state because the CA
link is down.
create a
“FORCEFLAG”
file in package
directory, and
…..
then restart the
package.
The role of the device group on
this site is "destination". The
state of the replication link is
down and the state of data may
not be current. Because the
package startup policy is
DATA_CURRENCY_PREFERRED,
the package is NOT allowed to
start up.
The package can
be manually
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 restarted
The following log message appears in the package log :
full copy was in
progress
successfully on
remote site after
The role of the device group on this site is "destination". The
state of the data may be inconsistent due to replication link is
a consistent
down while data copying from source to destination is still in
progress. The package is NOT allowed to start up.
snapclone/snapshot
of the destination
Vdisk is restored.
HP recommends
to take a
snapshot/snapclone
28 Understanding failover/failback scenarios