Avamar:由于孤立的检查点,Hyper V RCT 备份失败并显示错误
Summary: 本知识库 (KB) 文章提供了由于检查点创建错误导致的 Hyper-V 弹性更改跟踪 (RCT) 备份失败的解决方法。
Symptoms
Avamar Hyper-V RCT 备份可能会失败,并显示类似于以下内容的错误:
avhypervvss Info <43419>: Creating backup CheckPoint with 'Copy' guest backup type
2019-04-15 00:05:05 avhypervvss Info <43420>: Creating backup CheckPoint with 'Application' consistenty level
avhypervvss Error <43426>: Checkpoint creation for Virtual machine 'DELLEMC-VM<XXXXSS-XXXX-XXXX-XXXX-XXXXXX>' has failed and will be skipped from backup. For details, please check 'winclustersvc.log'.
avhypervvss Error <43426>: Checkpoint creation for Virtual machine 'AVAMAR-DEV<XXXXSS-XXXX-XXXX-XXXX-XXXXXX>' has failed and will be skipped from backup. For details, please check 'winclustersvc.log'.
avhypervvss Error <43426>: Checkpoint creation for Virtual machine 'DDR-Dev2<XXXXX-XXXX-XXXX-XXXX-XXXXXX>' has failed and will be skipped from backup. For details, please check 'winclustersvc.log'.
avhypervvss Warning <43427>: No targets available for backup after checkpoint process.Cause
Hyper-V RCT 备份可能会在一两天内成功完成。但是,上一个成功的备份是在虚拟机 (VM) 目录中留下孤立的检查点文件 (*.avhdx)。
在备份期间临时创建虚拟机的检查点。完成后,Hyper-V 插件程序会通知 Windows作系统 (OS) 将 AVHD 检查点合并到 VM 的父虚拟硬盘 (VHD) 中。
有时,备份完成后,检查点不会合并到主 VHD 中。在事件查看器日志(应用程序和服务日志 -> Microsoft -> Windows -> Hyper-V VMMS)中,可能会显示以下错误:
"'DDR-Dev2' background disk merge failed to complete: Account restrictions are preventing this user from signing in. For example: blank passwords aren't allowed, sign-in times are limited, or a policy restriction has been enforced. (0x8007052F). (Virtual machine ID XXXXX-XXXX-XXXX-XXXX-XXXXXX) "
在最坏的情况下,检查点可能在 Hyper-V 管理器或 PowerShell 命令中不可见。
Hyper-V 和 Avamar 插件都不知道孤立的检查点。由于存在现有的孤立检查点,Windows作系统无法创建新的检查点 AVHD 文件,因此下一次 Avamar 备份将失败。
Resolution
在 Avamar 日志中,已从 Avamar Hyper-V 插件程序端成功运行检查点清理。但是,事件查看器中同时出现错误,即它无法合并磁盘,从而导致检查点删除错误。
在 Winclustersvc.log 文件中,以下代码片段显示检查点清理已成功完成:
winclustersvc INFO<0000>: Cleaning up checkpoint created on group AvamarBackup_SERVER-app-20190510000504-0: checkpoint \\SERVER\root\virtualization\v2:Msvm_SnapshotCollection.CollectionID="DXXXXDX-XXCE-XXDX-XABF-XXXDXXXXXX" .
winclustersvc INFO<0000>: DestroySnapshot executed successfully
插件调用 Microsoft API 以删除检查点,只有在成功返回后,插件才会记录上述消息。
但是,同时事件查看器日志为所有虚拟机提供以下错误,导致检查点未被删除:
"'DDR-Dev2' background disk merge failed to complete: Account restrictions are preventing this user from signing in. For example: blank passwords aren't allowed, sign-in times are limited, or a policy restriction has been enforced. (0x8007052F). (Virtual machine ID XXXXX-XXXX-XXXX-XXXX-XXXXXX) "
向 Microsoft 创建支持案例,以对孤立的检查点问题进行更多故障排除。
以下是一些可能解决此问题的解决方法:
- 使用 Windows Update 在 Hyper-V 主机上安装最新的修补程序和更新。
- 在开始 Avamar 备份之前,重新启动 Hyper-V 虚拟机管理 (VMMS) 服务。创建计划任务后,“ 作为服务登录 ”组策略对象属性未与 VMMS 服务同步。重新启动 VMMS 服务时,它会尝试强制与 Microsoft 登录服务同步。
- 在组策略对象 (GPO) 中禁用“用户权限分配/作为服务登录”属性。之后,使用 Windows 命令或 PowerShell 提示符在 Hyper-V 计算机上运行以下命令:
GPUpdate / Force
Additional Information
参考: https://social.technet.microsoft.com/Forums/en-US/1dc1a820-be03-4c24-9f85-5793eb6c1d4a/background-merge-fails-replication-state-critical?forum=winserverhyperv (外部链接)