What are the internal basic steps in the VNXE replication process?

Vnxe replication uses internal checkpoints to replicate data. These internal checkpoints cannot be used for user management, which means you cannot manipulate them, such as deleting or resuming them.

The replication process contains the following internal steps (assuming that a connection has been established and validated between the source and target-side devices):

1, the network client can read or write to the source without interruption during the copy process. The target side is read-only during the copy process.

2. The VNXE administrator creates a copy session between the source and target-side objects.

3, the source side uses the specified interface to establish a connection with the target end object.

4, copy to the source object to create two checkpoints.

5, copy to target end object to create two checkpoints.

6. Replication verifies that there is no common ground between the source and target objects.

7. Perform a full copy operation to transfer data from the source end to the target side. If the user specifies a manual synchronization option, the data is transmitted only when the user is manually synchronizing.

8. On the target side, refresh the first checkpoint of the target segment ckpt to establish a common foundation with the source checkpoint.

9. After the common Foundation is established, refresh the second checkpoint at the source and ckpt the difference (increment) between the source-side checkpoint and the most recent point-in-time copy. Only increments between the current tag's internal checkpoint and the previously replicated internal checkpoint are transferred to the target side with a block ID.

10. After data transmission is completed, replication uses the nearest internal checkpoint on the target to establish a new common base ckpt 2. This latest internal checkpoint contains the same data as the internal checkpoint on the source end (Ckpt 2) that is marked for replication.

11, Replication Monitoring RPO value (if set) to determine how the target side is frequently updated source-side changes. Without RPO settings, users can synchronize on-demand.