You must take backups on the Secondary on a regular basis to guard against the consequences of disk failures. The Secondary checkpointing facility allows volume-level backups of the RVG to be restored at the Secondary node.
To get a consistent backup, replication must not be active. You do this by initiating a Secondary checkpoint at the Secondary node. This causes a request to be sent to the Primary node to pause updates and record the Secondary checkpoint in the SRL. While replication is paused, take a block-level backup of the RVG at the Secondary node. When the backup is complete, resume replication. Initiating a
resume at the Secondary node causes a request to be sent to the Primary node to resume updates. Note that the Secondary cannot do a checkpoint if it has lost contact with the Primary.
If you must recover from Secondary data volume failure, then after the block-level backup has been restored, subsequent updates can be replayed from the Primary starting at the checkpoint and the Secondary can be brought up-to-date. The Secondary can be brought up-to-date only if the updates are still in the SRL. You can display a list of checkpoints on the Secondary using the
cplist command. For more information, see Displaying a list of checkpoints.