VSS错误 [英] VSS error

问题描述

由于vss writer失败，我们的veeam备份失败了。日志显示如下：
$


Sqllib错误：调用ICommandText :: Execute时遇到OLEDB错误。 hr = 0x80040e14。 SQLSTATE：42000，本机错误：3013

错误状态：1，严重性：16

来源：Microsoft SQL Server Native Client 11.0

错误消息：BACKUP DATABASE正在异常终止。

SQLSTATE：42000，本机错误：3271

错误状态：1，严重性：16

来源：Microsoft SQL Server Native Client 11.0

错误消息：文件"{8F239560-1DB9-4ADD-8C17-17479D19896A"上发生了不可恢复的I / O错误76：" 995（由于线程退出或应用程序请求，I / O操作已中止。）。$
SQLSTATE：01000，本机错误：4035

错误状态： 1，严重性：0

来源：Microsoft SQL Server Native Client 11.0

错误消息：处理数据库'DCust'的0页，文件1上的文件'DCust'。 br />

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.

列出vss编写器显示sql vss编写器失败：

listing vss writers shows that sql vss writer has failed:

作者姓名：'SqlServerWriter'

   作家身份：{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}

   作家身份标识：{f25d3100-df1a-4a67-b281-4a701e0e5f01}

   状态：[11]失败¥b $ b   上一个错误：不可重试的错误

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?

推荐答案

- >确保帐户使用哪些服务"SQL Server VSS writer"正在服务中运行.msc在SQL Server中作为SYSADMIN添加。



- >检查SQL Server错误日志并告知备份失败时的错误。



- >我以前在同一个问题上工作，我在SQL Server错误日志中看到了以下消息。



2014-06-17 07：48：44.23 spid55     错误：3627，严重性：17，状态：0。

2014-06-17 07：48：44.23 spid55     由于此时执行的并行操作过多，无法启动新的并行操作。使用"max worker threads"配置选项增加允许线程数，或
减少系统上运行的并行操作数。



这是指工作线程由于数量庞大的数据库。请参阅此

article  解释了VSS备份和工作线程的依赖关系。



不确定这是否与您的问题有关。但值得检查。

-> 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 article  that explains the dependency of VSS backup and worker threads.

Not sure if this is related to your issue. But it is worth checking.

这篇关于VSS错误的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！