While many of you wonder why I am explaining manual Disaster Recovery failback when using VMware Site Recovery Manager where its an automated feature that is included in VMware vCenter Site Recovery Manager 5. Two main scenarios where this apply, the first one if you still using any vCenter Site Recovery Manager prior to VMware SRM 5. The other one if you need to break the replication then recover back without syncing back the changes that happened at the Disaster Recovery Site. In this scenario you won’t be able to use the automated failback feature of VMware vCenter Site Recovery Manager 5 as that sync the changes back to production in the process which you might not desire. For both of these scenarios the below steps become handy.
- Confirm Protected VMs recovered to DR Site are no longer being used and can be powered down.
- Confirm that you have an inventory of your VMs, DataStores, IPs, Network interfaces
- Power down the protected VMs in the DR Site.
- Perform a cleanup of the directory in the DR site that contained the placeholder VMs created during protection group creation in Protected site if placeholders exist.
- Delete earlier created Protection Groups and Recovery Plans.
- Connect to the vCenter Server in the protected site and remove all the VMs in the protected site that was recovered to the DR site from inventory.
- Connect to the vCenter Server in the DR site and remove all the VMs in the DR site that was recovered to it when the protected site failed over from inventory. (Only you need to remove it from inventory not from disk, in case you need to come back to it)
- Present the original LUNs back to the protected site as full read and write
- Right click the cluster where the the protected VMs reside in vCenter on the production side => Rescan for Datastores
- Go to each host configuration tab=> Storage. Then verify that all the datastores required are mounted.
- Add the VMs back to the inventory of the main site. Use the list created during the failover stage.
- If you see a small yellow warning on the VM then right click it and open the console on that VM. Then from the dialog choose “I moved it” and hit OK
- Reconfigure the VMs Network interfaces (Port groups) in case they are connected to a Distributed Switch. Note: Virtual Machines vDS Network Interfaces configuration in VMX file is lost upon removing it from inventory
- Establish replication from the protected site to the DR site.
- Recreate all the protection groups and recovery groups again.
- Run a failover test & clean up to ensure all is back in place.
I hope this help one execute or document the procedure as required.
Leave a Reply
Eiad Al-Aqqad, VCDX#89
VMware Canada PSO
- Backup Solutions (3)
- Blades (2)
- IBM Blades (2)
- Data Migration (2)
- EMC (1)
- VPLEX (1)
- How to (1)
- Management Software (5)
- Problem resolutions (0)
- Storage (19)
- Tips & Tricks (7)
- Tivoli (22)
- Tutorials (11)
- VMware (6)
- azhar: Really useful information Eiad THanks
- Mihai: thanks for the info Chip, very useful commands. starting from your example here we are another select: SELECT...
- MikeD: very helpful – but i hope we never need this precedure… thanks
- srinivas: Thanks for sharing such good article it is very useful to me. ch srinivas
- admin: How deeps is your pocket I guess ? Enjoy, Eiad
- TSM – IBM Tivoli Storage Manager Guru Blog: Microsoft SQL Cluster Data Migration to a new SAN
- TSM – IBM Tivoli Storage Manager Guru Blog: Migrating Exchange 2007/2003 Cluster to a new SAN
- IBM Tivoli Storage Manager Guru Blog: TSM
- How to Videos: Install IBM Systems Director 6 Common Agent on AIX | How to Install IBM Systems Director 6 Common...
- 8.3. Microsoft vShadow Transaction Consistent Database Cloning to a different server: Back to: IBM Tivoli Storage...
- Comparing Online Backup Services
- Veeam & PHD Virtual comparison
- IBM Tivoli Storage Manager support for VADP
- StarWind is Named a Finalist in The Storage Awards 2012
- PHD Virtual Monitor Review
- vSphere manual Disaster Recovery failback when using VMware SRM
- Migrating Exchange 2007/2003 Cluster to a new SAN
- Microsoft SQL Cluster Data Migration to a new SAN
- PHD Virtual Backup and Replication for VMware vSphere Review
- VMware ThinAPP Antivirus Best Practices