VMware Velocity
  • Home
  • About
  • VMUG
    • VMUG Sponsorship
    • VMUG Events 2018
    • VMUG Events 2017
    • VMUG Events 2016
    • VMUG Events 2015
    • VMUG Events 2014
    • UPSNYVMUG 2016
    • UPSNYVMUG 2015
    • UPSNYVMUG 2014
  • VMworld
    • VMWORLD 2020
    • VMworld 2019
    • VMworld 2018
    • VMworld 2017
    • VMworld 2016
    • VMWorld 2015
    • VMWorld 2014
  • vBeers
  • Book Reviews

VMware Replication vs Veeam Replication

1/23/2015

0 Comments

 
VMware introduced replication in vSphere 5.5. The biggest limitation is that it only provides a single restore point only. This is an immediate show stopper for most customers. Multiple restore points are absolutely essential, because just like "good" data, any corruption/virus/dataloss from the source VM is immediately replicated to target VM, and if you don't spot the problem and perform failover to replica fast enough (before the next replication cycle) - which is going to be impossible in most cases - then you are done.
Picture
Other limitations
• No failback
• No traffic compression
• No traffic throttling
• No swap exclusion
• No network customization (network mapping)
• No re-IP upon failover
• Minimum possible RPO is 15 minutes
• Basic VSS quiescing (no application-aware processing)
• Works within single vCenter only
• No ability to create container-based jobs (explicit VM selection only)
• Limited seeding options: cannot seed from backup, or using different VM as a seed (disk IDs have to match)
• Different ports for initial and incremental sync required
• No good reporting

Also, be aware that biggest marketing push around vSphere replication is technically incorrect statement!
“Unlike other solutions, enabling vSphere replication on a VM does not impact I/O load, because it does not use VM snapshots”

It is simply impossible to transfer specific state of running VM without some sort of snapshot even in theory! In reality, during each replication cycle they do create hidden snapshot to keep the replicated state intact, just different type of snapshot (exact same concept as Veeam reversed incremental).

PROS: No commit required, snapshot is simply discarded after replication cycle completes.
CONS: While replication runs, there is 3x I/O per each modified block that belongs to the replicated state. This is the I/O impact that got lost in marketing.

Unlike VMware replication Veeam takes advantage of multiple restore points.
For every replica, Veeam Backup & Replication creates and maintains a configurable number of restore points. If the original VM fails for any reason, you can temporary or permanently fail over to a replica and restore critical services with minimum downtime. If the latest state of a replica is not usable (for example, if corrupted data was replicated from source to target), you can select previous restore point to fail over to. Veeam Backup & Replication utilizes VMware ESX snapshot capabilities to create and manage replica restore points.

Replication of VMware VMs works similarly to forward incremental backup. During the first run of a replication job, Veeam Backup & Replication copies the original VM running on the source host and creates its full replica on the target host. You can also seed this initial copy at the target site. Unlike backup files, replica virtual disks are stored uncompressed in their native format. All subsequent replication job runs are incremental (that is, Veeam Backup & Replication copies only those data blocks that have changed since the last replication cycle).
Picture
Conclusion:
Veeam Replication really stands out on top of the feature lacking VMware Replication. The numerous missing features like taking advantage of multiple snapshot replications, to help insure data integrity, no failback, no traffic throttling and no traffic compression etc., translate to only using VMware replication for simple use cases.
0 Comments

Your comment will be posted after it is approved.


Leave a Reply.

    Recognition

    Picture
    Picture
    Picture
    Picture

      Subscribe!

    Subscribe to Newsletter

    Categories

    All
    Amazon
    Ansible
    Certifications
    Citrix
    Cloud Foundations
    Containers
    Converged/Hyper Converged
    Horizon
    NSX
    SD-WAN
    VeloCloud
    VMC
    VMUG
    VSAN
    VSphere
    Workspace One

    Picture

    Archives

    January 2020
    October 2019
    April 2019
    May 2018
    April 2018
    December 2017
    October 2017
    June 2017
    April 2017
    March 2017
    February 2017
    October 2016
    September 2016
    June 2016
    May 2016
    April 2016
    March 2016
    February 2016
    January 2016
    October 2015
    March 2015
    February 2015
    January 2015
    November 2014
    September 2014
    August 2014
    June 2014
    May 2014
    April 2014
    December 2013
    September 2013

    RSS Feed

    Tweets by @bdseymour
  • Home
  • About
  • VMUG
    • VMUG Sponsorship
    • VMUG Events 2018
    • VMUG Events 2017
    • VMUG Events 2016
    • VMUG Events 2015
    • VMUG Events 2014
    • UPSNYVMUG 2016
    • UPSNYVMUG 2015
    • UPSNYVMUG 2014
  • VMworld
    • VMWORLD 2020
    • VMworld 2019
    • VMworld 2018
    • VMworld 2017
    • VMworld 2016
    • VMWorld 2015
    • VMWorld 2014
  • vBeers
  • Book Reviews