我们有一台 Windows Server 2003 R2 SP2 VMWare VM，其 Veeam 备份失败，并出现以下错误：
无法为热备份准备客户机。错误：VSSControl：1 备份作业失败。无法创建包含写入器数据的卷的卷影副本。无法序列化 BackupComponents 文档。无法保存备份组件文档。路径：[C:\WINDOWS\VeeamVssSupport\metadata\VSS\BackupComponents.xml]。无法基于备份组件文档创建 XML 树。无法解析 XML 文档。文档：[
服务器已重新启动但仍然返回相同的错误。
服务器位于域中，用户帐户可以访问该服务器。磁盘空间也不是问题，有 12.9Gb 可用。VMWare Tools 的版本为 v10.0.0 build-3000743。
vssadmin list writers 显示运行 Veeam 备份之前所有写入器都处于稳定状态。尝试备份后，以下显示失败状态 - 注册表写入器、WMI 写入器和事件日志写入器。重新启动“卷影复制”和“Windows 管理规范”服务会使写入器恢复稳定，但备份仍然失败。
我检查了 VeeamGuestHelper.log 文件，其中有以下错误：
12/02/2016 10:20:13 5868 Creating an offline version of writers metadata.
12/02/2016 10:20:13 5868 [Event Log Writer] processing in progress. Instance ID: [{77268f2a-2cb2-4c48-a233-c0660846fca0}]. Class ID: [{eee8c692-67ed-4250-8d86-390603070d00}]
12/02/2016 10:20:13 5868 [Event Log Writer] processing in progress. Instance ID: [{77268f2a-2cb2-4c48-a233-c0660846fca0}]. Class ID: [{eee8c692-67ed-4250-8d86-390603070d00}]. Failed.
12/02/2016 10:20:13 5868 ERR Cannot store writer's metadata. Writer class ID: [{eee8c692-67ed-4250-8d86-390603070d00}]. Writer instance ID: [{77268f2a-2cb2-4c48-a233-c0660846fca0}]. Writer display name: [Event Log Writer].
12/02/2016 10:20:13 5868 ERR Cannot parse XML document. Document: [<WRITER_METADATA xmlns="x-schema:#VssWriterMetadataInfo" version="1.1"><IDENTIFICATION writerId="eee8c692-67ed-4250-8d86-390603070d00" instanceId="77268f2a-2cb2-4c48-a233-c0660846fca0" friendlyName="Event Log Writer" usage="SYSTEM_SERVICE" dataSource="OTHER"/><RESTORE_METHOD method="REPLACE_AT_REBOOT" writerRestore="never" rebootRequired="yes"/><BACKUP_LOCATIONS><FILE_GROUP componentName="Event Logs" caption="Event Logs" restoreMetadata="no" notifyOnBackupComplete="no" selectable="yes" selectableForRestore="no" componentFlags="0"><FILE_LIST path="%SystemRoot%\system32\config" filespec="AppEvent.Evt" alternatePath="%SystemRoot%\Repair\Backup\ServiceState\EventLogs" filespecBackupType="3855"/><FILE_LIST path="C:\WINDOWS\system32\config" filespec="kaspersk.evt" alternatePath="%SystemRoot%\Repair\Backup\ServiceState\EventLogs" filespecBackupType="3855"/><FILE_LIST path="%SystemRoot%\System32\config" filespec="SecEvent.Evt" alternatePath="%SystemRoot%\Repair\Backup\ServiceState\EventLogs" filespecBackupType="3855"/><FILE_LIST path="%SystemRoot%\system32\config" filespec="SysEvent.Evt" alternatePath="%SystemRoot%\Repair\Backup\ServiceState\EventLogs" filespecBackupType="3855"/></FILE_GROUP><EXCLUDE_FILES path="%SystemRoot%\system32\config" filespec="*.evt" recursive="no"/></BACKUP_LOCATIONS></WRITER_METADATA>].
12/02/2016 10:20:13 5868 ERR COM error: Error opening input file: 'x-schema:#VssWriterMetadataInfo'.
12/02/2016 10:20:13 5868 ERR The system cannot locate the resource specified.
12/02/2016 10:20:13 5868 ERR Code: 0x1
12/02/2016 10:20:13 5868 [VeeamFreezeWriter] processing in progress. Instance ID: [{026c5131-ac04-4217-9817-9affaa334635}]. Class ID: [{18ec56c4-e042-497d-a3d4-eea24284fa03}]
12/02/2016 10:20:13 5868 [VeeamFreezeWriter] processing in progress. Instance ID: [{026c5131-ac04-4217-9817-9affaa334635}]. Class ID: [{18ec56c4-e042-497d-a3d4-eea24284fa03}]. Failed.
12/02/2016 10:20:13 5868 ERR Cannot store writer's metadata. Writer class ID: [{18ec56c4-e042-497d-a3d4-eea24284fa03}]. Writer instance ID: [{026c5131-ac04-4217-9817-9affaa334635}]. Writer display name: [VeeamFreezeWriter].
12/02/2016 10:20:13 5868 ERR Cannot parse XML document. Document: [<WRITER_METADATA xmlns="x-schema:#VssWriterMetadataInfo" version="1.1"><IDENTIFICATION writerId="18ec56c4-e042-497d-a3d4-eea24284fa03" instanceId="026c5131-ac04-4217-9817-9affaa334635" friendlyName="VeeamFreezeWriter" usage="USER_DATA" dataSource="OTHER"/><BACKUP_LOCATIONS><FILE_GROUP componentName="VeeamFreezeWriter" caption="VeeamFreezeWriter" restoreMetadata="no" notifyOnBackupComplete="no" selectable="yes" selectableForRestore="yes" componentFlags="0"/></BACKUP_LOCATIONS></WRITER_METADATA>].
12/02/2016 10:20:13 5868 ERR COM error: Error opening input file: 'x-schema:#VssWriterMetadataInfo'.
12/02/2016 10:20:13 5868 ERR The system cannot locate the resource specified.
12/02/2016 10:20:13 5868 ERR Code: 0x1
12/02/2016 10:20:13 5868 [COM+ REGDB Writer] processing in progress. Instance ID: [{aa69744d-b494-4df9-9cdd-fb494395ea06}]. Class ID: [{542da469-d3e1-473c-9f4f-7847f01fc64f}]
12/02/2016 10:20:13 5868 [COM+ REGDB Writer] processing in progress. Instance ID: [{aa69744d-b494-4df9-9cdd-fb494395ea06}]. Class ID: [{542da469-d3e1-473c-9f4f-7847f01fc64f}]. Failed.
12/02/2016 10:20:13 5868 ERR Cannot store writer's metadata. Writer class ID: [{542da469-d3e1-473c-9f4f-7847f01fc64f}]. Writer instance ID: [{aa69744d-b494-4df9-9cdd-fb494395ea06}]. Writer display name: [COM+ REGDB Writer].
12/02/2016 10:20:13 5868 ERR Cannot parse XML document. Document: [<WRITER_METADATA xmlns="x-schema:#VssWriterMetadataInfo" version="1.1"><IDENTIFICATION writerId="542da469-d3e1-473c-9f4f-7847f01fc64f" instanceId="aa69744d-b494-4df9-9cdd-fb494395ea06" friendlyName="COM+ REGDB Writer" usage="BOOTABLE_SYSTEM_STATE" dataSource="OTHER"/><RESTORE_METHOD method="CUSTOM" writerRestore="never" rebootRequired="no"/><BACKUP_LOCATIONS><EXCLUDE_FILES path="%SystemRoot%\Registration" filespec="*" recursive="yes"/><FILE_GROUP componentName="COM+ REGDB" caption="COM+ REGDB" restoreMetadata="no" notifyOnBackupComplete="no" selectable="yes" selectableForRestore="no" componentFlags="0"><FILE_LIST path="%SystemRoot%\Repair\Backup\BootableSystemState\ComRegistrationDatabase" filespec="*" recursive="yes" filespecBackupType="3855"/></FILE_GROUP></BACKUP_LOCATIONS></WRITER_METADATA>].
12/02/2016 10:20:13 5868 ERR COM error: Error opening input file: 'x-schema:#VssWriterMetadataInfo'.
12/02/2016 10:20:13 5868 ERR The system cannot locate the resource specified.
12/02/2016 10:20:13 5868 ERR Code: 0x1
12/02/2016 10:20:13 5868 [MSDEWriter] processing in progress. Instance ID: [{2fb80071-eb0a-4650-9fd8-3e7790010a65}]. Class ID: [{f8544ac1-0611-4fa5-b04b-f7ee00b03277}]
12/02/2016 10:20:13 5868 [MSDEWriter] processing in progress. Instance ID: [{2fb80071-eb0a-4650-9fd8-3e7790010a65}]. Class ID: [{f8544ac1-0611-4fa5-b04b-f7ee00b03277}]. Failed.
12/02/2016 10:20:13 5868 ERR Cannot store writer's metadata. Writer class ID: [{f8544ac1-0611-4fa5-b04b-f7ee00b03277}]. Writer instance ID: [{2fb80071-eb0a-4650-9fd8-3e7790010a65}]. Writer display name: [MSDEWriter].
12/02/2016 10:20:13 5868 ERR Cannot parse XML document. Document: [<WRITER_METADATA xmlns="x-schema:#VssWriterMetadataInfo" version="1.1"><IDENTIFICATION writerId="f8544ac1-0611-4fa5-b04b-f7ee00b03277" instanceId="2fb80071-eb0a-4650-9fd8-3e7790010a65" friendlyName="MSDEWriter" usage="SYSTEM_SERVICE" dataSource="TRANSACTION_DB"/><RESTORE_METHOD method="RESTORE_IF_CAN_BE_REPLACED" writerRestore="always" rebootRequired="no"/></WRITER_METADATA>].
12/02/2016 10:20:13 5868 ERR COM error: Error opening input file: 'x-schema:#VssWriterMetadataInfo'.
12/02/2016 10:20:13 5868 ERR The system cannot locate the resource specified.
12/02/2016 10:20:13 5868 ERR Code: 0x1
12/02/2016 10:20:13 5868 [WMI Writer] processing in progress. Instance ID: [{702ef282-903f-46ed-aae5-7285f8a3eb52}]. Class ID: [{a6ad56c2-b509-4e6c-bb19-49d8f43532f0}]
12/02/2016 10:20:13 5868 [WMI Writer] processing in progress. Instance ID: [{702ef282-903f-46ed-aae5-7285f8a3eb52}]. Class ID: [{a6ad56c2-b509-4e6c-bb19-49d8f43532f0}]. Failed.
12/02/2016 10:20:13 5868 ERR Cannot store writer's metadata. Writer class ID: [{a6ad56c2-b509-4e6c-bb19-49d8f43532f0}]. Writer instance ID: [{702ef282-903f-46ed-aae5-7285f8a3eb52}]. Writer display name: [WMI Writer].
12/02/2016 10:20:13 5868 ERR Cannot parse XML document. Document: [<WRITER_METADATA xmlns="x-schema:#VssWriterMetadataInfo" version="1.1"><IDENTIFICATION writerId="a6ad56c2-b509-4e6c-bb19-49d8f43532f0" instanceId="702ef282-903f-46ed-aae5-7285f8a3eb52" friendlyName="WMI Writer" usage="SYSTEM_SERVICE" dataSource="OTHER"/><BACKUP_LOCATIONS><FILE_GROUP componentName="WMI" caption="Windows Managment Instrumentation" restoreMetadata="no" notifyOnBackupComplete="no" selectable="no" selectableForRestore="no" componentFlags="0"><FILE_LIST path="C:\WINDOWS\system32\WBEM\Repository" filespec="*.*" recursive="yes" filespecBackupType="3855"/></FILE_GROUP></BACKUP_LOCATIONS><RESTORE_METHOD method="REPLACE_AT_REBOOT" writerRestore="never" rebootRequired="yes"/></WRITER_METADATA>].
12/02/2016 10:20:13 5868 ERR COM error: Error opening input file: 'x-schema:#VssWriterMetadataInfo'.
12/02/2016 10:20:13 5868 ERR The system cannot locate the resource specified.
12/02/2016 10:20:13 5868 ERR Code: 0x1
12/02/2016 10:20:13 5868 [Registry Writer] processing in progress. Instance ID: [{acd8c3f4-9cbe-4abe-a0d9-449b10fa6f6d}]. Class ID: [{afbab4a2-367d-4d15-a586-71dbb18f8485}]
12/02/2016 10:20:13 5868 [Registry Writer] processing in progress. Instance ID: [{acd8c3f4-9cbe-4abe-a0d9-449b10fa6f6d}]. Class ID: [{afbab4a2-367d-4d15-a586-71dbb18f8485}]. Failed.
12/02/2016 10:20:13 5868 ERR Cannot store writer's metadata. Writer class ID: [{afbab4a2-367d-4d15-a586-71dbb18f8485}]. Writer instance ID: [{acd8c3f4-9cbe-4abe-a0d9-449b10fa6f6d}]. Writer display name: [Registry Writer].
12/02/2016 10:20:13 5868 ERR Cannot parse XML document. Document: [<WRITER_METADATA xmlns="x-schema:#VssWriterMetadataInfo" version="1.1"><IDENTIFICATION writerId="afbab4a2-367d-4d15-a586-71dbb18f8485" instanceId="acd8c3f4-9cbe-4abe-a0d9-449b10fa6f6d" friendlyName="Registry Writer" usage="BOOTABLE_SYSTEM_STATE" dataSource="OTHER"/><RESTORE_METHOD method="CUSTOM" writerRestore="never" rebootRequired="yes"/><BACKUP_LOCATIONS><FILE_GROUP componentName="Registry" caption="Registry" restoreMetadata="no" notifyOnBackupComplete="no" selectable="yes" selectableForRestore="no" componentFlags="0"><FILE_LIST path="%SystemRoot%\Repair\Backup\BootableSystemState\Registry" filespec="default" filespecBackupType="3855"/><FILE_LIST path="%SystemRoot%\Repair\Backup\BootableSystemState\Registry" filespec="SAM" filespecBackupType="3855"/><FILE_LIST path="%SystemRoot%\Repair\Backup\BootableSystemState\Registry" filespec="SECURITY" filespecBackupType="3855"/><FILE_LIST path="%SystemRoot%\Repair\Backup\BootableSystemState\Registry" filespec="software" filespecBackupType="3855"/><FILE_LIST path="%SystemRoot%\Repair\Backup\BootableSystemState\Registry" filespec="system" filespecBackupType="3855"/></FILE_GROUP><EXCLUDE_FILES path="%SystemRoot%\system32\config" filespec="default" recursive="no"/><EXCLUDE_FILES path="%SystemRoot%\system32\config" filespec="default.LOG" recursive="no"/><EXCLUDE_FILES path="%SystemRoot%\system32\config" filespec="default.sav" recursive="no"/><EXCLUDE_FILES path="%SystemRoot%\system32\config" filespec="SAM" recursive="no"/><EXCLUDE_FILES path="%SystemRoot%\system32\config" filespec="SAM.LOG" recursive="no"/><EXCLUDE_FILES path="%SystemRoot%\system32\config" filespec="SECURITY" recursive="no"/><EXCLUDE_FILES path="%SystemRoot%\system32\config" filespec="SECURITY.LOG" recursive="no"/><EXCLUDE_FILES path="%SystemRoot%\system32\config" filespec="software" recursive="no"/><EXCLUDE_FILES path="%SystemRoot%\system32\config" filespec="software.LOG" recursive="no"/><EXCLUDE_FILES path="%SystemRoot%\system32\config" filespec="software.sav" recursive="no"/><EXCLUDE_FILES path="%SystemRoot%\system32\config" filespec="system" recursive="no"/><EXCLUDE_FILES path="%SystemRoot%\system32\config" filespec="system.LOG" recursive="no"/><EXCLUDE_FILES path="%SystemRoot%\system32\config" filespec="system.sav" recursive="no"/></BACKUP_LOCATIONS></WRITER_METADATA>].
12/02/2016 10:20:13 5868 ERR COM error: Error opening input file: 'x-schema:#VssWriterMetadataInfo'.
12/02/2016 10:20:13 5868 ERR The system cannot locate the resource specified.
12/02/2016 10:20:13 5868 ERR Code: 0x1
12/02/2016 10:20:13 5868 Creating an offline version of writers metadata.. Ok.
12/02/2016 10:20:13 5868 Serializing VSS writers metadata. Ok.
12/02/2016 10:20:13 5868 Serializing BackupComponents document
12/02/2016 10:20:13 5868 Serializing BackupComponents document. Failed.
问题始于 2 月 9 日，当天 VMWare ESX 主机打了补丁，升级了内存，因此 VM 被迁移到另一台主机，但又移回了原来的主机。在发现备份失败后，VMWare 工具才升级。
同一 ESX 主机上所有其他类似的 Windows 2003 R2 SP2 服务器的 Veeam 备份都运行正常，但我不知道为什么这个备份会失败，如能得到任何帮助，不胜感激！
答案1
这是因为为该特定虚拟机启用了应用程序感知处理，因此无法成功执行静默快照。禁用此功能可让虚拟机成功备份。