I recently watched a video ("sponsored" on FB) regarding vSphere 6 / Veeam.
In it, there was mention of how this means, essentially, that
1) since Veeam uses VMWare APIs, and
2) since VMWare can now talk more "directly" to the storage via vVols (using VASA "appliance" provided by vendor. In my case, Compellent), that
3) what's possible now is that, instead of a snapshot being committed in the "traditional" manner, a snapshot can basically be a SAN level snapshot, and thus
4) the "commit"/removal of it is basically instant, with little to no performance impact (nearly, if not exactly the same as a "normal SAN snapshot").
In other words, what we seem to have as a possibility is an "end run" around needing to have Veeam ("directly") do the SAN snapshot - since VMWare *can* handle it, and since VMWare can supposedly do a "SAN snapshot" of a vVol via the VASA, therefore...(it seems to me that) Veeam can.
......Is that at all close?
Maybe I have a case of too much wishful thinking here, and that's where I'd like to seek clarification.
Perhaps it's just not quite possible. If it is
, though, this might make my year.
I'm curious because, as is referenced here, Compellent isn't on "the list" of supported SAN-snapshot-capable-vendors w/Veeam.
I'm still relying on VMWare level / VMDK level snapshots, which, as we all know, can take a bit of time to commit in some cases (though certainly not all).
Couple major examples for my environment, where "SAN Snapshot" would help a great deal:
1) We have a few systems which are very "sensitive" to snapshot commits. I've tried to work with the vendor on this, but that's a longer story.
In short, it comes down to this: I can't use Veeam for these systems, at least, not more often than during "downtime" over a weekend.
2) Large file servers. I am not comfortable having to wait potentially *days* for a backup, then potentially another day or more for the snapshot to commit once Veeam is done copying data.
I'm still spending time trying to understand what vVols can mean for me, as it relates to Veeam's integration with VMWare.
I've grasped the importance of the concepts from a "basic" standpoint, and understand where they can be beneficial in many ways.
They would have been a HUGE help for me about 2 years ago, when I had very little time to set up a large set of systems, with a correspondingly large set of LUNs behind them, but I digress.
I guess the "next step" for me is to spin up a fresh machine using vVol(s), or, storage vmotion a test one to a vVol (if that's possible) then see what Veeam does with it.
*IF* what I'm trying to understand here is possible - that Veeam can tell VMWare to take what amounts to a "SAN snapshot," then what we have here is nothing short of amazing
Of course, what would be "really nice" is if I could then storage vmotion a machine into a new set of virtual volumes, and then fully leverage Veeam for these VMs that can't currently handle the "pause" upon snapshot removal/commit.
Another example: http://www.blueshiftblog.com/?p=3806
"...the whole snapshot process can be offloaded to the storage array itself in some cases, providing instant and non-disruptive snapshots.
This is a huge change from vSphere 5 which should allow for backups and snap close operations on highly transactional servers where this might not have been possible in the past. Impact free snapshot (and backuptennesse-vols-fans(2)) operations."