Just to be clear, you can’t replicate/protect the vCenter that is connected to SRM & VR (nor would you want to). If you are talking about having a VC/SRM server at each site and another VC/PSC...
See more...
Just to be clear, you can’t replicate/protect the vCenter that is connected to SRM & VR (nor would you want to). If you are talking about having a VC/SRM server at each site and another VC/PSC that is contained within the one where SRM is installed, then yes, this can be protected like any other workload. I don’t believe that VC supports having its IP address changed by SRM. I suggest looking into supported ways to change the VC IP address. I believe that the VCSA runs Photon which I don't believe SRM supports IP customization for.
Thank you for not assuming as when you make an assumption you make an ass out of "you" and "uption". VR is designed to prevent the scenario you mention. With VR you will always end up with a c...
See more...
Thank you for not assuming as when you make an assumption you make an ass out of "you" and "uption". VR is designed to prevent the scenario you mention. With VR you will always end up with a consistent snapshot at the target site. VR uses something similar to option two. Take a look at this video: VMworld 2012: Session BCO1505 - VMware vSphere Replication: Technical Walk-Through with Engineering - YouTube and this FAQ for details: Introduction and General Information
1. VR standalone doesn't support non-disruptive testing of recovery. For this you would need SRM and it will allow you to do this without disrupting replication or networking. 2. Reversing repli...
See more...
1. VR standalone doesn't support non-disruptive testing of recovery. For this you would need SRM and it will allow you to do this without disrupting replication or networking. 2. Reversing replication would be done after failing over 3. Yes, when replication is reversed VR will use the file at the original site as a seed and run a checksum then only replicated changes
Yes, see the following text: Notwithstanding the foregoing, the SRM Standard Edition Restriction shall not apply if a failover of Protected Virtual Machines causes the number of Protected Vir...
See more...
Yes, see the following text: Notwithstanding the foregoing, the SRM Standard Edition Restriction shall not apply if a failover of Protected Virtual Machines causes the number of Protected Virtual Machines to exceed the SRM Standard Edition Restriction within a physical facility or building for a reasonable period of time Let's say they failed over the 46 VMs (let's call it site A) to the site with 74 VM (site B) during a power outage at site A. When the power is restored at site A (a day or a week later) and they are able to fail back this would be supported. What wouldn't be (and would require purchasing enterprise licenses for the VMs at site B) is the power comes back and they redistribute the VMs such that now they have 76 VMs at B and 44 at A. Make sense?
From the SRM FAQ Site Recovery Manager FAQ : What are the limitations with Site Recovery Manager Standard Edition? VMware Site Recovery Manager Standard Edition is subject to the following re...
See more...
From the SRM FAQ Site Recovery Manager FAQ : What are the limitations with Site Recovery Manager Standard Edition? VMware Site Recovery Manager Standard Edition is subject to the following restrictions: (a) protect up to seventy-five (75) Virtual Machines within a physical facility or building (b) For each running copy of VMware Site Recovery Manager Standard Edition, manage up to seventy-five (75) Protected Virtual Machines If at any given time, the number of Protected Virtual Machines in subsections (a) or (b) exceeds seventy-five (75), You are required to upgrade all VMware Site Recovery Manager Standard Edition licenses to VMware Site Recovery Manager Enterprise Edition. Notwithstanding the foregoing, the SRM Standard Edition Restriction shall not apply if a failover of Protected Virtual Machines causes the number of Protected Virtual Machines to exceed the SRM Standard Edition Restriction within a physical facility or building for a reasonable period of time
As far as I know SRM isn't supported working with PSC behind a load-balancer. It may work as long as it is talking to the same PSC but if it switches to the other one it won't.
Just remove the hosts and make sure that your placeholder VMs aren't registered on the hosts you are removing. Move the VMs to other hosts if they are.
You need to read the documentation for your SRAs and the documentation for SRM around adding SRAs. They are installed on both SRM servers and they should show up in the UI after they have been in...
See more...
You need to read the documentation for your SRAs and the documentation for SRM around adding SRAs. They are installed on both SRM servers and they should show up in the UI after they have been installed correctly.
I thought it was published somewhere but not finding it now. I'll get something out as a blog shortly and see about getting the documentation updated as well.