Hi ​@robns ,

have you already checked the Windows event log for any particular errors regarding VSS at the times the backup fails?

I think you can use a powershell command on your pre-exec option, so you can see which process are running before backup starts, this will help you to find the process.
 

Hi Andre,

Thanks, that’s useful to know I can run a script in the backup job settings. The problem is that I know that the VSS service is running at backup sometimes, that’s what is causing the error. What I don’t know how to do is find out what is triggering the service, what is starting the service, then keeping it running.

So, I need to detect what other process or program is manually starting the VSS service.

Any ideas?

Have you checked the Windows event viewer?

What is the scenario? Windows OS, Veeam Agent/VM backup, application aware, etc..

You can try this KB for VSS diagnostic: https://www.veeam.com/kb3164

Literally nothing in the event viewer, been down that route.

Windows server 2019 STD. VMWare backup, application aware.

I did a test run of the vsstrace utility. It outputs massive amounts of log data. Not sure how useful or easy it’s going to be to utilise it.

Hi ​@robns to resolve this issue follow these steps:

Kindly note that all commands should be in the command prompt run as an admin.

net stop vss  
net start vss  

Also, restart the Microsoft Software Shadow Copy Provider service.

net stop swprv  
net start swprv  

Check for Stuck Snapshots with the below command.

vssadmin list shadows  

If any snapshots are listed, delete them using.

vssadmin delete shadows /all  

If the issue persists restart the server to clear any stuck VSS instances.

I’ve used all these commands in various forms tackling this issue. I’ve set a scheduled task to output the VSS list shadows command just before backup to see if something is stuck at that particular time.

It is very strange that you do not see vss-related events in the Windows event log.

At this point I suggest you open a case to Veeam support to investigate the issue further.

Keep us updated.

Download Process Explorer from Microsoft SysInternals team, it is a better Task Manager. When VSS is running run ProcExp64 and find the VSS process, right click the VSS process and select properties, there will be a field labeled Parent, it will tell you what launched the process.

OK, thanks for that.

I started the VSS service manually then did what you said. The parent says services.exe. I’m hoping that whatever is triggering it will show up as the parent and not services.exe by default?!

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

vssadmin list writers

This will help identify any VSS errors.

In the past, I encountered a similar issue (VSSControl: -2147212522 Backup job failed), which was caused by another backup solution using the same VSS service.

To check if another system, such as a different backup application, is utilizing VSS, run:

vssadmin list providers

You can check this link—I used it to resolve my issue, and I hope it helps you.

https://answers.microsoft.com/en-us/windows/forum/all/backups-fail-volume-shadow-copy-errors-22-12292/1db3215c-af3c-45fa-a061-5f8bab823b5e

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

Vssadmin list writers

This will help identify any VSS errors.

In the past, I encountered a similar issue (VSSControl: -2147212522 Backup job failed), which was caused by another backup solution using the same VSS service.

To check if another system, such as a different backup application, is utilizing VSS, run:

Vssadmin list providers

You can check this link—I used it to resolve my issue, and I hope it helps you.
https://answers.microsoft.com/en-us/windows/forum/all/backups-fail-volume-shadow-copy-errors-22-12292/1db3215c-af3c-45fa-a061-5f8bab823b5e

Also, look at ths link

https://learn.microsoft.com/pt-br/windows-server/administration/windows-commands/vssadmin-list-writers

Hi,

Thanks for the suggestions. I have used the two VSSadmin commands quite a bit with this issue so far.

The issue occurred last night and I was able to see that the VSS service was running just before backup. lt didn’t stop when I tried to stop it. After that I checked the app log and found the following

--------------------------------------------------------------------------------------------------------------------------Event ID: 12293
Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details GetSnapshotProperties({e92596a3-a3e3-40ac-bc72-9b6d9cea2026}) )hr = 0x800706b5, The interface is unknown.

]. 

Operation:

   Executing Asynchronous Operation

Context:

   Current State: DoSnapshotSet

I used Process Explorer to see what the parent process was and as expected, it just says services.exe.

I did a list providers check and got this:

Provider name: 'Microsoft File Share Shadow Copy provider'
   Provider type: Fileshare
   Provider Id: {89300202-3cec-4981-9171-19f59559e0f2}
   Version: 1.0.0.1

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

I was reading around and someone suggested that there should only be the 1.0 provider (in the registry)

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers