I have 10 days left on my trial license. I am still trying to determine if I want to move forward with using Veeam and Hyper-v. It works great with VMWare but I am having some issues with Hyper-v. From reading the user guide, I am not using the recommended backup approach since I am using the Software VSS provider and I am not offloading the processing using a proxy. I am still doing testing and haven't yet forked over the money for a snapshot license. When I come in, in the morning about a quarter of my vm's are powered down and show "missing" under status. I have to repair them all to reassociate the .vhd's to the vm. The system log on the vm's show "unexpected shutdown" during the backup window with not a whole lot of other information. I am trying to figure out if Veeam is causing these shutdowns but after suspending the job last night, there were no more unexpected shutdowns.
I have 2 questions. The first is, will using the Hardware VSS, and offloading via proxy, resolve these unexpected shutdowns? Secondly, can I achieve a Lan free, Direct SAN Access, backup using Veeam and Hyper-v? I don't see a Direct SAN Access option in the Hyper-v proxy options. In VMWare, I have presented the LUNs to both the vmware hosts and the Veeam backup server and I am under the impression that most of the backup traffic goes over the SAN fabric. My bottleneck ratio in VMWare shows 2% for network.
I believe most of these reliability issues are caused by the relative newness of Hyper-v and CSV's, and not an issue with Veeam itself. For instance, I don't think there is anything I can do in Veeam that would take down and corrupt a VMWare virtual machine.