Remote Replication Concepts
This option is primarily useful when using replication to migrate data between appliances or in
other scenarios that don't involve replicating the received data back to the source as part of a
two-system disaster recovery plan.
The replication sever operation converts a replication package to a regular local project.
Because all local shares are always exported, and may be shared over SMB, the sever operation
will fail if any mount points or SMB resoure names conflict between replicated filesystems
and other filesystems on the system. These conflicts must be resolved before severing the
replication package by reconfiguring the project or share mount points or SMB resource names.
Related Topics
■
Severing a Replication Package BUI, CLI
■
Setting Up Remote Replication for Disaster Recovery BUI, CLI
■
Using Replication for Disk-to-Disk Backups
How Reverse Replication Works
The direction of the replication can be reversed to support two-system disaster recovery plans
and disk-to-disk backups.
Reversing Replication for Disaster Recovery
The reverse replication operation converts the replication package into a local project.
This operation also configures a replication action on the new local project for incremental
replication back to the source appliance. The first update attempt will convert the original
project on the source system into a replication package and roll back any changes made since
the last successful replication update from that system.
The following figure describes a typical reverse replication sequence of events.
554 Oracle ZFS Storage Appliance Administration Guide, Release OS8.6.x • September 2016
To Next Page
Loading...
Need help?
General
