Remote Replication Concepts
Failure Details
storage pool containing the package is not imported on
the target system, which may occur if the pool is faulted
or if storage or networking has been reconfigured on the
target appliance.
Non-empty package exists Replication failed because the target package contains
data from a previous, failed replication update. This error
occurs when attempting to send a replication update
for an action whose first replication update failed after
replicating some data. The target appliance will not
destroy data without explicit administrative direction,
so it will not overwrite the partially received data. The
administrator should remove the existing action and
package and create a new action on the source and start
replication again.
Disabled Replication failed because it is disabled on the target.
Either the replication service is disabled on the target or
replication has been disabled for the specific package
being replicated.
Target busy Replication failed because the target system has reached
the maximum number of concurrent replication updates.
The system limits the maximum number of ongoing
replication operations to avoid resource exhaustion.
When this limit is reached, subsequent attempts to
receive updates will fail with this error, while subsequent
attempts to send updates will queue up until resources are
available.
Out of space Replication failed because the source system had
insufficient space to create a new snapshot. This may
be because there is no physical space available in the
storage pool or because the project or one of its shares
would be over quota because of reservations that don't
include snapshots.
Key Unavailability Replication failed because the encryption key used by
the share is not available either on the source or target
system. Review the alerts on both the source and target
systems to ensure the key is available on both systems.
See “Replicating an Encrypted Share” on page 586
for information about replicating encrypted shares and
projects.
Incompatible target Replication failed because the target system is unable
to receive the source system's data stream format. This
can happen as a result of upgrading a source system and
applying deferred updates without having upgraded and
applied the same updates on the target. Check the release
notes for the source system's software version for a list of
deferred updates and whether any have implications for
remote replication.
iSCSI initiator/target missing Replication clone, sever, or reverse operation failed
because the initiator group or target group LUNs do not
exist for the LUNs included in the replication package.
546 Oracle ZFS Storage Appliance Administration Guide, Release OS8.6.x • September 2016
To Next Page
Loading...
Need help?
General
