Veeam - Databases will be backed up in crash-consistent state and transaction log processing will be skipped

Safe DR

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:

1. the SQL instance has one or more databases with a name starting or ending in a space character.
   
2. the account under which SQL VSS Writer service is running doesn't have sysadmin role on a SQL server
   
3. 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

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

1. Use the "Repair" function within Apps & Features for the Microsoft VSS Writer for SQL Server

1. 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. 

1. 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
   
   
2. Restart SQL Server VSS Writer service
   
   
3. 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
   
   
4. 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.

• Related Articles

• Veeam - Cloud Connect jobs fail with "Authentication failed because the remote party has closed the transport stream" error

  Safe DR Challenge After upgrade of Veeam Backup & Replication on the Veeam Cloud Connect service provider's backup server to version 10, tenant jobs may start failing with the following error: "Authentication failed because the remote party has ...

• Veeam - An existing connection was forcibly closed by the remote host Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}.

  Safe DR Challange Backup fails with the following error: Error: write: An existing connection was forcibly closed by the remote host Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}. What This Means The last backup job ...

• Veeam - Setting up Cloud Copy

  Safe DR Please follow the below steps when setting up cloud copy to our offsite repository. Prior to doing this you will need to set Safe Data Storage as your service provider, a link to doing that can be found here. Open up your Veeam Backup and ...

• Veeam - Task Failed Unexpectedly

  Safe DR Challenge Backup fails with the following error: Error Task failed Unexpectedly What This Means The job was terminated suddenly, resulting in an incomplete backup and restore point. Possible Causes Host rebooted during the backup, resulting ...

• Veeam - Add Safe Data Storage as a service provider

  You need to follow the below steps to connect your instance of Veeam Backup and Replication to Safe Data Storage as your Veeam Cloud Connect Service Provider. Open your Veeam Backup and Replication Client and navigate to "Backup Infrastructure", ...