Use this option to restore the Secondary when its replication status is displayed as Failed.

During active replication if you find that the data on the Secondary is inconsistent or corrupted then you can rollback the Secondary to a known good state with the help of the restore feature. You can first restore the Secondary volumes from the backup and then restore the Secondary from a known Secondary or RLINK checkpoint that is associated with the backup.

To restore the Secondary, it is essential that the Replication status of the Secondary must be in the Failed state. Hence, if the replication status is Active then you can forcefully fail the Secondary before restoring it. If there are writes on the Primary node that have not been copied to the Secondary node, then the Restore operation displays a message stating that there may be a loss of writes temporarily. The Restore option enables you to reestablish the link between the Primary and the Secondary and then writes the data on to the Secondary. After the restore operation completes, the Secondary is up-to-date. This option is enabled only if any checkpoints are available for the selected Secondary.