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

Table 5 Error Messages and their Resolution (continued)
ResolutionCauseLog Messages
Start the replication group using either
the startrcopygroup command or
The error was caused due to one of
the following reasons:
Not able to determine the status of the
local storage system. This may be
because of SSH connectivity issues or
the 3PAR Management Console. Restart
the package.
• The storage system is down.
because the local storage system is
down. The role of remote Remote
• The TCP/IP connectivity from the
node to the storage system is
down.
Copy volume group is “Primary”. This
means that the role of local Remote
Copy volume group can be either
• If you are using CLI client, then
password files are not configured
“Secondary” or “Primary-Rev”, or the
local storage system is down. The
to connect from nodes to the
package is not allowed to start up on
storage system for the
this node. To allow the package
corresponding user. Otherwise,
startup on this node, either fix the
Password less SSH is not
connectivity issue or use FORCEFLAG
file.
configured from the node to the
storage system.
• The Remote Copy volume group
for DC1 or DC2 may not exist.
• The connections to 3PAR array are
exhausted. For more information
see “Managing connections to
3PAR array” (page 60).
Start the replication group using either
the startrcopygroup command or
The startrcopygroup command
failed.
Starting of the Remote Copy volume
group
[<remote_copy_volume_group_name>]
has failed to complete. This means that
the 3PAR Management Console. Restart
the package.
Remote Copy is not functioning
between the primary and secondary
volume groups. Manually start Remote
Copy volume group using the
startrcopygroup command.
Fix the issue based on the identified
cause. Restore the replication link, and
start the package.
Either the link is down or the remote
storage system is not up. The local
Remote Copy volume group is
The role of local Remote Copy volume
group is "Secondary-Rev" and the link
is down. The package is not allowed
“Secondary-Rev”. The replicationto startup. Restore the links and ensure
cannot be restored because the link isthe storage systems are up before
restarting this package. down, and there is no way to make
the “Secondary-Rev” volume
read/write.
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 Remote Copy
Resyncwait timeout has occurred. The
package is not allowed to start up on
this node. Either data copy is still in
volume group volumes are inprogress between the virtual volumes
“Syncing” state. Metrocluster packageof the primary and secondary Remote
startup failed because theCopy volume groups
synchronization of the volumes did not(<remote_copy_volume_group_name>)
complete within the time intervalor the status of the volume
specified in the parameter
RESYNC_WAIT_TIMEOUT.
group/virtual volume is not “Started
or Synced”.
Fix the issue based on the cause
identified.
The error was caused due to one of
the following reasons:
Metrocluster failed to discover the
properties of both the remote and local
Remote Copy volume groups. The
package is not allowed to start up.
• The storage system is down.
• The TCP/IP connectivity form the
node to the storage system is
down.
Troubleshooting Metrocluster 59