Severing Replication - Oracle ZFS Storage Appliance Administration Manual

Replication updates are applied atomically at the filesystem level. Clients looking at replicated
files will see replication updates as an instantaneous change in the underlying filesystem.
Clients working with files deleted in the most recent update will see errors. Clients working
with files changed in the most recent update will immediately see the updated contents.
Replicated filesystems are not exported by default. They are exported by modifying the
exported property of the project or share using the BUI or CLI:
FIGURE 35 Inherited Properties
This property is inherited like other share properties. This property is not shown for local
projects and shares because they are always exported. Additionally, severing replication (which
converts the package into a local project) causes the package's shares to become exported.
Replicated LUNs currently cannot be exported. They must be first cloned or the replication
package severed in order to export their contents.
Related Topics
"Remote Replication Workflow" on page 470
■
"Inherited Properties" on page 364
■

Severing Replication

A replication package can be converted into a local, writable project that behaves just like other
local projects (that is, without the management restrictions applied to replication packages)
by severing the replication connection. After this operation, replication updates can no longer
be received into this package, so subsequent replication updates of the same project from the
source will need to send a full update with a new action (into a new package). Subsequent
replication updates using the same action will fail because the corresponding package no longer
exists on the target.
Remote Replication Concepts
Remote Replication 553