As a DBA, it is not uncommon to encounter issues with SQL Server backups. Recently, I had a client who was facing problems with their 3rd party backup solution. The SQL backups were not happening, and when they contacted the vendor, they were asked to run the command “VSSadmin List Writers” to check if the “SqlServerWriter” component was listed. Unfortunately, it was missing from the output.

After investigating the issue, I found some possible causes and solutions that I would like to share with you.

Possible Causes

1. SQL Writer Service not installed or started: Ensure that the SQL Writer Service is installed and started. If it is not available, you may need to install it from the SQL installation media.

2. Errors in Event Logs: Check the Event Logs for any errors related to the backup process. These logs can provide valuable information about the issue.

3. Trailing spaces in database names: Make sure that none of the databases in the SQL Server instance have trailing spaces in their names. This can cause issues with the backup process.

4. Service account permissions: Verify that the service account for the SQL Writer has sufficient permissions to connect to all instances on the machine. Permission-related issues can prevent the SQL Writer from functioning properly.

Workaround / Solution

In the case of my client, they had a permission-related issue. After changing the service account of the SQL Server, they were able to see the correct output from the “VSSadmin List Writers” command, and the backups started working again.

If you have encountered a similar issue, I would recommend checking the above checklist and trying the solutions provided. However, it is important to note that every situation may be unique, and additional troubleshooting may be required.

Have you faced a similar issue with SQL Server backups? If so, I would love to hear about your experiences and any alternative solutions you may have found.