Is there any way to run Veeam along another VSS provider?

[bunger]

I have 2 backup methods in place for a client and want to leave it that way. One is Veeam and the other is a solution that utilizes the ShadowCraft VSS provider.

I am backing up 7 virtual servers, 2 of which are 2k8 Std and one is SBS 2011. One of my 2k8 servers is backing up successfully with both applications in place. However, my SBS 2011 and the other 2k8 servers are grumpy about having the StorageCraft VSS provider in place.

The 2k8 Std Server reports:
6/28/2014 2:33:04 AM :: Error: VSSControl: -2147212529 Backup job failed.
Discovery phase failed.
Cannot add volumes to the snapshot set.
Cannot add a volume to the snapshot set. Volume name: [\\?\Volume{8c3881d3-9ae4-11e1-be12-806e6f6e6963}\].
Cannot add volume to the set of volumes that should be shadowed.
VSS error: VSS_E_UNEXPECTED_PROVIDER_ERROR. Code:0x8004230f

The SBS 2011 reports:
6/28/2014 2:31:06 AM :: Unable to release guest. Error: Unfreeze error: [Backup job failed.
Cannot create a shadow copy of the volumes containing writer's data.
A VSS critical writer has failed. Writer name: [NTDS]. Class ID: [{b2014c9e-8711-4c5c-a5a9-3cf384484757}]. Instance ID: [{ecb0265d-2226-4a2a-8b22-fa72fdd76994}]. Writer's state: [VSS_WS_FAILED_AT_POST_SNAPSHOT]. Error code: [0x800423f4].]

Is there any way around these errors such that I can continue to use both backup solutions? It seems there should be as the other Win2k8 Std server is backing up successfully with both providers installed...

Thanks in advance!

[Vitaliy S.]

This error message is returned by Windows server, that is unable to prepare itself for hot backups, Veeam does not control this process.

Can you please check Windows Event log on servers that have this error message? Secondly, check VSS writers and providers status on the VM that has successful backups and the ones that have this issue. Also I wonder whether you have the same entries of providers and writers on all these VMs.

[Gostev]

3rd party VSS providers are known to cause VSS processing issues, unfortunately normally there is no way to make Veeam work with them present, and uninstalling them is usually the only option. Thanks.

[bunger]

Rebooting the Win2k8 Std server fixed its issue and Veeam is once again backing it up.

Unfortunately, my SBS 2011 server is still unhappy.

[Gostev]

Bill, please do not post log snippets on the forum, as requested when you click New Topic. Instead, please follow the procedure explained there to get us the debug logs package, and include the support case ID here. Thanks!