After Site Recovery Manager performs a recovery, you can perform a failback to restore the original configuration of the protected and recovery sites.
About this task
To aid comprehension, the original protected site from before a recovery is site A. The original recovery site is site B. After a recovery from site A to site B, the recovered virtual machines are running on site B without protection.
Verify that the following conditions are in place.
You have performed a recovery, either as part of a planned migration or as part of a disaster recovery.
The original protected site, site A, is running.
If you performed a disaster recovery, you must perform a planned migration recovery when the hosts and datastores on the protected site, site A, are running again.
You did not run reprotect since the recovery.
- Click Recovery Plans in the Site Recovery Manager interface, select a recovery plan, and click Reprotect.
- Select the check box to confirm that you understand that the reprotect operation is irreversible.
- Review the reprotect information and click Start.
- Monitor the reprotect operation on the Recovery Steps tab until it finishes.
- (Optional) : If necessary, rerun reprotect until it finishes without errors.
At the end of the reprotect operation, Site Recovery Manager has reversed replication, so that the original recovery site, site B, is now the protected site.
- (Optional) : Click Test and follow the prompts to test the recovery plan.
Testing the recovery plan verifies that the recovery plan works after the reprotect operation.
- Click Recovery to run the recovery plan as a planned migration.
- Review the information in the confirmation prompt, and select I understand that this process will permanently alter the virtual machines and infrastructure of both the protected and recovery datacenters.
- Select Planned Migration, click Next, and click Start.
- Monitor the planned migration operation on the Recovery Steps tab until it finishes.
The planned migration shuts down the virtual machines on the new protected site, site B, and starts up the virtual machines on the new recovery site, site A. If necessary, rerun the planned migration until it finishes without errors.
When the planned migration completes, the virtual machines are running on the original protected site, site A, but the virtual machines are not protected. The virtual machines on the original recovery site, site B, are powered off.
- Click Reprotect and follow the instructions of the wizard to perform a second reprotect operation.
Running reprotect again reestablishes protection in the original direction from before the recovery.
You restored the protected and recovery sites to their original configuration before the recovery. The protected site is site A, and the recovery site is site B.