Hi
Do I need to buy two license in case active actvice protection ?
failback option dose it require a lisense in both sides or only in the protected site ?
Thanks
vSohill
Protection between VSAN stretched cluster sites isn't supported with SRM because VSAN is a single vCenter concept and SRM requires two. SRM would support failover between 2 separate VSAN stretched clusters.
vSphere Replication can replicate and failover VMs. Compared with SRM though you are missing:
- Non-disruptive testing (SRM supports testing failovers non-disruptively, this isn't possible with VR on it's own)
- Orchestration/Automation (SRM supports bringing up VMs in a specific order determined by priority groups and dependencies. It uses VMtools to ensure that a VM is fully operational before moving on to the next. VR does not do this. VR would require a manual failover and restart of each VM. This could work for less than 10 VMs, beyond that you would likely run into problems.)
- Failback - SRM will reverse replication and reprotection after failover, VR doesn't have that functionality
SRM requires licenses per protected VM so you don't need a license for the protected site and the failover site. For more licensing questions and answers see: https://www.vmware.com/files/pdf/products/SRM/vmware-site-recovery-manager-customer-faq.pdf
Many thanks @gs_khalsa
I need your clarification for two points:
- In the FAQ paper " Is Site Recovery Manager compatible with stretched storage solutions?
A. Yes. Site Recovery Manager 6.1 and newer versions support stretched storage solutions available by some of the major VMware storage partners."
Is it means that virtual san stretched cluster can funtion as Array Replications ?
- If I have two sites with static workload and there will no be any needs for vRO and vRA . Does vSphere replication without SRM can protects those VMs in case the failure of the protected site (with RPO 5 SRM 5 with vSAN)?
Protection between VSAN stretched cluster sites isn't supported with SRM because VSAN is a single vCenter concept and SRM requires two. SRM would support failover between 2 separate VSAN stretched clusters.
vSphere Replication can replicate and failover VMs. Compared with SRM though you are missing:
- Non-disruptive testing (SRM supports testing failovers non-disruptively, this isn't possible with VR on it's own)
- Orchestration/Automation (SRM supports bringing up VMs in a specific order determined by priority groups and dependencies. It uses VMtools to ensure that a VM is fully operational before moving on to the next. VR does not do this. VR would require a manual failover and restart of each VM. This could work for less than 10 VMs, beyond that you would likely run into problems.)
- Failback - SRM will reverse replication and reprotection after failover, VR doesn't have that functionality
Thank you Khalsa,
Very clear clarification