1-800-691-1991 | 9am - 8pm ET
EN

SQL VSS Writer is missing: databases will be backed up in crash-consistent state and transaction log processing will be skipped

KB ID: 2095
Product: Veeam Backup & Replication 11
Published: 2016-02-10
Last Modified: 2021-06-24
Languages: FR

Challenge

Job reports warning:

SQL VSS Writer is missing: databases will be backed up in crash-consistent state and transaction log processing will be skipped

Running the command vssadmin list writers shows that 'SqlServerWriter' is not active.

Cause

There are different causes of the issue:

  • the SQL instance has one or more databases with a name starting or ending in a space character. 
  • the account under which SQL VSS Writer service is running doesn't have sysadmin role on a SQL server
  • SQL VSS Writer service stuck in an invalid state
This warning notifying that the "SQL VSS writer is missing" is a courtesy message that is presented to the user when Veeam Backup & Replication detects that the SQL VSS Writer is missing on a server where it was seen previously.

Solution

Below is a list of possible solutions that have been reported to us by customers from previous support cases.

Veeam is not responsible for any issues incurred after making the suggested changes. You are advised to contact and review all setting changes with the respective product support organization.

Reported causes\solutions to fix the SQL VSS Writer not be present on a SQL Server:

  • Use the "Repair" function within Apps & Features for the Microsoft VSS Writer for SQL Server
  • To check if your database has a space in the name you can run the following query on the SQL Server which has the missing SQL VSS Writer. If you notice any spaces in the database names, then you will need to remove the spaces from the database names. (Changing database names may require checking with the software that is using that database to make sure it can be changed to the new name.)
select '#' + name + '#' from sys.databases where name like '% %'
The # shown in the SQL query results makes it easier to spot leading and trailing spaces.
  • Make sure that the user specified in the [Log on as] for the SQL Server VSS Writer service is set as having a sysadmin role (Instructions in KB here: https://www.veeam.com/kb1978)
  • Restart SQL Server VSS Writer service (Instructions in KB here: https://www.veeam.com/kb2041)
  • In the case of SBS machines that are also Domain Controllers, ensure that the SQL Writer is running as a domain administrator and not local system
  • Allow the SQL Writer service account access to the Volume Shadow Copy service via the registry:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\VssAccessControl
    If the DWORD value “NT SERVICE\SQLWriter” is present in this key, it must be set to 1.
    If the Volume Shadow Copy service is running, stop it after changing this registry value. Do not disable the Volume Shadow Copy service, it's default state is Manual.

More information

Microsoft documentation states that the SQL Writer service must run as Local System.

  • In SQL Server 2008R2 and earlier, this means that the writer service account appears to SQL Server as “NT AUTHORITY\System”.
  • In SQL Server 2012 and later, the writer service account appears to SQL Server as “NT Service\SQLWriter”.
KB ID: 2095
Product: Veeam Backup & Replication 11
Published: 2016-02-10
Last Modified: 2021-06-24
Languages: FR

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later
Knowledge base content request
By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you for your interest in Veeam products!
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please go back try again later.