Hi, our veeam backup fails due to a vss writer failing. Log shows as follows:
Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 3013
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 11.0
Error message: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3271
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 11.0
Error message: A nonrecoverable I/O error occurred on file "{8F239560-1DB9-4ADD-8C17-17479D19896A}76:" 995(The I/O operation has been aborted because of either a thread exit or an application request.).
SQLSTATE: 01000, Native Error: 4035
Error state: 1, Severity: 0
Source: Microsoft SQL Server Native Client 11.0
Error message: Processed 0 pages for database 'DCust', file 'DCust' on file 1.
listing vss writers shows that sql vss writer has failed:
Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {f25d3100-df1a-4a67-b281-4a701e0e5f01}
State: [11] Failed
Last error: Non-retryable error
I can restart it - but it will fail again upon next backup schedule. Any ideas?
解决方案-> Make sure account with which services "SQL server VSS writer" is running in services.msc be added as a SYSADMIN in SQL Server.
-> Check SQL Server error log and advise of errors at that time of backup failure.
-> I have worked previously on this same issue where I saw below message in SQL Server errorlog.
2014-06-17 07:48:44.23 spid55 Error: 3627, Severity: 17, State: 0.
2014-06-17 07:48:44.23 spid55 New parallel operation cannot be started due to too many parallel operations executing at this time. Use the "max worker threads" configuration option to increase the number of allowable threads, or
reduce the number of parallel operations running on the system.
This refers to worker thread starvation due to huge number of database. Refer this
articlethat explains the dependency of VSS backup and worker threads.
Not sure if this is related to your issue. But it is worth checking.