To diagnose the Volume Shadow Copy service writer problem, run the vssadmin command immediately after the backup failure: Run. Type vssadmin list writers. This command lists the Volume Shadow Copy service writers and the current state of each writer.

When you run a non-component VSS backup (for example, by using Azure Site Recovery (ASR) Agent) against volumes of servers hosting SQL Server 2016 instances, the backup jobs may report failure with the following events logged in the Application Event log.

Fixes an issue in which VSS snapshot restore fails in Windows Server 2012.

In this scenario, the SQL Writer Service can reach a deadlock situation and indefinitely keep locks against an internal system table in master (sys.sysdbreg with object_id 28).

Fixes an issue that generates a "0x0000007E" Stop error. This error occurs when you run a Volume Shadow Copy Service (VSS)-based application on a computer that is running Windows 7 or Windows Server 2008 R2.

Fixes a problem in Windows Server 2008 and in Windows Vista in which a non-persistent snapshot cleanup operation that takes more than three minutes is aborted by VSS.

This article describes an issue in which snapshots are not deleted after you perform a backup operation by using Volume Shadow Copy Service (VSS) in Windows Server 2012 R2.

Apply this hotfix only to systems that are experiencing the problem that is described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

To resolve this issue, install the June 14, 2022 or newer Windows update on the Application Server as well as the File Server. The account used to perform the shadow copy operation is a local account that has Administrator or Backup Operator privileges on the File Server.

Xbox Support ... Xbox Support