Replication Action Properties - Oracle ZFS Storage Appliance Administration Manual

Failure
Misc
A replication update fails if any part of the update fails. The current implementation replicates
the shares inside a project serially and does not rollback changes from failed updates. As a
result, when an update fails, some shares on the target may be up-to-date while others are not.
See "Replication Snapshots and Data Consistency" on page 542
Although some data may have been successfully replicated as part of a failed update, the current
implementation resends all data that was sent as part of the previous (failed) update. That is,
failed updates will not pick up where they left off, but rather will start where the failed update
started.
When scheduled or continuous replication fails, the system waits several minutes and
tries again. The system will continue retrying failed scheduled or continuous replications
indefinitely. At any point during the retry procedure, initiating a manual update will
immediately begin a retry, circumventing the usual delay between successive retries. If the
manual update completes successfully, it terminates the retry sequence and the replication
action reverts to its normal scheduled or continuous updates. Failed manual replications without
a prior scheduled replication action are not retried.
When a replication update is in progress and another update is scheduled, the scheduled
replication is deferred until the previous update completes, and an alert is posted.
Related Topics
How to Troubleshoot Replication Issues (Doc ID 1397959.1) on
■
//support.oracle.com/)

Replication Action Properties

Replication actions have the following properties.
The replication action properties in the BUI and CLI differ slightly, as described in the
following table.
Remote Replication Concepts
Details
The initiator or target group name was either deleted or
renamed on the target appliance.
Replication failed, but no additional information is
available on the source. Check the alert log on the target
system and if necessary contact support for assistance.
Some failure modes that currently fall into this category
include insufficient disk space on the target to receive the
update and attempting to replicate a clone whose origin
snapshot does not exist on the target system.
for details.
My Oracle Support (http:
Remote Replication 547