Comprehensive data protection for all workloads
mcwill
Enthusiast
Posts: 64
Liked: 10 times
Joined: Jan 16, 2010 9:47 am
Full Name: Iain McWilliams
Contact:

Re: v6 WAN Replication - Wow!

Post by mcwill » Dec 02, 2011 1:43 pm

The initial plan for Veeam when purchased was to use it to maintain our DR site, however replication jobs were just too slow in V4/V5. We therefore used rsyncing of backups to maintain backups offsite with the knowledge that if required there would be a delay in restoring backups to DR environment.

With V6 we can now obtain our original goal of having the DR environment kept up to date automatically.

murdocmk
Influencer
Posts: 24
Liked: 4 times
Joined: Dec 14, 2009 5:10 pm
Contact:

Re: v6 WAN Replication - Wow!

Post by murdocmk » Dec 02, 2011 9:54 pm

Speaking of WAN backups vs. WAN replication ... in v6 should we notice any significant benefit (in terms of backups times and WAN traffic) to using replication vs. a WAN backup? We have customers that are using Veeam for off-site backups and DR and find the recovery time adequate using vPower and restoring VMs. If they simply keep their jobs configured that way in v6 will they be missing out on WAN traffic improvements that replication offers, or are those improvements now essentially the same for replication and backups?

Gostev
SVP, Product Management
Posts: 24017
Liked: 3254 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: v6 WAN Replication - Wow!

Post by Gostev » Dec 02, 2011 10:09 pm

Great question!

All improvement are a part of core engine, so both backup and replication over WAN in v6 are exactly identical in terms of traffic and performance. If they are using Linux target with v5 for off-site backup (which is really the only way to do it efficiently with v5), then they do not need to change anything in order to take advantage of WAN optimizations v6 engine brings.

However, I don't necessarily agree that vPowering-up a backup is good approach. Sure, it's perfect to handle single VM outages, but what if a big part of the site goes down? vPower NFS will not provide sufficient I/O performance for large scale outages. Also, quite frankly, all the new v6 replication functionality (failback, Re-IP) makes the whole experience much more streamlined. It takes just a few clicks to failover a bunch of VMs and have them running on DR site at full speed not constrained by vPower NFS, and then bring them back over to production with another few clicks... you cannot get anything like this with the backups.

tsightler
VP, Product Management
Posts: 5294
Liked: 2146 times
Joined: Jun 05, 2009 12:57 pm
Full Name: Tom Sightler
Contact:

Re: v6 WAN Replication - Wow!

Post by tsightler » Dec 02, 2011 10:17 pm

Just in case it wasn't clear from Anton's post, if they were NOT previously using a Linux target for offsite backups with V5, then with V6 you should add either a Windows or Linux repository on the remote side to optimize the traffic and there will be a huge benefit.

With V6 the traffic compression for replication (proxy->proxy) is identical to backup (proxy->repository), so as long as there is a remote repository of some sort, you get the benefit.

Gostev
SVP, Product Management
Posts: 24017
Liked: 3254 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: v6 WAN Replication - Wow!

Post by Gostev » Dec 02, 2011 10:20 pm

...and since both proxy and repository use the same data mover agent, all other WAN optimizations (multiple connections and enhanced protocol) also apply no matter of what components are "talking" as per Tom's post.

VER
Influencer
Posts: 23
Liked: 4 times
Joined: Jan 16, 2011 10:24 am
Full Name: Wouter
Contact:

Re: v6 WAN Replication - Wow!

Post by VER » Jan 15, 2012 5:35 pm

v5 replication: 20 to 24 hours for a 1 TB fileserver with an already excluded drive for swapfile en temp directory.
v6 replication: between 40 and 50 minutes. This v6 job includes the drive with the temp dir's and has only the swapfile excluded.

Please note that the v5 replication was achieved using push replication to an ESXi target which is not recommended.

Other replication jobs show a similar decrease is running time. :D

tsightler
VP, Product Management
Posts: 5294
Liked: 2146 times
Joined: Jun 05, 2009 12:57 pm
Full Name: Tom Sightler
Contact:

Re: v6 WAN Replication - Wow!

Post by tsightler » Jan 15, 2012 5:48 pm

Assuming you system is Windows then you don't even need to exclude the swapfile, V6 does this automatically.

Gostev
SVP, Product Management
Posts: 24017
Liked: 3254 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: v6 WAN Replication - Wow!

Post by Gostev » Jan 15, 2012 10:53 pm

Here you go, 25 times faster comparing to the "worst case" v5 scenario. Looks like we have over delivered our marketing promise of "10x faster" replication! :D

bdoellefeld
Influencer
Posts: 22
Liked: never
Joined: Nov 02, 2011 5:19 pm
Full Name: Bill Doellefeld
Location: Colorado, USA
Contact:

Re: v6 WAN Replication - Wow!

Post by bdoellefeld » Jan 16, 2012 5:57 pm

SQL 2008 (our primary)
ver. 5: would take 14 hours
ver. 6: < 1 hour

Impressed!

Post Reply

Who is online

Users browsing this forum: Bing [Bot], Google [Bot], Karinne, razorslinky, TGacs and 25 guests