Backup job warns me about missing vss writer

[Darkyputz]

Hello!

I am new to this backup solution, and unfortunately, the KB ID: 2095 that i found to that subject is sub optimal when it comes to solve the issue
It states, that my SQl database is having a space in its name...but after checking my existing databases, none of them is having spaces in name or before nor after.

I just did a query of my databases...and they look spaceless:
Select '#'+name+'#' from sys.databases
#master#
#tempdb#
#model#
#msdb#
#amwsys#
#sample999#
#testrestore#
#law#
#KDAD#
#java#

Did anyone came across that issue before and found a fix?
Thx in advance and here the KB to that issue:

Products: Veeam Backup & Replication
Version: 9.x

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

Your SQL instance have databases with names ending in a space character.
Solution

Please rename the database to a new name (without a space in it)
More Information

Running vssadmin list writers shows that SqlServerWriter in not in the list.

[alanbolte]

Is the SQL Writer service actually running?

Otherwise, I recommend creating a support case, and posting the case ID here.

[Doan]

I have the same issue after upgrading to version 9.
The service is running.

[Gostev]

What is your support case ID for this issue?

[Scraps]

Hi Guys

I have the same issue after upgrading to V9.
Had no issues on V8 only now after I upgraded to V9 the problem started. My case ID # 01707939

[alanbolte]

What version of SQL are all of you running? If I recall correctly, early versions of SQL Server 2005 used the MSDE writer instead of the SQL writer, and we only support the latter.

[Doan]

My suppor case ID is: 01708116

We are running SQL Server 2008R2.

We do also have customers with the same setup, where we don't have this issue.

[eneurink]

Hello,
I am sorry, my Englisch is not so good but, we have the same problem. After installing te upgrade to version 9 i get the error "SQL VSS Writer is missing: databases will be backed up in crash-consistent state"
The error is with backing-up de the SQL server switch is Using SQL 2005 but with the VSS Writer.
The VSS Writer is logging in with the administrator account and still the problem.
I hope some one has an awnser or bether, a sollution for this problem.
Thanx
Erik

[Vitaliy S.]

Please take a look at this KB article. If it doesn't help, please open a support case to investigate this issue further.

[Doan]

Giving the account under which SQL VSS Writer service is running the sysadmin role solved my issue.

Go to services.msc and check the Log On As.
Connect to all named instances and check if the account has sysadmin role. If you don't see the Log On As account, you will have to create a New Login... and give it sysadmin role.

[GregorS]

Hi!

I've got this old Windows XP VM with MS SQL Server 2005 Express. SQL Server (<Instance>) system service is running under Network Service account and SQL Server VSS Writer service is running under Local System account. The account used for application-aware processing (AAP) guest OS credentials has sysadmin server role. Nothing from KB2095 seems to apply, SqlServerWriter is in Stable state. The best part is that Veeam backup job performs correctly regarding AAP on this SQL! It's just that since VBR upgrade to v9.0 there's this silly warning that triggers e-mail being sent to my mailbox every morning. Do you need another ticket lifted or is it already known that a remedy for this specific issue will be included in the upcoming Update 1?


Regards
Gregor

[foggy]

SQL Server VSS Writer service is running under Local System account.

In the Luan's case giving the account under which SQL Server VSS Writer service is running the sysadmin role resolved the issue. Could you please check this is the case? Also, restarting the service did help in another case mentioned in this thread.

[GregorS]

NT AUTHORITY\SYSTEM is sysadmin. Service restart did not help.

[foggy]

Then I suggest opening your own case for investigation.

[GregorS]

SUPPORT CASE ID# 01733384

[enoch]

Also have this issue with one VM.

Before v9.0 (8.0) there was not a warning.

Have checked that the service account running as SQL VSS Writer is Sysadmin on SQL.

[foggy]

Do you have a case opened for this?

[enoch]

No, but will do today.

I was asking because it could have been har general issue/problem.

[foggy]

Based on this thread, the behavior can be caused by different issues, so it is recommended to check with support.

[showstopper]

SUPPORT CASE ID# 01733384

Did you manage to fix your issue? I have exactly the same issue with XP and SQL Express - working under 8, but "fails" in 9.

[showstopper]

Did you manage to fix your issue? I have exactly the same issue with XP and SQL Express - working under 8, but "fails" in 9.

EDIT - I updated to Update 1 and i still have the same issue.
I will log a call with support.

[GregorS]

Hi Tony

Support stated that XP was no longer a supported OS and that they would not be fixing this. As I understood they excluded the XP version of the SQL VSS API from VBR v9... or something...

[veremin]

Application Aware logic including SQL logs processing works for Microsoft Windows 2003 and later, meaning XP is out of scope here. Thanks.

[Dave]

Hi,

Is there an option to suppress the warning message, we have disabled the sql vss writer service. In veeam 8 we did not get this warning message.

Regards,
Dave

[foggy]

v8 didn't have this check and just silently performed database backup in crash consistent state. I don't think there's a way to suppress this warning.

[m.novelli]

Hello guys, I'm having the same warning after upgrading a customer to Veeam Backup v9 Update 1

The VM is a Windows XP SP3 with SQL Server 2005 Express SP4

Is there a way to suppress the warning "SQL VSS Writer is missing"?

Many thanks!

Marco

[Vitaliy S.]

I guess you can suppress this by disabling application-aware image processing for this VM and switch to VMware Tools Quiescence.

[iknowtech]

Hmm, I'm getting his on Server 2019, with SQL Server Express 2014. Was anyone getting this that wasn't on XP that got a resolution with support?

[foggy]

Hi Jason, I recommend contacting support directly with this unless you've already done so.

[iknowtech]

I was able to confirm that it was an issue with the SQL VSS Writer service not having Access to SQL. I had to get the LOB App vendor to provide me the SA login to SQL Express so I could setup a service account with SysAdmin rights, then use that account for the VSS Writer Service.