Discussions specific to the VMware vSphere hypervisor
Post Reply
ro.Reen
Influencer
Posts: 14
Liked: never
Joined: May 07, 2014 7:07 am
Full Name: Rene
Contact:

VSSControl: -2147212500 Backup job failed.

Post by ro.Reen » Mar 03, 2015 7:55 am

Hi,

well, I love veeam! Everything is fine, till a few weeks ago: Veeam stopped backing up 1 drive from 1 vm. All other vm's still work. Had this problem with b&r 7, so I upgraded to 8. Applied all patches... A few weeks ago it worked...

The VM is a Windows Server 2012 R2:

Code: Select all

C:\Windows\system32>VSSADMIN LIST WRITERS
vssadmin 1.1 - Verwaltungsbefehlszeilenprogramm des Volumeschattenkopie-Dienstes

(C) Copyright 2001-2013 Microsoft Corp.

Verfassername: "Task Scheduler Writer"
   Verfasserkennung: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Verfasserinstanzkennung: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "VSS Metadata Store Writer"
   Verfasserkennung: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Verfasserinstanzkennung: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "Performance Counters Writer"
   Verfasserkennung: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Verfasserinstanzkennung: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "System Writer"
   Verfasserkennung: {e8132975-6f93-4464-a53e-1050253ae220}
   Verfasserinstanzkennung: {2d4a4e9b-a8f7-4428-ac83-6da30fdc59a0}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "WIDWriter"
   Verfasserkennung: {8d5194e1-e455-434a-b2e5-51296cce67df}
   Verfasserinstanzkennung: {2a8a5956-471d-41fd-b2da-f415778d980a}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "Shadow Copy Optimization Writer"
   Verfasserkennung: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Verfasserinstanzkennung: {a6f07371-30ff-456a-a4af-1b57ec88ee7a}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "BITS Writer"
   Verfasserkennung: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Verfasserinstanzkennung: {4684e1c2-e803-409f-8dfd-0f000c40388f}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "ASR Writer"
   Verfasserkennung: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Verfasserinstanzkennung: {97175211-4a9d-4995-9d2b-746c43145df5}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "IIS Config Writer"
   Verfasserkennung: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Verfasserinstanzkennung: {482a6316-b3be-4202-ad32-3db1017f1a09}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "Registry Writer"
   Verfasserkennung: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Verfasserinstanzkennung: {8f5e42bf-7f48-460a-aaea-aa8c63f2bd86}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "COM+ REGDB Writer"
   Verfasserkennung: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Verfasserinstanzkennung: {f00c6066-d002-40ea-ac96-72b38d231944}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "MSSearch Service Writer"
   Verfasserkennung: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
   Verfasserinstanzkennung: {46d3503f-e73f-47a8-8e05-37f39b4c538e}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "WMI Writer"
   Verfasserkennung: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Verfasserinstanzkennung: {17a67007-4417-459b-b93e-c1aa7dd3ed29}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler

Verfassername: "TermServLicensing"
   Verfasserkennung: {5382579c-98df-47a7-ac6c-98a6d7106e09}
   Verfasserinstanzkennung: {814351d9-49af-476d-9fed-4acc6df60a4e}
   Status: [1] Stabil
   Letzter Fehler: Kein Fehler


C:\Windows\system32>VSSADMIN LIST PROVIDERS
vssadmin 1.1 - Verwaltungsbefehlszeilenprogramm des Volumeschattenkopie-Dienstes

(C) Copyright 2001-2013 Microsoft Corp.

Anbietername: "Microsoft File Share Shadow Copy provider"
   Anbietertyp: Dateifreigabe
   Anbieterkennung: {89300202-3cec-4981-9171-19f59559e0f2}
   Version: 1.0.0.1

Anbietername: "Microsoft Software Shadow Copy provider 1.0"
   Anbietertyp: System
   Anbieterkennung: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Version: 1.0.0.7


C:\Windows\system32>
So as you can see: I think VSS is ok, but still getting this error:
Error: VSSControl: -2147212500 Backup job failed. Discovery phase failed. Cannot add volumes to the snapshot set. Cannot add a volume to the snapshot set. Volume name: [\\?\Volume{2dbfc885-dff0-11e3-9404-0050568550e4}\]. Cannot add volume to the set of volumes that should be shadowed. VSS error: . Code:0x8004232c

Any idea?
Thanks!

Vitaliy S.
Product Manager
Posts: 22442
Liked: 1442 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: VSSControl: -2147212500 Backup job failed.

Post by Vitaliy S. » Mar 03, 2015 10:16 am

Hi,

It seems like there is an issue with VSS provider, have you checked Windows Event log for more info? Aslo, please include your case ID (as it is advised by our forum rules), otherwise this topic will be removed by a moderator.

Thanks!

ro.Reen
Influencer
Posts: 14
Liked: never
Joined: May 07, 2014 7:07 am
Full Name: Rene
Contact:

Re: VSSControl: -2147212500 Backup job failed.

Post by ro.Reen » Mar 03, 2015 11:08 am

Hi!

Well: Didn't open a support case, so there is no case ID. Should I?

And: Yes, I checked the Windows Event Log. Nothing interesting so far. Is there a special folder to check?

Vitaliy S.
Product Manager
Posts: 22442
Liked: 1442 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: VSSControl: -2147212500 Backup job failed.

Post by Vitaliy S. » Mar 03, 2015 11:58 am

Yes, please open a case with our team, as they might have seen it previously and can provide you with a solution.

alanbolte
Expert
Posts: 635
Liked: 172 times
Joined: Jun 18, 2012 8:58 pm
Full Name: Alan Bolte
Contact:

Re: VSSControl: -2147212500 Backup job failed.

Post by alanbolte » Mar 04, 2015 5:16 am

0x8004232C translates to VSS_E_NESTED_VOLUME_LIMIT, which seems to suggest you're trying to shadow copy volumes within other volumes.

ro.Reen
Influencer
Posts: 14
Liked: never
Joined: May 07, 2014 7:07 am
Full Name: Rene
Contact:

Re: VSSControl: -2147212500 Backup job failed.

Post by ro.Reen » Mar 04, 2015 7:58 am

Hi!

What does that mean: I'm trying to shadow copy volumes within other volumes?

I'm trying to backup a Terminalserver. So the users got their own container with personal files. May be that the problem? Any suggestions?

Thanks!

ro.Reen
Influencer
Posts: 14
Liked: never
Joined: May 07, 2014 7:07 am
Full Name: Rene
Contact:

Re: VSSControl: -2147212500 Backup job failed.

Post by ro.Reen » Mar 04, 2015 8:02 am

Case #00822170

arjennap
Lurker
Posts: 1
Liked: never
Joined: Nov 13, 2013 9:21 am
Contact:

Re: VSSControl: -2147212500 Backup job failed.

Post by arjennap » Jun 03, 2015 8:30 am

I had the same problem and the easy fix was to restart de vss services.

Post Reply

Who is online

Users browsing this forum: No registered users and 11 guests