*************************************************************************
****** Updated information - Jun 02, 2015 ******
****** Check new Maximum for VR 6.0 ****** *************************************************************************
That’s an updated post of Demystifying vSphere Replication, which was focused on VR 5.1.
****** Updated information - Jun 02, 2015 ******
****** Check new Maximum for VR 6.0 ****** *************************************************************************
That’s an updated post of Demystifying vSphere Replication, which was focused on VR 5.1.
While most of
the concepts and information’s still true, the release of vSphere Replication 5.5 brought a few new
things!!!
For a total
comprehension of the topic I advise you to read the original post as well.
The
maximums still the same, but now there’s no difference between the VR that
comes with Site Recovery Manager (SRM) or the Stand Alone version, that means
you can replicate a maximum of 500 VMs, to load balance the replication you can
deploy multiple VR servers up to 10 (that’s the bigger change at 5.5), remembering
each one will be limited to a 100VMs.
Operations Limits (KB2034768), has just been updated to reflect this new concept.
A new
welcome feature is that now Storage vMotion and Storage DRS are supported on
the source VM, not affecting the replication of recoverability at all.
Another new
feature is the Multiple Point in Time Recovery, while configuring the
replication you can configure how many Point in time you want to keep. After recovering
a VM, those Multiple Points will be available as snapshots, which you could
revert as your will.
The
utilization of additional Multiple Point would cause a need for extra storage
on the
destination. Plan it carefully.
