Failed to create VSS snapshot

How much free space is on each of the drives you are trying to back up on your computer?

Hi ​@goose_ws ,

Have you checked the following article?

https://www.veeam.com/kb1794

Regards

Chalid

C:\ is at 205 GB free, 725 GB used, of 930 GB total (~22% free, ~78% used)

I have another disk attached, but it’s not assigned any drive letters/mount points in Windows, as it’s a Linux installation I dual boot with. It does have one 4 GB FAT32 partition that I suppose Windows could read/see? I’m not sure how much space is in use, on that partition.

Based on the size of your disk and the working room needed for VSS I am not sure 205GB free will suffice.  You can specify where VSS saves snapshots and can move it off C drive.  Might be something to try.

​@goose_ws - it looks like ​@CMF and ​@Chris.Childerhose are spot on. The KB Chalid shared should help as it has the exact error code listed in the output you shared initially. Try to follow the KB and see if that resolves your issue. Keep us posted.

Best.

I freed up a significant amount of space:

However, backup attempts still fail with the same error. If more space is required, could I specify my SMB share as the location to use for VSS snapshots? Looking at the article that ​@CMF linked, I don’t see anything about using a non-local disk. I suspect replacing 

/on=Z:

with

/on=\\192.168.2.100\veeam

Might work? But I’m not sure how/where to supply the password for that destination, as it’s different credentials than any local user.

I freed up a significant amount of space:

However, backup attempts still fail with the same error. If more space is required, could I specify my SMB share as the location to use for VSS snapshots? Looking at the article that ​@CMF linked, I don’t see anything about using a non-local disk. I suspect replacing 

/on=Z:

with

/on=\\192.168.2.100\veeam

Might work? But I’m not sure how/where to supply the password for that destination, as it’s different credentials than any local user.

You still need the used space plus working room.  Need to investigate VSS more and settings, etc.

I suggest checking for any VSS-related issues by running the following command when the job fails:

Vssadmin list writers

There might be a stuck snapshot. You can check for this using:

vssadmin list shadows  

This will help identify any VSS-related errors or incomplete snapshots.

In the past, I encountered a similar issue caused by another backup solution using the same VSS service.

To check if another system or backup application is utilizing VSS, run:

Vssadmin list providers

Hi, 

Please test VSS outside of Veeam as per KB 1980: https://www.veeam.com/kb1980

Observe the section for Veeam Agent for Windows, and see if manual VSS creation with all of the same volumes from the logs works.

Start with just one volume, see if it works, and if so, add another until it fails. Then test the most recently added volume to see if it fails when tested solo. Test the rest of the volumes afterwards without the suspect volume.

(Remember to clean up any leftover disk shadows)

This won’t fix the issue for you, but it will at least let you know which volume VSS is cranky about -- if it’s the attached but not mounted disk, then try disconnecting it and see if it works. I do suspect the FAT32 volume is getting detected by the Veeam Agent, but your logs should tell you that (KB will point you where to check)

​@goose_ws  Can you check the status of your VSS writers by running the following command.

“vssadmin list writers”

Please confirm the "State" and "Last error" reported for each writer. This can help identify if any VSS writer has failed and the error message might help troubleshooting in right direction 

Also, run the following command to review shadow copy storage:

“vssadmin list shadowstorage”
This will show the shadow copy storage associations on each volume. Alternatively, you can right-click the volume > Properties > Shadow Copies tab to check the allocated and maximum shadow copy storage space on the volume. You can increase the maximum space if needed. 

Following the guidance in the KB, I resized my shadowstorage (I went for unlimited), but my veeam still fails:

PS C:\Users\goose> vssadmin list shadowstorage
vssadmin 1.1 - Volume Shadow Copy Service a
dministrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.
Shadow Copy Storage association
   For volume: (C:)\\?\Volume{52d2ff6b-ac17-4f60-8137-4d13c8ce25e2}\
   Shadow Copy Storage volume: (C:)\\?\Volume{52d2ff6b-ac17-4f60-8137-4d13c8ce25e2}\
   Used Shadow Copy Storage space: 8.88 GB (0%)
   Allocated Shadow Copy Storage space: 9.19 GB (0%)
   Maximum Shadow Copy Storage space: 9.30 GB (0%)

PS C:\Users\goose> vssadmin resize shadowstorage /for=C: /on=C: /maxsize=UNBOUNDED
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.
Successfully resized the shadow copy storage association

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

Shadow Copy Storage association
   For volume: (C:)\\?\Volume{52d2ff6b-ac17-4f60-8137-4d13c8ce25e2}\
   Shadow Copy Storage volume: (C:)\\?\Volume{52d2ff6b-ac17-4f60-8137-4d13c8ce25e2}\
   Used Shadow Copy Storage space: 2.74 GB (0%)
   Allocated Shadow Copy Storage space: 3.22 GB (0%)
   Maximum Shadow Copy Storage space: UNBOUNDED (1845881493%)

PS C:\Users\goose> 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: {0ab5d2d2-bef7-42d8-88f4-d172e3ca310d}
   State: [1] Stable
   Last error: No error

Writer name: 'MSSearch Service Writer'
   Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
   Writer Instance Id: {1f0a21d6-2eac-4f16-97e8-37843b034be6}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {05c500ce-ae44-406f-83d0-6a24931cba22}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {7896760a-bc80-4cd8-b6d6-45b4808ec7fe}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {34690e85-4144-4c52-b6c6-bddc4b52df4c}
   State: [1] Stable
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {51ec4973-e8ac-4281-aaa1-50474917b690}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {118bcd9c-8e93-4f58-91d7-39562417ae58}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {cb243387-f19a-45e7-8c16-c6adccc29692}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {8ebc97ee-1b18-40f0-9a22-e2f70e9f8a31}
   State: [1] Stable
   Last error: No error

PS C:\Users\goose> 

Kindly take a look at Window Events Viewer for other possible reasons (vss related errors). Here is a KB describing your error code you have shared: https://www.veeam.com/kb1794 Also, ensure your box and 3party applications are correctly patched due to VSS interference etc.

From the job log as shown in the KB, can you show the list of volumes that were detected?

In your post above, all I see is that the shadow copy storage was set to unbounded and the vss writers/shadow storage were listed, but the purpose of the KB was to see how to check which volumes Veeam Agent for Windows was requesting a VSS snap for and to test using the same KB article.

Main point is to figure out which volume VSS does not like and which disk it’s on, and to do that you’ll need to check the Veeam Agent logs as mentioned in the KB, compare the found volumes to the volumes you have in Windows, and then test VSS on each volume one by one till you find the problematic volume.

If it’s on the unmounted disk, then that disk should be disconnected I suppose. 

If it’s on the System Volume, probably it’s best to check with Support at that point, the System Volume must succeed with VSS, but unclear why it’s not.