我的独立物理服务器正在运行Server 2012 R2 Foundation。 存在两个单独的备份计划,都使用Windows Server Backup。 在使用WBADMIN命令创build的每周备份过程中, 我从DHCP Jet Writer收到VSS错误 ,但是在从Windows Server Backup GUI创build的计划中运行的两个每日备份过程中没有收到VSS错误 。
通过从PowerShell脚本运行WBADMIN来创build备份。 该命令是:
wbadmin start backup -backuptarget:"\\?\Volume{86997494-eb2a-11e3-80c1-d4ae52d397d7}\" -allCritical -systemState -vssFull --% -include:"C:","E:" -quiet
The backup operation has completedlogging在Microsoft-Windows-Backup / Operational日志中) 活动ID 2002(来源ESENT):
svchost (1860) Shadow copy instance 15 encountered error -2403 on freeze.
事件ID 12290(源VSS):
Volume Shadow Copy Service warning: ESENT ERROR {be9ac81e-3619-421f-920f-4c6fea9e93ad} Dhcp Jet Writer: -2403. hr = 0x00000000, The operation completed successfully. Operation: OnFreeze event Freeze Event Context: Execution Context: Jet Writer Writer Class Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad} Writer Name: Dhcp Jet Writer Execution Context: Writer Writer Class Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad} Writer Name: Dhcp Jet Writer Writer Instance ID: {d25a80e6-7314-4c56-98f4-7f9ee9500b6a}
事件ID 8229(来源VSS):
A VSS writer has rejected an event with error 0x800423f3, The writer experienced a transient error. If the backup process is retried, the error may not reoccur. . Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer. Operation: Freeze Event Context: Execution Context: Writer Writer Class Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad} Writer Name: Dhcp Jet Writer Writer Instance ID: {d25a80e6-7314-4c56-98f4-7f9ee9500b6a} Command Line: C:\Windows\system32\svchost.exe -k DHCPServer Process ID: 1860
Event ID 2007(来源ESENT):
svchost (1860) Shadow copy instance 15 aborted.
事件ID 16389(来源SPP):
Writer Dhcp Jet Writer experienced retryable error during shadow copy creation. Retrying... More info: .
vssadmin list writers 。 所有的作家报告稳定,没有错误。 (但是,我还没有机会在星期天上午12:00之后立即执行此操作)。 我还有什么可以尝试? 我会发布任何需要的附加信息。
我通过将启动时间向前移动30分钟来解决这个问题。 我仔细研究了一些正在运行的进程,这个进程与原来的上午12:00开始时间相冲突,但无法find一个进程,但我唯一可以得出的结论是,其他的东西阻止了DHCP VSS writer在备份时运行开始。