Designing Disaster Recovery Clusters using Metroclusters and Continentalclusters, Reprinted October 2011 (5900-1881)

Table 26 Error Messages and their Resolution
ResolutionCauseLog Messages
Start the Remote Copy volume group
manually using startrcopygroup
The error was caused by one of the
following reasons:
The Remote Copy is not functioning
from the remote storage system to the
local storage system. The package is
command or via 3PAR Management
Console. Restart the package.
• The Remote Copy volume group
was stopped manually by using
not allowed to start up. Start the
Remote Copy volume group manually
before restarting the package.
stoprcopygroup command or
via 3PAR Management Console.
• There was a link failure followed
by link restore with auto_recover
policy not set.
Create a FORCEFLAG file under the
package directory using touch
The Remote Copy link is down and the
Remote Copy volume group status is
“Stopped”. AUTO_NONCURDATA
parameter is not set to 1.
The Remote Copy link is down and
data in the local storage system might
not be up-to-date. The user has set
AUTO_NONCURDATA parameter to 0,
<package directory>/FORCEFLAG
to start the package with or without the
and has not created the FORCEFLAG
latest data in the local storage system.
Restart the package.
file. The package is not allowed to
start up. To start the package forcefully
using non current data, use
FORCEFLAG file.
Wait till the Remote Copy volume group
is fully synchronized and is in “Synced”
state. Restart the package.
The data is being synchronized from
the remote storage system to the local
storage system, and the virtual
The Remote Copy volume group is in
"Syncing" state and
RESYNC_WAIT_TIMEOUT parameter
volumes of the Remote Copy volume
is set to 0. The package is not allowed
to start up.
group are in “Syncing” state.
Metrocluster parameter
RESYNC_WAIT_TIMEOUT is set to 0,
and is configured not to start under
this condition.
Change the Remote Copy volume group
policy to “no_fail_wrt_on_err” using the
The policy fail_wrt_on_err is not
supported for a Remote Copy volume
group in a Metrocluster environment.
The Remote Copy volume group is set
with fail_wrt_on_err and the link is
down. The package is not allowed to
start up.
command setrcopygroup pol
no_fail_wrt_on_err
<rc_volume_group_name> or via
3PAR Management Console.
If application availability is more
important than data currency, create a
The package fails back from the
remote site when the link is down. The
The role of local Remote Copy volume
group is “Primary” and the role of
FORCEFLAG file under the packagerole of local Remote Copy volume
group “Primary” and the role of the
remote Remote Copy volume group
role is “Primary-Rev”. The package is
directory using touch <package
remote Remote Copy volume group isnot allowed to start up. The link is
directory>/FORCEFLAG and then
restart the package.
“Primary-Rev”. The package is not
started because the data written on
down and the user has not created the
FORCEFLAG file.
the remote site has not been replicated
to the local site. Starting the package
on the local site discards all the
changes that were made earlier on
the remote site.
Start the replication using
startrcopygroup command, and
then restart the package.
The Remote Copy volume group is
configured but not yet started.
The Remote Copy volume group is
either in “New” or “Stale” status. The
package is not allowed to start up.
Take corrective actions based on the
cause identified.
The error was caused by one of the
following reasons:
The role of local Remote Copy volume
group is “Primary” and the role of
remote Remote Copy volume group is
• The storage system is down.
“Primary-Rev”. Start Remote Copy from
• The TCP/IP connectivity from the
node to the storage system is
down.
the remote site to this site using
“recover” operation before restarting
the package.
332 Building Disaster Recovery Serviceguard Solutions Using Metrocluster with 3PAR Remote Copy