Integration with Storage Snapshots : Tintri

Availability for the Always-On Enterprise

Integration with Storage Snapshots : Tintri

Veeam Logoby JimmyO » Fri Aug 29, 2014 10:59 am

Working for a global company and implementing Tintri VMstore in 3 regions I really see a need for storage snapshots integration for Tintri.

Sice we also (along with many other Tintri customers) plan to (or use) Veeam to back up all our Tintri VMstores, any priority on this functionality would be appreciated.
JimmyO
Enthusiast
 
Posts: 38
Liked: 2 times
Joined: Sun Apr 27, 2014 8:19 pm

Re: Integration with Storage Snapshots : Vendor Roadmap

Veeam Logoby lorengordon » Mon Sep 01, 2014 12:09 am

+1 for Veeam integration with Tintri snapshots!
lorengordon
Influencer
 
Posts: 23
Liked: 3 times
Joined: Fri Jul 01, 2011 12:50 pm
Full Name: Loren Gordon

Re: Integration with Storage Snapshots : Vendor Roadmap

Veeam Logoby vClintWyckoff » Tue Sep 02, 2014 12:51 pm

+1 for Veeam integration with Tintri VMReplication and VMSnapshots!
vClintWyckoff
Veeam Software
 
Posts: 464
Liked: 104 times
Joined: Sat Oct 27, 2012 1:22 am
Location: Technical Evangelist
Full Name: Clint Wyckoff

Re: Integration with Storage Snapshots : Vendor Roadmap

Veeam Logoby ggrice » Fri Sep 05, 2014 11:45 am 3 people like this post

Thought this may be interesting for some folks. I am running Veeam V7 on ESX5.5 backed by a Tintri T540. I am very happy with the backup speeds we are achieving, I run six jobs per night on an incremental basis, and two during working hours. Here is a pic I took of one of the backups from last night. Roughly 600gb of raw vm size, 35gb of changed data to backup and completed in just over 5 minutes :D We do this five more times every night and every job is running in under 10 minutes.

Image

I checked the Tintri performance at that time and it was practically idling. Of course a lot of this performance is also due to Veeam's compression on the fly, but I can honestly say if you are holding out on buying Veeam or Tintri until there is a software integration - reconsider if you even need to as they work as a really great combo already.
ggrice
Novice
 
Posts: 9
Liked: 3 times
Joined: Fri Aug 16, 2013 8:19 am
Full Name: Geoff Grice

Re: Integration with Storage Snapshots : Vendor Roadmap

Veeam Logoby depps » Fri Sep 05, 2014 1:25 pm

Snapshot integration becomes important when you have busy servers, VMWare snapshots are slow so the ability to leverage fast array snapshots is killer funtionality.

What the max number of snapshots the Tintri can have per VM?

We're evaluating both, I like the Tintri for its NFS/VWmare capabilities but Nimble seems to have more advanced snapshot capability and is cheaper. We want to keep hundreds of snaps of our SQL up to 15 minute increments and Nimble allows for almost unlimited snaps.
depps
Influencer
 
Posts: 20
Liked: never
Joined: Mon Jan 24, 2011 10:16 pm
Full Name: Daniel Epps

Re: Integration with Storage Snapshots : Vendor Roadmap

Veeam Logoby v.Eremin » Fri Sep 05, 2014 1:35 pm

depps wrote:We want to keep hundreds of snaps of our SQL up to 15 minute increments

What you're going to snapshot SQL server every 15 minute? Are you after SQL point in time recovery? Thanks.
v.Eremin
Veeam Software
 
Posts: 13709
Liked: 1026 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin

Re: Integration with Storage Snapshots : Vendor Roadmap

Veeam Logoby depps » Fri Sep 05, 2014 1:45 pm

For historical information and protection against corruption

RPO and RTO is currently seconds with CA/ArcServe RHA

Snapshot schedule/retention will be like this

15 min snaps kept for 1 week
daily's kept for 1 month
weeklies for 6 months
monthlies for 12-24 months
yearlies indefinitely, prob dump to tape or cheap storage a after 1 yr
depps
Influencer
 
Posts: 20
Liked: never
Joined: Mon Jan 24, 2011 10:16 pm
Full Name: Daniel Epps

Re: Integration with Storage Snapshots : Vendor Roadmap

Veeam Logoby robgirard » Fri Sep 05, 2014 2:13 pm 1 person likes this post

+1 for Tintri integration
8)
robgirard
Lurker
 
Posts: 1
Liked: 1 time
Joined: Fri Sep 05, 2014 2:09 pm
Full Name: Rob Girard

Re: Integration with Storage Snapshots : Vendor Roadmap

Veeam Logoby jwdiii » Fri Sep 05, 2014 3:23 pm

+1 for Tintri integration with snapshots an replication
jwdiii
Lurker
 
Posts: 1
Liked: never
Joined: Fri Sep 05, 2014 3:21 pm
Full Name: John Davis

Re: Integration with Storage Snapshots : Vendor Roadmap

Veeam Logoby ggrice » Fri Sep 05, 2014 4:30 pm

depps wrote:Snapshot integration becomes important when you have busy servers, VMWare snapshots are slow so the ability to leverage fast array snapshots is killer funtionality.

What the max number of snapshots the Tintri can have per VM?

We're evaluating both, I like the Tintri for its NFS/VWmare capabilities but Nimble seems to have more advanced snapshot capability and is cheaper. We want to keep hundreds of snaps of our SQL up to 15 minute increments and Nimble allows for almost unlimited snaps.


Hi Depps, Tintri uses the VMware VAAI plug in so VMware snapshots are almost instant, I can snapshot my 1TB exchange VM in under 5 seconds with no degredation to the VM. VAAI completely unloads the servers so like I said Tintri + Veeam it super fast already. My Exchange cluster is on an 8 hour backup rotation, I just checked the Veeam settings, it would be possible to reduce this to every 15 minutes, although that does sound less like a backup requirement and more like a DR style requirement which might be better served with VM replication through Veeam, SRM, or even Tintri replication which happens with zero overhead to your front end infrastructure.
ggrice
Novice
 
Posts: 9
Liked: 3 times
Joined: Fri Aug 16, 2013 8:19 am
Full Name: Geoff Grice

Re: Integration with Storage Snapshots : Vendor Roadmap

Veeam Logoby vClintWyckoff » Fri Sep 05, 2014 5:39 pm

@Daniel- Tintri T650 VMstore supports 50,000 VM Snapshots maximum on OS 3.0. As Geoff mentions, offloading vSphere cloning, snapshots and replication tasks off the hypervisor down to the storage layer completely eliminates all of the vSphere snapshot overhead and issues resulting from it (VM Stun / Commit...etc). I'm sure you're aware that this is much more efficient than the native VMware Hypervisor based snapshots. Nimble snapshots and cloning activities are provided at the entire volume / LUN level where as Tintri DOES EVERYTHING at the individual virtual machine and even individual vDisk layer, including providing dedicated QoS for that said SQL Server. But I'm sure you already knew that too ;)
vClintWyckoff
Veeam Software
 
Posts: 464
Liked: 104 times
Joined: Sat Oct 27, 2012 1:22 am
Location: Technical Evangelist
Full Name: Clint Wyckoff

Re: Integration with Storage Snapshots : Vendor Roadmap

Veeam Logoby mdaltoriob » Fri Sep 05, 2014 5:50 pm

We have 3 sites with Tintri units. 2x540s and 1x650 currently. We are using Veeam to go to secondary storage for longer rentention, but I bet we could do some amazing stuff if we had integration with SAN snapshots.

Has there been any response from Veeam people on this?
mdaltoriob
Lurker
 
Posts: 2
Liked: never
Joined: Wed Aug 27, 2014 2:43 pm

Re: Integration with Storage Snapshots : Vendor Roadmap

Veeam Logoby Gostev » Fri Sep 05, 2014 9:41 pm

mdaltoriob wrote:Has there been any response from Veeam people on this?

Please see my answer here.

And while Tintri clearly lacks market share to be our priority target for integration (note that we look at the actual market statistics, not the amount of +1s in this thread) , I am still curious where exactly do you see the value of Veeam integrating with Tintri? Based on the feedback from actual users on the previous page, Tintri's ability to offload VM snapshots to storage already solves that very same issue our Backup from Storage Snapshot feature is designed to address (namely, impact on production environment from large VM snapshots commits).

Perhaps there could be some lack of understanding here what our integration with storage snapshots is about... I would be happy to clarify this, if needed. Likewise, there might be lack of knowledge of some Tintri drawbacks on my part, too.

But reading through the feedback on the previous page, it sounds like there is absolutely nothing preventing Tintri users to do regular Veeam backups every 15 minutes today, without any sort of special integration. And perhaps the same can be applied to any SSD-based storage, really... because let's admit it - infinite IOPS will chew through anything regardless, even without any "special sauce".
Gostev
Veeam Software
 
Posts: 21611
Liked: 2409 times
Joined: Sun Jan 01, 2006 1:01 am
Location: Baar, Switzerland

Re: Integration with Storage Snapshots : Vendor Roadmap

Veeam Logoby lorengordon » Mon Sep 08, 2014 1:22 am

Apologies, I was unaware that VAAI for NAS would offload a VMware snapshot to the array. My understanding was that the snap primitive was used to clone a VM -- the primitive names are sometimes misleading and confusing. I'm trying to find more information on exactly how the snapshot offload works. VMware KB 1021976 doesn't have nearly enough details. Is the VM still stunned when creating the snapshot? When the snapshot is deleted, is there still the potential for a very long commit period? I'm fairly certain the commit details are not significantly different, based on what I've seen (even though I didn't know I was using the offload feature), and commits are where all our issues have been with VMware snapshots.

As for the feedback on the previous page, we all know that there is a lot more to designing a backup architecture than just the primary storage device. The backup target design and network architecture design are incredibly important, as well. Also, 600GB is only 5% of the T540 capacity. In a rather small environment I was managing previously, we were backing up something like 10TB from a T540, and the backup target was an older DataDomain (daily incrementals and weekly fulls). We had a few very active SQL servers and a couple other high IO systems, and we would regularly have significant issues with backup performance and snapshot commits (and yes, we did have the Tintri VAAI for NAS vib installed to all hosts). The VMstore wasn't working hard enough to be a concern, and thankfully it's per-VM QoS is good enough that no other systems were ever impacted. Throughput issues were typically a result of job configuration + DataDomain, but throughput was secondary. The timing of the application issues we'd encounter could near always be traced to the snapshot commit period. In a much larger environment I helped design, we had EMC Clariion's with hundreds of spindles, and we'd have the same issues with snapshot commits.

In the end, my experience is that if your VMs are sufficiently busy, you will have problems with VMware snapshots, regardless of the storage solution and how fast it is. So yes, I advocate for avoiding VMware snapshots, and offloading snapshots and commits to the storage array entirely.

The ideal workflow to me would be for Veeam to quiesce the VM, then send the Tintri VMstore the command to snapshot the VM, then release the VM, then copy the snapshot from the VMstore to the backup target, then delete the Tintri snapshot. Note the data path there -- from the VMstore to the backup target -- not from the VMstore to the vSphere host to the backup target. Also note in this workflow that there may be very little interaction with vCenter or the vSphere hosts.

I see another use case for Veeam integration with storage/Tintri snapshots, though. It would be wonderful to utilize storage snapshots as the first tier backup, with a backup copy job to copy the snapshots to another storage device. Backups would then be nearly instant, and the backup copy of the snapshot would be "out of band" in a sense so it would not impact performance of the VM in any way.
lorengordon
Influencer
 
Posts: 23
Liked: 3 times
Joined: Fri Jul 01, 2011 12:50 pm
Full Name: Loren Gordon

Re: Integration with Storage Snapshots : Vendor Roadmap

Veeam Logoby mdaltoriob » Mon Sep 08, 2014 3:24 pm

Gostev wrote:
mdaltoriob wrote:Has there been any response from Veeam people on this?

Please see my answer here.

And while Tintri clearly lacks market share to be our priority target for integration (note that we look at the actual market statistics, not the amount of +1s in this thread) , I am still curious where exactly do you see the value of Veeam integrating with Tintri? Based on the feedback from actual users on the previous page, Tintri's ability to offload VM snapshots to storage already solves that very same issue our Backup from Storage Snapshot feature is designed to address (namely, impact on production environment from large VM snapshots commits).

Perhaps there could be some lack of understanding here what our integration with storage snapshots is about... I would be happy to clarify this, if needed. Likewise, there might be lack of knowledge of some Tintri drawbacks on my part, too.

But reading through the feedback on the previous page, it sounds like there is absolutely nothing preventing Tintri users to do regular Veeam backups every 15 minutes today, without any sort of special integration. And perhaps the same can be applied to any SSD-based storage, really... because let's admit it - infinite IOPS will chew through anything regardless, even without any "special sauce".


I guess I am confused here. If I use Veeam to backup VMs that reside on the Tintri that have Tintri snapshots I still get long commits that can cause brief outages. This may be an issue with the secondary storage I am using, but if I were working off of a storage snapshot from the beginning wouldn't I not need to worry about commits on a running VM? When I do a Tintri snapshot that quiesces the VM it stay open for only the briefest possible time. If Veeam could backup from a Tintri snapshot that happens 15 minutes before the job starts then we would not impact production VMs at all from a VMware snapshot perspective. If I am wrong please help me understand.
mdaltoriob
Lurker
 
Posts: 2
Liked: never
Joined: Wed Aug 27, 2014 2:43 pm

Next

Return to Veeam Backup & Replication



Who is online

Users browsing this forum: KevinM and 1 guest