Veeam vs. vSphere Replication

VMware specific discussions

Re: Veeam vs. vSphere Replication

Veeam Logoby Gostev » Mon Oct 07, 2013 11:04 pm

Here is my current understanding, based on Ken's explanation above.

Ordered by I/O impact during data transfer periods, from lowest to highest:

1. Veeam replication with storage snapshot integration.
No I/O overhead.

2. vSphere replication
3x I/O overhead for VMDK writes to blocks belonging to the replicated state, and meeting the following criteria:
vmKen wrote:1) have changed while the replication for that VMDK is taking place,
2) have not already been sent from the current LWD,
3) have been sent but not written and acknowledged by the recovery site.

Write to PSF (for holding), Read from PSF + Write to VMDK (for LWD commit) = 3x I/O (Ken to confirm if 2x and why).

3. Veeam replication with vStorage API
3x I/O overhead for any VMDK write at all.
Write to snapshot (for holding), Read from snapshot + Write to VMDK (for snapshot commit) = 3x I/O
Gostev
Veeam Software
 
Posts: 21396
Liked: 2349 times
Joined: Sun Jan 01, 2006 1:01 am
Location: Baar, Switzerland

Re: Veeam vs. vSphere Replication

Veeam Logoby averylarry » Mon Oct 07, 2013 11:07 pm

averylarry wrote:I don't think so. Ken claims that only the very small subset of changed blocks that are changed again during the replication cycle are CoW . . .
And if I understand, it's only changed blocks that are changed again but haven't been replicated yet, so it's a shrinking subset of blocks that might need to be CoW.

If true, I think that really could be an interesting way to reduce I/O load from 3X guaranteed to 2X guaranteed and up to 3X max.

Of course, synchronous replication could in theory make no I/O impact. I think.
averylarry
Expert
 
Posts: 258
Liked: 28 times
Joined: Tue Mar 22, 2011 7:43 pm
Full Name: Ted

Re: Veeam vs. vSphere Replication

Veeam Logoby Gostev » Mon Oct 07, 2013 11:12 pm

averylarry wrote:it's a shrinking subset of blocks that might need to be CoW

That is correct. Still, LWD can produce noticeable extra I/O that should be taken into account for I/O intensive workloads before enabling vSphere replication.
Gostev
Veeam Software
 
Posts: 21396
Liked: 2349 times
Joined: Sun Jan 01, 2006 1:01 am
Location: Baar, Switzerland

Re: Veeam vs. vSphere Replication

Veeam Logoby dellock6 » Tue Oct 08, 2013 9:56 am 2 people like this post

First things first, thanks Ken for coming here and explaining these things. This discussion is becoming really interesting.

vmKen wrote: There is no published API at all, to partners or customers, it's using a fundamental call within the kernel itself, so it's hard to expose that gracefully to the outside world. Trust me, we get beat up on APIs about this all the time, but securing the kernel is important. So we have a few calls we can make to it internally (via CLI) to configure the replication and that's about it. Lots of people want API access and lots of people want expanded CLI. We're always looking at how to do that though! Some other vendors in the world are doing... inappropriate things to gain access to things like the vSCSI filters without an API, and the problem there is if we change anything at all on those internal calls the whole house of cards might come down. People don't like it when their replication stops working for DR. :) So we're looking at potentially writing a published API for this, but since that hasn't been in scope from the start it's something we're going to have to retrofit.


Even without putting out the names many of us know who are you referring about, and is more than one solution. One of them is really "near" to VMware and claims to use the vSCSI filter driver, so you are saying that even in that case it's a totally unsupported solution, from a VMware view point? You can also say "no comment" or nothing, I can understand.

Here is the problem: there is no other "officially supported" way of doing replication other than VM snapshots (or bypassing it completely with storage level replication), so some other solutions choose some "hacks" and by doing this they are totally unsupported; this is not a great thing not only because one simple change in the kernel would break their software, but also since we are talking about data protection so even official support is important.

But, but, there is an exception with your own Replication, that uses an "internal use only" kernel call. I've found this blog post by you (http://blogs.vmware.com/vsphere/2011/10 ... -work.html) and also this KB (http://kb.vmware.com/selfservice/micros ... Id=2005776) and in both places VMware says it's using vSCSI filter driver, the same of the other solutions.

So, can we sum it as "the filter driver itself is totally supported, but only if it's called by a VMware product" ?

Really, exposing those calls to partners would make all this stuff really easier, completely supported, and at the end customers will have better products.
Your role sounds to me like one that could eventually take care of this :)

Luca.
Luca Dell'Oca
EMEA Cloud Architect @ Veeam Software

@dellock6
http://www.virtualtothecore.com
vExpert 2011-2012-2013-2014-2015-2016
Veeam VMCE #1
dellock6
Veeam Software
 
Posts: 5052
Liked: 1330 times
Joined: Sun Jul 26, 2009 3:39 pm
Location: Varese, Italy
Full Name: Luca Dell'Oca

Re: Veeam vs. vSphere Replication

Veeam Logoby Starman » Mon Oct 14, 2013 3:36 pm

The only difference that matters to me is that Veeam does not work (or have a plug in for) with VMware SRM so I am forced to use VMware replication on the 20% of machines that aren't on my Equalogics for array based replication. I say so again so that it may happen in the future :)

I've never been very happy with the extremely limited VMware replication devices.
Starman
Enthusiast
 
Posts: 44
Liked: 10 times
Joined: Tue Sep 27, 2011 5:11 pm
Full Name: Todd Leavitt

Re: Veeam vs. vSphere Replication

Veeam Logoby PeteWest » Mon Oct 21, 2013 6:40 am

This forum was a great read :)
We are possibly purchasing Veeam soon. Ive found that a lot of features functionality depends on the business requirements.
I've noticed high I/O and performance impacts when VM's come in and out of snapshots, i would like to use storage level replication to avoid this but Veeam only support HP SANS and the function is at an increased cost.
Obviously an advantage is vSphere replication is free... It also allows us to Replicate production from a Dell Compellent SAN to our older EMC San, which Veeam cannot.
Once Veeam releases a few plug-ins for more SAN vendors will re-asses, but even then may stick with vSphere replication as alwyas have a few little disk consolidation issues and performance impact using snapshot, we will already be using many snapshots with Veeam images, adding many hourly replication snapshots to production machines as well doesn't appeal to us.
Im in no way a replication or backup specialist, this is just based on encountered experiences.
In relation to the question Veeam v vSphere replicaton.. we plan to be using both haha :)
Cheers
PeteWest
Lurker
 
Posts: 1
Liked: never
Joined: Mon Oct 21, 2013 6:10 am
Full Name: Pete Weston

[MERGED] Veeam Replication vs vSphere Replication 5.5

Veeam Logoby karlochacon » Fri Jan 31, 2014 5:35 pm

hi guys

I would like to know what I have to choose among Veeam and vSphere replication but regarding version 5.5

for what I know vSphere Replication now has multiple recovery points but I was reading only one VM at a time can be recover during a Failover.
I know the RPO for vSphere replication is 15 min what about Veeam?

does any one has any comparison table among these products?

BTW can I failover and failback multiple VMs at a time using Veeam?

thanks a lot
karlochacon
Enthusiast
 
Posts: 35
Liked: never
Joined: Wed Mar 21, 2012 5:43 pm
Full Name: Carlos Chacon

Re: Veeam vs. vSphere Replication

Veeam Logoby v.Eremin » Mon Feb 03, 2014 8:55 am

Hi, Carlos,

Your post has been merged into existing discussion regarding similar matter, so, please, take a look at the answers provided above.

I know the RPO for vSphere replication is 15 min what about Veeam?

You can set whatever interval or exact run time you want to. Also, if you're after minimal RPO, you can set replication job to run continuously. This, way new replication cycle will be started immediately after the previous one is finished.

BTW can I failover and failback multiple VMs at a time using Veeam?

Yes, you can select multiple VMs at one time and perform the said operations.

Thanks.
v.Eremin
Veeam Software
 
Posts: 13281
Liked: 970 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin

Re: Veeam vs. vSphere Replication

Veeam Logoby DaveBristolIT » Fri Jul 18, 2014 7:59 am

From a pure speed point of view, across local network, is vSphere replication quicker? Veeam replication on it's first run is about 7MB/sec in my current environments and blames the "Target" for being the bottleneck, even though the Target is capable of writing at speeds of 200MB/sec plus.
DaveBristolIT
Influencer
 
Posts: 13
Liked: 1 time
Joined: Mon Mar 17, 2014 11:06 am
Full Name: Dave Hamer

Re: Veeam vs. vSphere Replication

Veeam Logoby Vitaliy S. » Sat Jul 19, 2014 3:14 pm

What performance rate do you have if you try to write any similar data to the target storage via datastore browser of the vSphere Client?
Vitaliy S.
Veeam Software
 
Posts: 19564
Liked: 1104 times
Joined: Mon Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov

Re: Veeam vs. vSphere Replication

Veeam Logoby Gostev » Sun Jul 20, 2014 7:34 pm

Vitaly, I think I can answer this question myself (about 7MB/s or so) :)
Perhaps the target proxy is simply not hot add capable in this case.
Gostev
Veeam Software
 
Posts: 21396
Liked: 2349 times
Joined: Sun Jan 01, 2006 1:01 am
Location: Baar, Switzerland

Re: Veeam vs. vSphere Replication

Veeam Logoby DaveBristolIT » Mon Jul 21, 2014 6:45 am

Hotadd... well that's an entire different equation that I'm currently struggling with Veeam Support on (00581754)

I can tell you the speed uploading via vSphere client in about 50 hours after my 2TB replication finishes at 5MB/sec :( I know from previous experience that I've been able to upload the 2012 R2 ISO to the datastore in about 45 seconds (91MB/sec)
DaveBristolIT
Influencer
 
Posts: 13
Liked: 1 time
Joined: Mon Mar 17, 2014 11:06 am
Full Name: Dave Hamer

Re: Veeam vs. vSphere Replication

Veeam Logoby Vitaliy S. » Mon Jul 21, 2014 1:45 pm

The upload speed via Datastore Browser and writing data to target host via network mode is the same, since the same uploading method is used in both cases. I wonder what performance rates you will have if you switch your target proxy to network mode.
Vitaliy S.
Veeam Software
 
Posts: 19564
Liked: 1104 times
Joined: Mon Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov

Re: Veeam vs. vSphere Replication

Veeam Logoby albertwt » Fri Oct 31, 2014 2:23 pm

Cool, many thanks Anton G. for the explanation.
--
/* Veeam software enthusiast user & supporter ! */
albertwt
Expert
 
Posts: 607
Liked: 19 times
Joined: Thu Nov 05, 2009 12:24 pm
Location: Sydney, NSW

Re: Veeam vs. vSphere Replication

Veeam Logoby cffit » Fri Dec 26, 2014 4:23 pm

Can someone update this thread with comparing VEEAM B&R v8 and the current VMware DRaaS offering? I'm currently trying to decide on one or the other and I think that there have been large changes on both sides since this thread was created and debated.
cffit
Expert
 
Posts: 338
Liked: 33 times
Joined: Fri Jan 20, 2012 2:36 pm
Full Name: Christensen Farms

PreviousNext

Return to VMware vSphere



Who is online

Users browsing this forum: No registered users and 7 guests