Building Disaster Recovery Serviceguard Solutions Using Metrocluster with 3PAR Remote Copy

Table 4 Replication modes and failover scenarios (continued)
ResolutionMetrocluster ActionMetrocluster
Parameters
Replication
Mode
Replication
State/Link
Status
Remote
RCVG
Role
Local
RCVG
Role
NOTE: You can
start the package
after creating a
FORCEFLAG file.
However, the
package starts up
without syncing
the remote site
with the local
site, which results
in the loss of
data.
happening from the
remote storage system
to the local storage
system. Start the
Remote Copy volume
group manually before
restarting the
package.
Metrocluster starts up
the Remote Copy
volume group and
syncs the data from
RESYNC_WAIT_TIMEOUT
is greater than 0
RESYNC_WAIT_TIMEOUT
is set to no_timeout
the remote site to the
local site. If the sync
completes with the
time period specified
in
RESYNC_WAIT_TIMEOUT
parameter,
Metrocluster does a
role change and starts
up the package, else
it fails the package
startup with the
following error
message.
Error: Data copy is in
progress for <Local
Remote Copy Volume
Group name>.
Start the remote
copy using
Metrocluster fails the
package start up
SyncStopped/UpPrimary
Primary
Rev
Secondary
Secondary
Rev startrcopygroupirrespective of the
values specified
command or from
inRESYNC_WAIT_TIMEOUT
the Inform
and Management
Console GUI.AUTO_NONCURDATA
NOTE: You can
start the package
after creating a
FORCEFLAG file.
However, the
package starts up
without syncing
the remote site
with the local
site, which results
in the loss of
data.
parameters. It logs the
following message in
the log file.
Error: The Remote
Copy is not
happening from the
remote storage system
to the local storage
system. Start the
Remote Copy volume
group manually before
restarting the
package.
The package can
start up when
If the
AUTO_NONCURDATA
AUTO_NONCURDATA
= 0
Periodic/SyncStopped/DownPrimarySecondary
using the
parameter is set to 0,
FORCEFLAG file
the package fails to
option. To enable
start up and logs the
the package to
following error
start up, create a
message in the log
file.
FORCEFLAG file
44 Understanding failover/failback scenarios