Veeam and the HP MSA VSS Provider

by
After upgrading our Hyper-V failover cluster nodes from Windows Server 2012 to Windows Server 2012 R2, and upgrading the HP VSS hardware provider, I found that that any job log which showed, “Using source proxy NODE01” or NODE03 in Veeam B&R resulted in this error:
________________________________________________________________________________
2/7/2015 9:08:46 PM :: Unable to create snapshot (HP MSA 1040/2040 VSS Provider) (mode: Veeam application-aware processing). Details: Failed to check whether provider ‘{9d09666c-5cf8-45ca-9294-127c95562094}’ supports shadow copies on the volume ‘\?Volume{151beef4-849d-4d6e-9580-701765731e08}’.
The shadow copy provider had an error. Check the System and Application event logs for more information.
–tr:Failed to add volumes to the snapshot set.
–tr:Failed to perform pre-backup tasks.
________________________________________________________________________________
Jobs showing “Using source proxy NODE02” or NODE04 were able to create the snapshot using the HP hardware provider. This is what got 01 and 03 working like 02 and 04:
1.      Drained VMs from node.
2.      Uninstalled these HP array-specific software installs from the affected nodes:
a.      VDS Provider
b.      VSS Provider
c.      CAPI Proxy
3.      Restarted Volume Shadow Copy service on the affected nodes.
4.      Ran “vssadmin list providers” on the affected nodes to make sure that the HP hardware provider was not present, if it was I deleted its entry from HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesVSSProviders.
5.      If necessary, restarted Volume Shadow Copy service on the affected nodes then ran “vssadmin list providers” on the affected nodes to make sure that the HP hardware provider was not present.
6.      Un-paused the affected nodes and let the drained VMs return to the affected nodes.

 

7.      Successfully ran a warning-free backup of VMs that were on 01 and 03.