Configuration:
- using vSphere Replication 5.5 as replication engine to protect up to 75 VMs
- using SRM 5.5 to recover VMs
What is the implication of using vSphere Replication's native abilities to manually recover a particular VM outside of SRM if that VM already resides in a Protection Group and Recovery Plan in SRM? Will SRM know about it? What will the VM look like in the Recovery Plan if vSphere Replication recovers it and not SRM, i.e. Not Protected, Not Configured, etc.?
If it's very ugly to recover a single VM with vSphere Replication when that VM is part of a larger SRM Recovery Plan, I may have to look at creating per-VM Protection Groups for vSphere Replication-protected VMs for the cases where an individual VM needs to be recovered. This idea is not preferred because of the management overhead of so many Protection Groups, but I see that it's limited to a maximum of 75 VMs today, so I've got that going for me, which is nice. Or maybe we rely on other backup and recovery solutions if a single VM needs to be recovered and let SRM worry about the bigger picture.
All the best,
Mike
-----------------------------------------
Please consider marking this answer "correct" or "helpful" if you found it useful
Mike Brown
VMware, Cisco Data Center, and NetApp dude
Consulting Engineer
Twitter: @VirtuallyMikeB
Blog: http://VirtuallyMikeBrown.com
LinkedIn: http://LinkedIn.com/in/michaelbbrown
I reached out to the man himself and got this response:
I reached out to the man himself and got this response: