Sql Server Vss Writer
Most backup solutions for Windows use Volume Shadow Copy Service (VSS) to create backup copies of the application or service data. In some cases, the VSS service or one of its writers start to work incorrectly which results in failures during the backup.
I have faced such an problem on Exchange, MSSQL and Hyper-V servers. To quickly recover VSS and its components, I use the following instruction.To detect a failed VSS writer, let’s display the list of VSS writers registered in the system and their status using the vssadmin command.vssadmin list writers. Re-register the VSS components:regsvr32 /s ole32.dllregsvr32 /s oleaut32.dllregsvr32 /s vssps.dllvssvc /registerregsvr32 /s /i swprv.dllregsvr32 /s /i eventcls.dllregsvr32 /s es.dllregsvr32 /s stdprov.dllregsvr32 /s vssui.dllregsvr32 /s msxml.dllregsvr32 /s msxml3.dllregsvr32 /s msxml4.dllvssvc /registerStart the previously stopped services:Net Start SWPRVNet Start VSSMake sure that the error of the problem VSS writer has disappeared.This method of restarting and re-registering of VSS components is effective both on Windows Server 2008 / 2012/ R2 and on Windows Server 2016.
Sql Server Vss Writer And Backup Issues
- When VSS writers on Windows 8 or Windows Server 2012 fail, it could cause backups to fail. To repair VSS writers, the process usually involves using the VShadow utility, but this tool is not available for the above two operating systems.
- Veeam Community discussions and solutions for: A VSS critical writer has failed. I then turned off the Sql Server VSS Writer under Services. VEEAM seems to need.
The SQL Writer Service provides added functionality for backup and restore of SQL Server through the Volume Shadow Copy Service framework. The SQL Writer Service is installed automatically. It must be running when the Volume Shadow Copy Service (VSS) application requests a backup or restore.