Jump to main content

# Open Replicator session options

Open Replicator is a non-disruptive migration and data mobility application.

Depending on the operation that you are performing, some of the following options may not apply.

Table 1. Open Replicator session options
Session Option | Used with UI operation | Description
--- | --- | ---
Consistent | Activate | This option causes the volume pairs to be consistently activated.
Donor Update Off | Consistently stops the donor update portion of a session and maintains the consistency of data on the remote volumes.
Copy | Create | Volume copy takes place in the background. This behavior is the default for both pull and push sessions.
Cold | Create | Control volume is write-disabled to the host while the copy operation is in progress. A cold copy session can be created provided one or more directors discovers the remote device.
Differential | Create | This option creates a one-time full volume copy. Only sessions that are created with the differential option can be re-created. For push operations, this option is selected by default. For pull operations, this option is cleared by default (no differential session).
Donor Update | Create | This option causes data that is written to the control volume during a hot pull to also be written to the remote volume.
Incremental Restore | Maintains a remote copy of any newly written data while the Open Replicator session is restoring.
Force | Terminate Restore | Select the Force option if the copy session is in progress. This option allows the session to continue to copy in its current mode without donor update.
Donor Update Off | Select the Force option if the copy session is in progress. This option allows the session to continue to copy in its current mode without donor update.
Force Copy | Activate | This option overrides any volume restrictions and allows a data copy. For a push operation, remote capacity must be equal to or larger than the control volume extents and conversely for a pull operation. The exception to this rule is when you have pushed data to a remote volume that is larger than the control volume, and you want to pull the data back, you can use the Force_Copy option.
Front-End Zero Detection | Create | This option enables front end zero detection for thin control volumes in the session. Front-end zero detection looks for incoming zero patterns from the remote volume, and instead of writing the incoming data of all zeros to the thin control volume, the group on the thin volume is de-allocated.
Hot | Create | Hot copying allows the control device to be read/write online to the host while the copy operation is in progress. All directors that have the local devices mapped are required to participate in the session. A hot copy session cannot be created unless all directors can discover the remote device.
Nocopy | Activate | Temporarily stops the background copying for a session by changing the state to CopyOnAccess or CopyOnWrite from CopyInProg.
Pull | Create | A pull operation copies data to the control device from the remote device.
Push | Create | A push operation copies data from the control volume to the remote volume.
Precopy | Create Recreate | For hot push sessions only, begins immediately copying data in the background before the session is activated.
SymForce | Terminate | Forces an operation on the volume pair including pairs that would be rejected. Use caution when checking this option because improper use may result in data loss.