Using backup and checkpoint

Using the checkpoint feature, you can synchronize the Secondary using a block-level backup and restore method without interrupting the Primary. The block-level backup can be used to recover the Secondary data in case of data volume failure.

This method is useful for low-bandwidth networks or very large data sets. When you use checkpoints, you take backup of the data on the Primary and physically ship the backup media to the Secondary location, and restore the backup on the Secondary. When you start the backup, mark the starting point, by using the checkstart operation on the Primary. When you end the backup, mark the ending point by using the checkend operation on the Primary. While the backup and restore is going on, updates are written to the Replicator Log volume.

To bring the Secondary data up-to-date, restore the block-level backup. After the restore is complete, start replication to the Secondary with checkpoint using the same checkpoint name that you had specified for the checkstart operation on the Primary.

The advantage of this method is that data on the Secondary is inconsistent for a shorter period although there is a risk that the Replicator Log volume may overflow.

Note:

The Secondary can be brought up-to-date only if the updates are still present in the Replicator Log volume. Using checkpoints is a multi-step process and therefore, needs to be done very carefully.

More Information

Understanding checkpoints