Discussions specific to the VMware vSphere hypervisor
Post Reply
eversys
Enthusiast
Posts: 36
Liked: 6 times
Joined: Dec 11, 2014 1:09 pm
Full Name: EVERSYS
Contact:

VSSControl: -2147212529 Backup job failed

Post by eversys »

Case # 00721419

We use Veeam Backup & Replication to backup VMs on our VMware ESXi 5.5 host. Job used to work just fine, now we are receiving the following for all Windows VMs:

Failed to prepare guest for hot backup. 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{b2eb2d38-1eac-11e3-b290-806e6f6e6963}\]. Cannot add volume to the set of volumes that should be shadowed. VSS error: VSS_E_UNEXPECTED_PROVIDER_ERROR. Code:0x8004230f 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{b2eb2d38-1eac-11e3-b290-806e6f6e6963}\]. Cannot add volume to the set of volumes that should be shadowed. VSS error: VSS_E_UNEXPECTED_PROVIDER_ERROR. Code:0x8004230f

Any ideas what the problem could be? We use a combination of Windows Server 2003, 2008, XP and Windows 7 VMs.

Thanks for your help.

foggy
Veeam Software
Posts: 20451
Liked: 1949 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: VSSControl: -2147212529 Backup job failed

Post by foggy »

The error is returned by the guest OS components, do you see any related messages in the Windows Event Log on the affected VMs? Have you checked VSS writers/providers status on them? Do you have any 3rd party VSS providers installed there?

eversys
Enthusiast
Posts: 36
Liked: 6 times
Joined: Dec 11, 2014 1:09 pm
Full Name: EVERSYS
Contact:

Re: VSSControl: -2147212529 Backup job failed

Post by eversys »

When the Veeam job runs, our Event logs report VSS errors. On a Windows Server 2008 is full of VSS 12292 and 13 errors. On a Windows Server 2003 the event logs is full of VSS 12292 and 11 errors.
Source: VSS
Event-ID: 12292
Volumeschattenkopie-Dienstfehler: Beim Erstellen der Schattenkopieanbieter-COM-Klasse mit CLSID {790f2886-9889-4c99-8ef5-531add05d044} [0x80070422, Der angegebene Dienst kann nicht gestartet werden. Er ist deaktiviert oder nicht mit aktivierten Geräten verbunden.] ist ein Fehler aufgetreten.
Source: VSS
Event-ID: 13 or 11
Volumenschattenkopie-Dienst-Informationen: Der COM-Server mit CLSID {790f2886-9889-4c99-8ef5-531add05d044} und dem Namen "SW_PROV" kann nicht gestartet werden. [0x80070422, Der angegebene Dienst kann nicht gestartet werden. Er ist deaktiviert oder nicht mit aktivierten Geräten verbunden.]
All services are running. We used to use Symantec System Recovery on all VMs - although the software is still installed the relevant services are deactivated.

foggy
Veeam Software
Posts: 20451
Liked: 1949 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: VSSControl: -2147212529 Backup job failed

Post by foggy » 3 people like this post

If you see Symantec VSS provider in the list provided by the vssadmin list providers command, try to remove Symantec software from one of the VMs and back it up again. 3rd party backup VSS providers can easily cause VSS freeze issues like the one you're reporting.

eversys
Enthusiast
Posts: 36
Liked: 6 times
Joined: Dec 11, 2014 1:09 pm
Full Name: EVERSYS
Contact:

Re: VSSControl: -2147212529 Backup job failed

Post by eversys »

Yes, "Symantec Software VSS Provider" is listed as a VSS provider. Will do as you suggest and keep you updated.

Many thanks

eversys
Enthusiast
Posts: 36
Liked: 6 times
Joined: Dec 11, 2014 1:09 pm
Full Name: EVERSYS
Contact:

Re: VSSControl: -2147212529 Backup job failed

Post by eversys » 4 people like this post

Yes, a deinstallation of SSR worked just fine. Infact, it was enough to reactivate the SSR services - backups in Veeam worked just fine thereafter.

many thanks.

Post Reply

Who is online

Users browsing this forum: No registered users and 26 guests