对 Azure 备份失败进行故障排除:代理或扩展的问题Troubleshoot Azure Backup failure: Issues with the agent or extension

本文提供故障排查步骤,可帮助解决与 VM 代理和扩展通信相关的 Azure 备份错误。This article provides troubleshooting steps that can help you resolve Azure Backup errors related to communication with the VM agent and extension.

如果本文未解决你的 Azure 问题,请访问 MSDN 和 CSDN 上的 Azure 论坛。If your Azure issue is not addressed in this article, visit the Azure forums on MSDN and CSDN. 可以在这些论坛上发布问题。You can post your issue in these forums. 还可提交 Azure 支持请求。You also can submit an Azure support request. 若要提交支持请求,请在 Azure 支持页上提交。To submit a support request, on the Azure support page.

UserErrorGuestAgentStatusUnavailable - VM 代理无法与 Azure 备份通信UserErrorGuestAgentStatusUnavailable - VM agent unable to communicate with Azure Backup

错误代码:UserErrorGuestAgentStatusUnavailableError code: UserErrorGuestAgentStatusUnavailable
错误消息:VM 代理无法与 Azure 备份进行通信Error message: VM Agent unable to communicate with Azure Backup

Azure VM 代理可能已停止、已过期、处于不一致状态或未安装,从而阻止 Azure 备份服务触发快照。The Azure VM agent might be stopped, outdated, in an inconsistent state, or not installed and prevent Azure Backup service to trigger snapshots.

  • 打开 Azure 门户>“VM”>“设置”>“属性”窗格 > 确保 VM“状态”为“正在运行”,“代理状态”为“就绪” 。Open Azure portal > VM > Settings > Properties pane > ensure VM Status is Running and Agent status is Ready. 如果 VM 代理已停止或处于不一致状态,请重启代理If the VM agent is stopped or is in an inconsistent state, restart the agent
    • 对于 Windows VM,请遵循以下步骤重启来宾代理。For Windows VMs, follow these steps to restart the Guest Agent.
    • 对于 Linux VM,请遵循以下步骤重启来宾代理。For Linux VMs, follow these steps to restart the Guest Agent.
  • 打开 Azure 门户>“VM”>“设置”>“扩展”> 确保所有扩展均处于“预配成功”状态 。Open Azure portal > VM > Settings > Extensions > Ensure all extensions are in provisioning succeeded state. 如果未处于该状态,请按照以下步骤解决问题。If not, follow these steps to resolve the issue.

GuestAgentSnapshotTaskStatusError - 无法与 VM 代理通信以获取快照状态GuestAgentSnapshotTaskStatusError - Could not communicate with the VM agent for snapshot status

错误代码:GuestAgentSnapshotTaskStatusErrorError code: GuestAgentSnapshotTaskStatusError
错误消息:无法与 VM 代理通信,因此无法获取快照状态Error message: Could not communicate with the VM agent for snapshot status

注册和计划 Azure 备份服务的 VM 后,备份会通过与 VM 备份扩展通信来获取时间点快照,从而启动作业。After you register and schedule a VM for the Azure Backup service, Backup initiates the job by communicating with the VM backup extension to take a point-in-time snapshot. 以下任何条件都可能阻止快照的触发。Any of the following conditions might prevent the snapshot from being triggered. 如果未触发快照,则备份可能失败。If the snapshot isn't triggered, a backup failure might occur. 请按所列顺序完成以下故障排除步骤,然后重试操作:Complete the following troubleshooting steps in the order listed, and then retry your operation:

原因 1:代理安装在 VM 中,但无响应(针对 Windows VM)Cause 1: The agent is installed in the VM, but it's unresponsive (for Windows VMs)

原因 2:VM 中安装的代理已过时(针对 Linux VM)Cause 2: The agent installed in the VM is out of date (for Linux VMs)

原因 3:无法检索快照状态或无法创建快照Cause 3: The snapshot status can't be retrieved, or a snapshot can't be taken

原因 4:备份扩展无法更新或加载Cause 4: The backup extension fails to update or load

原因 5:未设置 VM-Agent 配置选项(对于 Linux VM)Cause 5: VM-Agent configuration options are not set (for Linux VMs)

UserErrorVmProvisioningStateFailed - VM 处于预配失败状态UserErrorVmProvisioningStateFailed - The VM is in failed provisioning state

错误代码:UserErrorVmProvisioningStateFailedError code: UserErrorVmProvisioningStateFailed
错误消息:VM 处于预配失败状态Error message: The VM is in failed provisioning state

当其中一个扩展失败将 VM 状态置于预配失败状态时,会发生此错误。This error occurs when one of the extension failures puts the VM into provisioning failed state.
打开 Azure 门户>“VM”>“设置”>“扩展”>“扩展状态”,然后检查所有扩展是否都处于“预配成功”状态 。Open  Azure Portal > VM > Settings > Extensions > Extensions status and check if all extensions are in provisioning succeeded state.

  • 如果 VMSnapshot 扩展处于失败状态,则右键单击失败的扩展并将其删除。If VMSnapshot extension is in a failed state, then right-click on the failed extension and remove it. 触发按需备份,这将重新安装扩展并运行备份作业。Trigger an on-demand backup, this will reinstall the extensions and run the backup job.
  • 如果其他任何扩展处于失败状态,则可能会干扰备份。If any other extension is in a failed state, then it can interfere with the backup. 确保这些扩展问题已解决,然后重试备份操作。Ensure those extension issues are resolved and retry the backup operation.

UserErrorRpCollectionLimitReached - 已达到还原点集合的最大限制UserErrorRpCollectionLimitReached - The Restore Point collection max limit has reached

错误代码:UserErrorRpCollectionLimitReachedError code: UserErrorRpCollectionLimitReached
错误消息:已达到还原点集合的最大限制。Error message: The Restore Point collection max limit has reached.

  • 如果恢复点资源组中的锁阻止自动清理恢复点,则可能会发生此问题。This issue could happen if there's a lock on the recovery point resource group preventing automatic cleanup of recovery points.
  • 如果每天触发多个备份,则也可能发生此问题。This issue can also happen if multiple backups are triggered per day. 目前,我们建议每天只创建一个备份,因为即时还原点只保留 1-5 天(按照配置的快照保留期的要求),并且在任意给定时间,只能将 18 个即时 RP 与一个 VM 相关联。Currently we recommend only one backup per day, as the instant restore points are retained for 1-5 days per the configured snapshot retention and only 18 instant RPs can be associated with a VM at any given time.
  • VM 的各个还原点集合和资源组的还原点数量不能超过 18 个。The number of restore points across restore point collections and resource groups for a VM can't exceed 18. 若要创建新的还原点,请删除现有的还原点。To create a new restore point, delete existing restore points.

建议的操作:Recommended Action:
若要解决此问题,请删除 VM 资源组中的锁,并重试触发清理的操作。To resolve this issue, remove the lock on the resource group of the VM, and retry the operation to trigger clean-up.

备注

备份服务将创建一个单独的资源组而非 VM 的资源组来存储还原点集合。Backup service creates a separate resource group than the resource group of the VM to store restore point collection. 建议客户不要锁定为备份服务使用而创建的资源组。Customers are advised not to lock the resource group created for use by the Backup service. 备份服务创建的资源组的命名格式为:AzureBackupRG_<Geo><number> 例如:AzureBackupRG_northeurope_1The naming format of the resource group created by Backup service is: AzureBackupRG<Geo>_<number> Eg: AzureBackupRG_northeurope_1

步骤 1:删除还原点资源组中的锁Step 1: Remove lock from the restore point resource group
步骤 2:清理还原点集合Step 2: Clean up restore point collection

UserErrorKeyvaultPermissionsNotConfigured - 备份服务对密钥保管库没有足够的权限,无法备份已加密的 VMUserErrorKeyvaultPermissionsNotConfigured - Backup doesn't have sufficient permissions to the key vault for backup of encrypted VMs

错误代码:UserErrorKeyvaultPermissionsNotConfiguredError code: UserErrorKeyvaultPermissionsNotConfigured
错误消息:备份服务对 Key Vault 没有足够的权限,无法备份已加密的 VM。Error message: Backup doesn't have sufficient permissions to the key vault for backup of encrypted VMs.

要使备份操作在加密的 VM 上成功,该服务必须具有访问密钥保管库的权限。For backup operation to succeed on encrypted VMs, it must have permissions to access the key vault. 这可以使用 Azure 门户或通过 PowerShell 来完成This can be done using the Azure portal or through the PowerShell

ExtensionSnapshotFailedNoNetwork - 由于虚拟机上无网络连接,快照操作失败ExtensionSnapshotFailedNoNetwork - Snapshot operation failed due to no network connectivity on the virtual machine

错误代码:ExtensionSnapshotFailedNoNetworkError code: ExtensionSnapshotFailedNoNetwork
错误消息:由于虚拟机上无网络连接,快照操作失败Error message: Snapshot operation failed due to no network connectivity on the virtual machine

注册和计划 Azure 备份服务的 VM 后,备份会通过与 VM 备份扩展通信来获取时间点快照,从而启动作业。After you register and schedule a VM for the Azure Backup service, Backup initiates the job by communicating with the VM backup extension to take a point-in-time snapshot. 以下任何条件都可能阻止快照的触发。Any of the following conditions might prevent the snapshot from being triggered. 如果未触发快照,则备份可能失败。If the snapshot isn't triggered, a backup failure might occur. 请按所列顺序完成以下故障排除步骤,然后重试操作:Complete the following troubleshooting steps in the order listed, and then retry your operation:

原因 1:无法检索快照状态或无法创建快照Cause 1: The snapshot status can't be retrieved, or a snapshot can't be taken
原因 2:备份扩展无法更新或加载Cause 2: The backup extension fails to update or load

ExtensionOperationFailedForManagedDisks - VMSnapshot 扩展操作失败ExtensionOperationFailedForManagedDisks - VMSnapshot extension operation failed

错误代码:ExtentionOperationFailedForManagedDisksError code: ExtentionOperationFailedForManagedDisks
错误消息:VMSnapshot 扩展操作失败Error message: VMSnapshot extension operation failed

注册和计划 Azure 备份服务的 VM 后,备份会通过与 VM 备份扩展通信来获取时间点快照,从而启动作业。After you register and schedule a VM for the Azure Backup service, Backup initiates the job by communicating with the VM backup extension to take a point-in-time snapshot. 以下任何条件都可能阻止快照的触发。Any of the following conditions might prevent the snapshot from being triggered. 如果未触发快照,则备份可能失败。If the snapshot isn't triggered, a backup failure might occur. 请按所列顺序完成以下故障排除步骤,然后重试操作:Complete the following troubleshooting steps in the order listed, and then retry your operation:
原因 1:无法检索快照状态或无法创建快照Cause 1: The snapshot status can't be retrieved, or a snapshot can't be taken
原因 2:备份扩展无法更新或加载Cause 2: The backup extension fails to update or load
原因 3:代理安装在 VM 中,但无响应(针对 Windows VM)Cause 3: The agent is installed in the VM, but it's unresponsive (for Windows VMs)
原因 4:VM 中安装的代理已过时(针对 Linux VM)Cause 4: The agent installed in the VM is out of date (for Linux VMs)

BackUpOperationFailed/BackUpOperationFailedV2 - 备份失败并出现内部错误BackUpOperationFailed / BackUpOperationFailedV2 - Backup fails, with an internal error

错误代码:BackUpOperationFailed/BackUpOperationFailedV2Error code: BackUpOperationFailed / BackUpOperationFailedV2
错误消息:发生内部错误,备份失败 - 请在几分钟后重试操作Error message: Backup failed with an internal error - Please retry the operation in a few minutes

注册和计划 Azure 备份服务的 VM 后,备份会通过与 VM 备份扩展通信来获取时间点快照,从而启动作业。After you register and schedule a VM for the Azure Backup service, Backup initiates the job by communicating with the VM backup extension to take a point-in-time snapshot. 以下任何条件都可能阻止快照的触发。Any of the following conditions might prevent the snapshot from being triggered. 如果未触发快照,则备份可能失败。If the snapshot isn't triggered, a backup failure might occur. 请按所列顺序完成以下故障排除步骤,然后重试操作:Complete the following troubleshooting steps in the order listed, and then retry your operation:
原因 1:代理安装在 VM 中,但无响应(针对 Windows VM)Cause 1: The agent installed in the VM, but it's unresponsive (for Windows VMs)
原因 2:VM 中安装的代理已过时(针对 Linux VM)Cause 2: The agent installed in the VM is out of date (for Linux VMs)
原因 3:无法检索快照状态或无法创建快照Cause 3: The snapshot status can't be retrieved, or a snapshot can't be taken
原因 4:备份扩展无法更新或加载Cause 4: The backup extension fails to update or load
原因 5:备份服务因资源组锁定而无权删除旧的还原点Cause 5: Backup service doesn't have permission to delete the old restore points because of a resource group lock

UserErrorUnsupportedDiskSize - Azure 备份当前不支持配置的磁盘大小UserErrorUnsupportedDiskSize - The configured disk size(s) is currently not supported by Azure Backup

错误代码:UserErrorUnsupportedDiskSizeError code: UserErrorUnsupportedDiskSize
错误消息:Azure 备份当前不支持配置的磁盘大小。Error message: The configured disk size(s) is currently not supported by Azure Backup.

对磁盘大小大于 32 TB 的 VM 进行备份时,备份操作可能会失败。Your backup operation could fail when backing up a VM with a disk size greater than 32 TB. 此外,目前不支持备份大小超过 4 TB 的加密磁盘。Also, backup of encrypted disks greater than 4 TB in size is not supported today. 通过拆分磁盘,确保磁盘大小于或等于支持的限制。Ensure that the disk size(s) is less than or equal to the supported limit by splitting the disk(s).

UserErrorBackupOperationInProgress - 无法启动备份,因为另一个备份操作当前正在进行中UserErrorBackupOperationInProgress - Unable to initiate backup as another backup operation is currently in progress

错误代码:UserErrorBackupOperationInProgressError code: UserErrorBackupOperationInProgress
错误消息:无法启动备份,因为另一个备份操作当前正在进行中Error message: Unable to initiate backup as another backup operation is currently in progress

最近的备份作业失败,因为某个现有的备份作业正在进行。Your recent backup job failed because there is an existing backup job in progress. 在当前作业完成前,无法启动新的备份作业。You can't start a new backup job until the current job finishes. 在触发或计划其他备份操作之前,请确保完成当前正在进行的备份操作。Ensure the backup operation currently in progress is completed before triggering or scheduling another backup operations. 若要检查备份作业状态,请执行以下步骤:To check the backup jobs status, perform the below steps:

  1. 登录 Azure 门户,单击“所有服务” 。Sign in to the Azure portal, click All services. 键入“恢复服务”,然后单击“恢复服务保管库”。 Type Recovery Services and click Recovery Services vaults. 此时显示恢复服务保管库列表。The list of recovery services vaults appears.
  2. 在恢复服务保管库列表中,选择在其中配置了备份的保管库。From the list of recovery services vaults, select a vault in which the backup is configured.
  3. 在保管库仪表板菜单中,单击“备份作业”显示所有备份作业 。On the vault dashboard menu, click Backup Jobs it displays all the backup jobs.
    • 如果某个备份作业正在进行,请等待它完成或取消备份作业。If a backup job is in progress, wait for it to complete or cancel the backup job.
      • 若要取消备份作业,请右键单击备份作业并单击“取消”或使用 PowerShellTo cancel the backup job, right-click on the backup job and click Cancel or use PowerShell.
    • 如果已在另一个保管库中重新配置了备份,则确保旧保管库中没有正在运行的备份作业。If you have reconfigured the backup in a different vault, then ensure there are no backup jobs running in the old vault. 如果存在,则取消备份作业。If it exists, then cancel the backup job.
      • 若要取消备份作业,请右键单击备份作业并单击“取消” 或使用 PowerShellTo cancel the backup job, right-click on the backup job and click Cancel or use PowerShell
  4. 重试备份操作。Retry backup operation.

如果计划备份操作花费时间长且与下一个备份配置冲突,请查看最佳做法备份性能还原注意事项If the scheduled backup operation is taking longer, conflicting with the next backup configuration, then review the Best Practices, Backup Performance, and Restore consideration.

UserErrorCrpReportedUserError - 由于出现错误,备份失败。UserErrorCrpReportedUserError - Backup failed due to an error. 有关详细信息,请参阅“作业错误消息详细信息”For details, see Job Error Message Details

错误代码:UserErrorCrpReportedUserErrorError code: UserErrorCrpReportedUserError
错误消息:由于出现错误,备份失败。Error message: Backup failed due to an error. 有关详细信息,请参阅“作业错误消息详细信息”。For details, see Job Error Message Details.

此错误从 IaaS VM 报告。This error is reported from the IaaS VM. 若要确定问题的根本原因,请访问恢复服务保管库设置。To identify the root cause of the issue, go to the Recovery Services vault settings. 在“监视”部分选择“备份作业”,筛选并查看状态。 Under the Monitoring section, select Backup jobs to filter and view the status. 单击“失败” ,查看基本错误消息详细信息。Click on Failures to review the underlying error message details. 根据错误详细信息页中的建议采取进一步操作。Take further actions according to the recommendations in the error details page.

原因和解决方法Causes and solutions

代理安装在 VM 中,但无响应(针对 Windows VM)The agent is installed in the VM, but it's unresponsive (for Windows VMs)

解决方案Solution

VM 代理可能已损坏或服务可能已停止。The VM agent might have been corrupted, or the service might have been stopped. 重新安装 VM 代理可帮助获取最新版本。Reinstalling the VM agent helps get the latest version. 此外,还有助于与服务重新开始通信。It also helps restart communication with the service.

  1. 确定 Windows Azure 来宾代理服务是否在 VM 服务 (services.msc) 中运行。Determine whether the Windows Azure Guest Agent service is running in the VM services (services.msc). 尝试重启 Windows Azure 来宾代理服务并启动备份。Try to restart the Windows Azure Guest Agent service and initiate the backup.
  2. 如果服务中未显示 Windows Azure 来宾代理服务,请在“控制面板”中转到“程序和功能”,确定是否已安装 Windows Azure 来宾代理服务 。If the Windows Azure Guest Agent service isn't visible in services, in Control Panel, go to Programs and Features to determine whether the Windows Azure Guest Agent service is installed.
  3. 如果“程序和功能”中显示了 Windows Azure 来宾代理,请将其卸载 。If the Windows Azure Guest Agent appears in Programs and Features, uninstall the Windows Azure Guest Agent.
  4. 下载并安装最新版本的代理 MSIDownload and install the latest version of the agent MSI. 必须拥有管理员权限才能完成安装。You must have Administrator rights to complete the installation.
  5. 检查服务中是否显示了 Windows Azure 来宾代理服务。Verify that the Windows Azure Guest Agent services appear in services.
  6. 运行按需备份:Run an on-demand backup:
    • 在门户中,选择“立即备份” 。In the portal, select Backup Now.

此外,检查是否在 VM 中安装了 Microsoft .NET 4.5Also, verify that Microsoft .NET 4.5 is installed in the VM. VM 代理需要使用 .NET 4.5 来与服务通信。.NET 4.5 is required for the VM agent to communicate with the service.

VM 中安装的代理已过时(针对 Linux VM)The agent installed in the VM is out of date (for Linux VMs)

解决方案Solution

对于 Linux VM,与代理或扩展相关的大多数失败都是由于影响过时的 VM 代理的问题所造成的。Most agent-related or extension-related failures for Linux VMs are caused by issues that affect an outdated VM agent. 若要解决此问题,请遵循以下通用准则:To troubleshoot this issue, follow these general guidelines:

  1. 按照更新 Linux VM 代理的说明进行操作。Follow the instructions for updating the Linux VM agent.

    备注

    强烈建议 只通过分发存储库更新代理。We strongly recommend that you update the agent only through a distribution repository. 建议不要直接从 GitHub 下载代理代码并将其更新。We do not recommend downloading the agent code directly from GitHub and updating it. 如果分发没有可用的最新代理,请联系分发支持部门,了解如何安装最新代理。If the latest agent for your distribution is not available, contact distribution support for instructions on how to install it. 若要检查最新代理,请转到 GitHub 存储库中的 Microsoft Azure Linux 代理页。To check for the most recent agent, go to the Windows Azure Linux agent page in the GitHub repository.

  2. 运行以下命令,确保 Azure 代理可在 VM 上运行:ps -eEnsure that the Azure agent is running on the VM by running the following command: ps -e

    如果该进程未运行,请使用以下命令进行重启:If the process isn't running, restart it by using the following commands:

    • 对于 Ubuntu: service walinuxagent startFor Ubuntu: service walinuxagent start
    • 对于其他分发版: service waagent startFor other distributions: service waagent start
  3. 配置自动重新启动代理Configure the auto restart agent.

  4. 运行新的测试备份。Run a new test backup. 如果仍然失败,请从 VM 收集以下日志:If the failure persists, collect the following logs from the VM:

    • /var/lib/waagent/*.xml/var/lib/waagent/*.xml
    • /var/log/waagent.log/var/log/waagent.log
    • /var/log/azure/*/var/log/azure/*

如果需要 waagent 的详细日志记录,请执行以下步骤:If we require verbose logging for waagent, follow these steps:

  1. 在 /etc/waagent.conf 文件中,找到以下行:Enable verbose logging (y|n)In the /etc/waagent.conf file, locate the following line: Enable verbose logging (y|n)
  2. Logs.Verbose 值从 n 更改为 y。Change the Logs.Verbose value from n to y.
  3. 保存更改,然后遵循本部分前面所述的步骤重启 waagent。Save the change, and then restart waagent by completing the steps described earlier in this section.

未设置 VM-Agent 配置选项(对于 Linux VM)VM-Agent configuration options are not set (for Linux VMs)

配置文件 (/etc/waagent.conf) 可控制 waagent 的操作。A configuration file (/etc/waagent.conf) controls the actions of waagent. 配置文件选项“Extensions.Enable”和“Provisioning.Agent”应设置为“y”,以使备份正常工作 。Configuration File Options Extensions.Enable and Provisioning.Agent should be set to y for Backup to work. 有关 VM-Agent 配置文件选项的完整列表,请参阅 https://github.com/Azure/WALinuxAgent#configuration-file-optionsFor full list of VM-Agent Configuration File Options, please refer https://github.com/Azure/WALinuxAgent#configuration-file-options

无法检索快照状态或无法创建快照The snapshot status can't be retrieved, or a snapshot can't be taken

VM 备份依赖于向基础存储帐户发出快照命令。The VM backup relies on issuing a snapshot command to the underlying storage account. 备份失败的原因可能是它无法访问存储帐户,也可能是快照任务的执行被延迟。Backup can fail either because it has no access to the storage account, or because the execution of the snapshot task is delayed.

解决方案Solution

以下状态可能导致快照任务失败:The following conditions might cause the snapshot task to fail:

原因Cause 解决方案Solution
由于在远程桌面协议 (RDP) 中关闭了 VM,VM 状态报告不正确。The VM status is reported incorrectly because the VM is shut down in Remote Desktop Protocol (RDP). 如果在 RDP 中关闭了 VM,请检查门户,确定 VM 状态是否正确。If you shut down the VM in RDP, check the portal to determine whether the VM status is correct. 如果不正确,请在门户中使用 VM 仪表板上的“关闭” 选项来关闭 VM。If it’s not correct, shut down the VM in the portal by using the Shutdown option on the VM dashboard.
VM 无法从 DHCP 获取主机或结构地址。The VM can't get the host or fabric address from DHCP. 必须在来宾内启用 DHCP,才能正常进行 IaaS VM 备份。DHCP must be enabled inside the guest for the IaaS VM backup to work. 如果 VM 无法从 DHCP 响应 245 获取主机或结构地址,则无法下载或运行任何扩展。If the VM can't get the host or fabric address from DHCP response 245, it can't download or run any extensions. 如果需要静态专用 IP,则应通过 Azure 门户或 PowerShell 进行配置,同时确保启用 VM 内的 DHCP 选项 。If you need a static private IP, you should configure it through the Azure portal or PowerShell and make sure the DHCP option inside the VM is enabled. 详细了解如何通过 PowerShell 设置静态 IP 地址。Learn more about setting up a static IP address with PowerShell.

无法更新或加载备份扩展The backup extension fails to update or load

如果无法加载扩展,则会由于无法创建快照而导致备份失败。If extensions can't load, backup fails because a snapshot can't be taken.

解决方案Solution

卸载扩展以强制重新加载 VMSnapshot 扩展。Uninstall the extension to force the VMSnapshot extension to reload. 下一次备份尝试将重新加载扩展。The next backup attempt reloads the extension.

卸载扩展:To uninstall the extension:

  1. Azure 门户中,找到备份失败的 VM。In the Azure portal, go to the VM that is experiencing backup failure.
  2. Select Settings.
  3. 选择“扩展” 。Select Extensions.
  4. 选择“快照扩展” 。Select Snapshot Extension.
  5. 选择“卸载” 。Select Uninstall.

对于 Linux VM,如果 VMSnapshot 扩展未显示在 Azure 门户中,请更新 Azure Linux 代理,然后运行备份。For Linux VM, If the VMSnapshot extension does not show in the Azure portal, update the Azure Linux Agent, and then run the backup.

完成这些步骤可在下一次备份期间重新安装扩展。Completing these steps causes the extension to be reinstalled during the next backup.

删除恢复点资源组中的锁Remove lock from the recovery point resource group

  1. 登录到 Azure 门户Sign in to the Azure portal.

  2. 转到“所有资源选项”,选择采用 AzureBackupRG_<Geo><number> 格式的还原点集合资源组。 Go to All Resources option, select the restore point collection resource group in the following format AzureBackupRG<Geo>_<number>.

  3. 在“设置”部分,选择“锁”以显示锁。 In the Settings section, select Locks to display the locks.

  4. 若要删除锁,请选择省略号,然后单击“删除”。 To remove the lock, select the ellipsis and click Delete.

    删除锁

清理还原点集合Clean up restore point collection

删除锁后,必须清理还原点。After removing the lock, the restore points have to be cleaned up.

如果删除 VM 的资源组或 VM 本身,则托管磁盘的即时还原快照会保持活动状态,并根据保留集过期。If you delete the Resource Group of the VM, or the VM itself, the instant restore snapshots of managed disks remain active and expire according to the retention set. 若要删除存储在还原点集合中的即时还原快照(如果不再需要这些快照),请按照以下步骤清理还原点集合。In order to delete the instant restore snapshots (if you don't need them anymore) that are stored in the Restore Point Collection, clean up the restore point collection according to the steps given below.

若要清理还原点,请执行以下任一方法:To clean up the restore points, follow any of the methods:

通过运行按需备份来清理还原点集合Clean up restore point collection by running on-demand backup

删除锁后,将触发按需备份。After removing the lock, trigger an on-demand backup. 这可以确保自动清理还原点。This will ensure the restore points are automatically cleaned up. 预期此按需操作第一次会失败;但是,它可以确保自动完成清理,而无需手动删除还原点。Expect this on-demand operation to fail the first time; however, it will ensure automatic cleanup instead of manual deletion of restore points. 清理后,下一个计划的备份应会成功。After cleanup your next scheduled backup should succeed.

备注

自动清理将在触发按需备份的数小时后发生。Automatic cleanup will happen after few hours of triggering the on-demand backup. 如果计划的备份仍然失败,请尝试使用此处列出的步骤手动删除还原点集合。If your scheduled backup still fails, then try manually deleting the restore point collection using the steps listed here.

从 Azure 门户清理还原点集合Clean up restore point collection from Azure portal

若要手动清除由于资源组中存在锁而未能清除的还原点集合,请尝试以下步骤:To manually clear the restore points collection, which isn't cleared because of the lock on the resource group, try the following steps:

  1. 登录到 Azure 门户Sign in to the Azure portal.

  2. 在“中心”菜单中单击“所有资源”,选择 VM 所在的、采用 AzureBackupRG_<Geo><number> 格式的资源组。 On the Hub menu, click All resources, select the Resource group with the following format AzureBackupRG<Geo>_<number> where your VM is located.

    删除锁

  3. 单击“资源组”。此时会显示“概述”窗格。 Click Resource group, the Overview pane is displayed.

  4. 选择“显示隐藏的类型”选项,以显示所有已隐藏的资源。 Select Show hidden types option to display all the hidden resources. 选择采用 AzureBackupRG_<VMName><number> 格式的还原点集合。Select the restore point collections with the following format AzureBackupRG<VMName>_<number>.

    删除锁

  5. 单击“删除”以清理还原点集合。 Click Delete to clean the restore point collection.

  6. 再次重试备份操作。Retry the backup operation again.

备注

如果资源(RP 集合)具有大量还原点,则从门户中将其删除的操作可能会超时并失败。If the resource (RP Collection) has a large number of Restore Points, then deleting them from the portal may timeout and fail. 这是已知的 CRP 问题,其中所有还原点不会在规定时间内都删除且操作会超时;但是,删除操作通常会在 2 次或 3 次重试后成功。This is a known CRP issue, where all restore points are not deleted in the stipulated time and the operation times out; however the delete operation usually succeeds after 2 or 3 retries.