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. Severing a replication package can be used to migrate data between appliances or in other scenarios that do not involve replicating the received data back to the source appliance.
If a replication update is performed during or after a sever operation, the update will fail with an appropriate alert. The replication action is then disabled, resulting in no future updates from this action to the replication target.
A new replication action and a full update of the same project is required to send replication updates to a new replication package.
To avoid mount point or SMB name conflicts, resolve the conflicts before severing the replication package by reconfiguring the project, share mount points, or SMB resource names. Because all local shares are always exported, and might be shared over SMB, the sever operation will fail if any mount points or SMB resource names conflict between replicated filesystems and other filesystems on the system.
Related Topics