In order to run a reprotect operation, a recovery operation must be fully executed. If the workflow was run in disaster recovery mode and there were failures on the source site, resolve the issues and re-run the recovery operation until all operations complete successfully. This may require some manual intervention in the VMware environment depending on the failure.
Once complete, the reprotect operation will be available for execution.
Click on the Reprotect button. In the window that pops up, select the box to confirm the process. and click Next.
Review the details and click Finish to start the reprotect.
The reprotection process for ActiveDR is fairly straightforward for the SRA.
The process is:
-
Confirm that replication is enabled and in-sync to the formerly source, but now target, site
Prior to a reprotect the volumes on both sides will have both the puresra-demoted tag and the puresra-failover tag, here are the states.
Source volumes.
Target volumes.
The tags are removed on the source volumes during the step Configure storage to reverse direction.
But the tags are still on the target side after the reprotect is completed.
This is because the tags are removed from the source volumes directly. Removing the tags on the source volumes causes the removal of the tags to be propagated to the target volumes within minutes-therefore there is no need for them to be directly removed (also the array blocks manipulating volumes in a demoted pod directly in any way).
Their automated disappearance can take up to 15 minutes to occur, though the update can be forced by promoting then demoting the target pod (either manually or by running a test recovery).
Note:It is recommended to run a reprotect operation as quickly as possible to re-enable disaster recovery. If a disaster occurs while the environment is in a recovered, but-not-yet reprotected state, SRM-controlled recovery will not be possible and manual intervention will be needed.