by Vitaliy S. » Thu Mar 19, 2015 11:23 am people like this post
In order to have a single snapshot for VMs in the job, your VMs should reside on the same host and on the same volume. In the config above, I see that you can process VM-DC and VM-Print from the same VSS snapshot. Do you see a different behavior for these VMs?
by RGijsen » Tue Feb 02, 2016 7:57 am people like this post
Hi, I'm also struggling with MSA2040 (fibrechannel though) and Veeam. 2012R2 hosts, offhost proxy 2012R2 as well. I am running the latest firmware already (GL220R005, released january 15th 2016) and CAPI and VSS driver 188.8.131.52 (januari 22th 2016), which are available for 2012R2 as well. I keep running into extremely slow 'pickups' of the snapshots. The snapshot itself is created in a few seconds, but then Veeam drops errors like:
2-2-2016 01:15:06 :: Failed to create snapshot (HP MSA 1040/2040 VSS Provider) (mode: Veeam application-aware processing with failover) Details: Unknown status of async operation The shadow copy provider had an error. Check the System and Application event logs for more information. --tr:Failed to create VSS snapshot. --tr:Failed to perform pre-backup tasks.
No obvious errors show up (to me that is) on either the host or guest. Now I don't want to capture your thread but what I wonder is you are talking about VDS drivers as well. VDS is superseeded by SM-API. Still VDS drivers can be used. I can't find anything on VDS in the Veeam manuals at all. Do I need to install the VDS drivers?
by jazzoberoi » Sun Feb 21, 2016 10:29 pm people like this post
We keep getting the following too.
20/02/2016 8:01:32 PM :: Failed to create snapshot HP MSA 1040/2040 VSS Provider on Hyper-V Off-Host Backup Proxy (mode: Veeam application-aware processing with failover) Details: Failed to prepare for backup Another shadow copy creation is already in progress. Wait a few moments and try again. --tr:Failed to create VSS snapshot. --tr:Failed to perform pre-backup tasks.
Can someone from Veeam please explain what is the cause for this and what can we try to fix this ?