VSS snapshot error

[Edvvde]

Dear community,

Everytime I try to run a backup with Veeam Agent for Windows I get the following error:

12.01.2020 21:58:00 :: Creating VSS snapshot Error: Failed to create snapshot: Backup job failed. Discovery phase failed. Cannot add volumes to the snapshot set. Cannot add a volume to the snapshot set. Volume name: [\\?\Volume{2b4dc0eb-596e-4a21-868a-b3d0ae6f9813}\]. Cannot check whether volume supported by the system software provider. VSS error: VSS_E_UNEXPECTED_PROVIDER_ERROR. Code:0x8004230f

12.01.2020 21:58:09 :: Processing finished with errors at 12.01.2020 21:58:09

Support case id: 03949539

Thanks for all of your answers in advance.

[Egor Yakovlev]

Hi and thanks for sharing case ID.
While waiting for support reply, I would also check for errors (elevated CMD) here:

Code: Select all

vssadmin list writers > C:\vsswriters.txt
vssadmin list providers > C:\vssproviders.txt
vssadmin list shadows > C:\vssshadows.txt
vssadmin list shadowstorage > C:\vssshadowstorage.txt

and tried to perform VSS snapshot manually using this KB.
/Thanks!

[PetrM]

Hello!

One more question: do you use some third party tools to backup the same server?
0x8004230f code generally means that the backup process could not initialize due to a third party VSS Provider component installed on the system.

You will see this information in "vssadmin list providers" output suggested above.

Thanks!

[Edvvde]

Hi and thanks for your answers. The cmds above I already tried before. No other backup software, no other vss provider. Its a Windows 10 Pro 1909 18363.535 Client.
Here is the result of the commands above:

vssadmin 1.1 - Verwaltungsbefehlszeilenprogramm des Volumeschattenkopie-Dienstes
(C) Copyright 2001-2013 Microsoft Corp.

_____________


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

vssadmin 1.1 - Verwaltungsbefehlszeilenprogramm des Volumeschattenkopie-Dienstes
(C) Copyright 2001-2013 Microsoft Corp.

Es wurde keine Ergebnisse fr die Abfrage gefunden.


_______


vssadmin 1.1 - Verwaltungsbefehlszeilenprogramm des Volumeschattenkopie-Dienstes
(C) Copyright 2001-2013 Microsoft Corp.

Es wurde keine Ergebnisse fr die Abfrage gefunden.


______



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: {f430b8f0-3b94-452b-ab45-38c3d3397c0f}
Status: [1] Stabil
Letzter Fehler: Kein Fehler

Verfassername: "SqlServerWriter"
Verfasserkennung: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Verfasserinstanzkennung: {59823f72-54be-41b3-80b8-ea61fc94e6f9}
Status: [1] Stabil
Letzter Fehler: Kein Fehler

Verfassername: "ASR Writer"
Verfasserkennung: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Verfasserinstanzkennung: {2dd8e24d-cdde-4c24-beda-66f7deaa9678}
Status: [1] Stabil
Letzter Fehler: Kein Fehler

Verfassername: "Shadow Copy Optimization Writer"
Verfasserkennung: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Verfasserinstanzkennung: {2e1cc520-55b2-4838-a8ef-1d88a4464210}
Status: [1] Stabil
Letzter Fehler: Kein Fehler

Verfassername: "Registry Writer"
Verfasserkennung: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Verfasserinstanzkennung: {7f4b0430-440b-4036-943b-1b0b5f77fc68}
Status: [1] Stabil
Letzter Fehler: Kein Fehler

Verfassername: "COM+ REGDB Writer"
Verfasserkennung: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Verfasserinstanzkennung: {a5407a5d-4223-48cb-9e86-030837cb6e53}
Status: [1] Stabil
Letzter Fehler: Kein Fehler

Verfassername: "WMI Writer"
Verfasserkennung: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Verfasserinstanzkennung: {58c317a5-b176-4117-9b69-91b06d436dfe}
Status: [1] Stabil
Letzter Fehler: Kein Fehler

Verfassername: "MSSearch Service Writer"
Verfasserkennung: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
Verfasserinstanzkennung: {7f280883-5161-4640-942a-0114c354ccab}
Status: [1] Stabil
Letzter Fehler: Kein Fehler



Thanks in advance.

[PetrM]

Thanks for reply!

I'd suggest to continue working with support team because our possibility to troubleshoot technical issues via forum is quiet limited.
Have you tried to follow the instructions from the KB mentioned above to create VSS snapshot manually?

Thanks!

[lramirez.sengua]

i have the same problem
1/15/2020 9:29:57 PM :: Error: Failed to create snapshot: Backup job failed. Discovery phase failed. Cannot add volumes to the snapshot set. Cannot add a volume to the snapshot set. Volume name: [\\?\Volume{ec84fd9d-0000-0000-0000-602200000000}\]. Cannot check whether volume supported by the system software provider. VSS error: VSS_E_UNEXPECTED_PROVIDER_ERROR. Code:0x8004230f

Someone who was fix this?

[Egor Yakovlev]

Same as above, please:
- check status of VSS Writers(should be state [1] Stable),
- check list of VSS Providers(should be no 3rd party leftover ghosts),
- check DiskShadow for existing VSS Snapshot(leftover),
- try to perform VSS Snapshot manually via DiskShadow,
- finally, open a support ticket to work it out with an engineer guidance.
\Thanks!

[Zweistein]

Hello Edvve,
frist Restart your Windows 10.
second, please check if you have a size limit in the settings for the drive snapshot.

[CSSDan]

Did you get this figured out? Mine started this on the 12th as well. I believe it was right after the MS updates applied. I've tried backing up 4 different local drives, tried creating new jobs, (disk, volume, file) etc., and regardless of which drive I choose but same error. VSS itself manually works so it seems something changed that the agent doesn't like.
For fun I tried (after I couldn't get Veeam to backup) installing another backup program which also uses VSS and it works fine. Agent still doesn not.

[Egor Yakovlev]

MS update might have bumped Windows version to an unsupported by currently installed agent.
What kind of OS build you are running and what version of Veeam agent is present?

[CSSDan]

I'm on Windows Version 10.0.19041.746 and client version 4.0.1.2169. I tried a repair of the client first and then did a complete uninstall and reinstalled the client but the same issue continues.

[Egor Yakovlev]

Well without agent logs its a guessing game.
Toss a support ticket ID here and upload C:\ProgramData\Veeam\Endpoint from failing agent machine to it.
/Thanks!

[tittan]

Yesterday I had the same problem with a fresh new 20H2 19042.870 Windows 10 Pro VMWare VM and the last 5.0.0_4301 Veeam Endpoint Backup for Windows in free mode. Heach time the configured backup started it don't go further 0% and fails. After repairing the System Restore Service following this https://www.youtube.com/watch?v=CwkPD6l1Yew and applying the .reg file given in the video I rebooted the VM and was able to create a restore point and veeam begin to work with no more problems. Any help please ask here and I can help.