Remote Replication Concepts
of replicated LUNs, however, will have different GUIDs (just as clones of local LUNs have
different GUIDs than their origins).
Related Topics
■
“Remote Replication Workflow” on page 470
■
“Remote Replication” on page 469
Replication Failures
Individual replication updates can fail for a number of reasons. Where possible, the appliance
reports the reason for the failure in alerts posted on the source appliance or target appliance, or
on the Replication screen for the action that failed. You may be able to get details on the failure
by clicking the orange alert icon representing the action's status.
The following are the most common types of replication failures:
Failure Details
Cancelled The replication update was cancelled by an administrator.
Replication can be cancelled on the source or target.
Network connectivity failure The appliance was unable to connect to the target
appliance due to a network problem. There may be a
misconfiguration on the source, target, or the network.
Peer verification failed The appliance failed to verify the identity of the target.
This occurs most commonly when the target has been
reinstalled or factory reset. A new replication target must
be configured on the source appliance for a target which
has been reinstalled or factory reset in order to generate
a new set of authentication keys. See “Replication
Targets” on page 529.
Peer RPC failed A remote procedure call failed on the target system. This
occurs most commonly when the target appliance is
running incompatible software.
Name collision Replication of <project/share> from <source> failed
due to a name collision with @<snapname> being held
on the target for NDMP. To recover, rename (or remove)
the snapshot on the replication source that has the same
name as the snapshot held by NDMP on the target (the
one named in the alert), unless it starts with .rr. Then
either perform a manual sync or allow the replication
source to automatically retry the replication update.
No package Replication failed because no package exists on the
target to contain the replicated data. Since the package is
created when configuring the action, this error typically
happens after an administrator has destroyed the package
on the target. It's also possible to see this error if the
Remote Replication 545
To Next Page
Loading...
Need help?
General
