Creating VSS snapshot Error: VSS_E_VOLUME_NOT_SUPPORTED

[bdoe]

I have several workstations failing backup with the following error:

Code: Select all

6/13/2017 3:05:03 PM :: 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{1062a7ce-1a89-44d0-9b1f-b1c96bd62e3a}\]. Cannot add volume to the set of volumes that should be shadowed. VSS error: VSS_E_VOLUME_NOT_SUPPORTED. Code:0x8004230c 

All of the affected systems are Windows 10; some are running 1511, some are 1703. Some are Veeam Endpoint 1.5, some have been updated to Agent 2.0. They're all targeting repositories on a Veeam server, which is at the latest version. Offhand it may be related to rebooting, but I'm not sure if last month's updates caused it; updates are managed by WSUS so today's haven't hit them. I have more to try in the morning but was hoping someone could point me in the right way.

[Mike Resseler]

This is mostly when one of the VSS writers or providers have gone crazy.

Can you do a vssadmin list writers and vssadmin list providers to see if there is more information?

[bdoe]

Here's the output from both of those:

Code: Select all

PS C:\WINDOWS\system32> vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.

Writer name: 'Task Scheduler Writer'
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error

Writer name: 'VSS Metadata Store Writer'
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error

Writer name: 'Performance Counters Writer'
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {641c82fe-2b74-47c9-b990-6205fadd11e9}
   State: [1] Stable
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {7857bed8-0f91-4ee2-af51-cb97eb9e8309}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {13454dc3-00cc-4d93-be24-22bd8ac2f9d4}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {0a2b0dcf-baa4-491a-b84c-111f5b29c465}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {118355c8-f1e7-4174-89ac-05f1fced18ea}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {656a444c-5ce4-4943-8a8a-c927dfc56ebe}
   State: [1] Stable
   Last error: No error

Writer name: 'MSSearch Service Writer'
   Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
   Writer Instance Id: {6e40c24d-27f5-4be0-8f9a-7a3bf70b00e0}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {f4b9f8ea-7ee8-4c4a-96a1-eeb4b81f0301}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {c6b52283-901d-4062-bd7e-e14a14a08d34}
   State: [1] Stable
   Last error: No error

PS C:\WINDOWS\system32> vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.

Provider name: 'Microsoft Software Shadow Copy provider 1.0'
   Provider type: System
   Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Version: 1.0.0.7

PS C:\WINDOWS\system32>

I also checked, one machine that's working has only been up for two days, so it's not reboot-related. Also, the Veeam console shows 9 machines are failing.

[bdoe]

I opened a case with support, it turned out the recovery partition on the affected machines was filling up and causing the error. Changing the job to leave that out has them running again. These machines are all imaging with volume licensing with no OEM partitions left behind, so I'm not sure what caused it, but at least Veeam is happy again.

[Mike Resseler]

Glad to hear that it is solved. And I have maybe an idea what is happening. That recovery partition is probably something what was built through the OEM. For example, a Microsoft Surface has a recovery partition and it is windows 10 that uses this (you can revert or reset in the control panel, it get's the data from that). I assume it is that mechanism that fills it up when you take a backup because you are actually taking a snapshot. Since you are using VAW, you might consider looking into this and remove the recovery partition (not necessary anymore as you have already backup (and a better one ) and get some additional GB free on the drive (First thing I always do with a surface since those SSD's on the lower end models are small, the additional 5 GB is a lot for me )