It is a good practice to backup the Secondary data volumes at frequent intervals. During this period you can pause updates to any Secondary from the Primary host. During a pause, the Primary continues to keep a history of volume updates but does not send the updates to the Secondary. The network session between the Primary and paused Secondary (on behalf of the Secondary) is broken.

Sometimes, pausing the replication from the Primary host may be required to perform some maintenance tasks on the Secondary or to make configuration changes such as changes to the network connecting the two hosts. This can be done effectively by pausing the Secondary from the Primary.

You can use the resume feature to reestablish the network session between the Primary and Secondary host and allow updates to continue from the point of the pause. If there are any updates to the volume during the pause, a synchronous Secondary is forced to become asynchronous, until it catches up.