Site Recovery 中的服务更新Service updates in Site Recovery

本文概述 Azure Site Recovery 更新,并介绍如何升级 Site Recovery 组件。This article provides an overview of Azure Site Recovery updates, and describes how to upgrade Site Recovery components.

Site Recovery 定期发布服务更新。Site Recovery publishes service updates on a regular basis. 更新包括新功能、支持改进、组件更新和 bug 修复。Updates include new features, support improvements, component updates, and bug fixes. 为了利用最新的功能和修复,我们建议运行最新版本的 Site Recovery 组件。In order to take advantage of the latest features and fixes, we recommend running the latest versions of Site Recovery components.

更新支持Updates support

Azure Site Recovery 的支持说明Support statement for Azure Site Recovery

我们建议始终升级到最新的组件版本:We recommend always upgrading to the latest component versions:

每次发布 Azure Site Recovery 组件的新版本“N”,“N-4”以下的所有版本都被视为终止支持With every new version 'N' of an Azure Site Recovery component that's released, all versions below 'N-4' are considered to be out of support.

Important

官方的升级支持适用于 N-4 以上的版本到 N 版本。Official support is for upgrading from > N-4 version to N version. 例如,如果你正在运行 N-6,则需要先升级到 N-4,然后升级到 N。For example, if you're running you are on N-6, you need to first upgrade to N-4, and then upgrade to N.

查看此文中的最新更新汇总(版本 N)。Review the latest update rollup (version N) in this article. 请记住,Site Recovery 为 N-4 版本提供支持。Remember that Site Recovery provides support for N-4 versions.

组件过期Component expiry

组件已过期(或即将到期)时,Site Recovery 将通过电子邮件(如果你已订阅电子邮件通知)或门户中的保管库仪表板向你发出通知。Site Recovery notifies you of expired components (or nearing expiry) by email (if you subscribed to email notifications), or on the vault dashboard in the portal.

  • 此外,有可用的更新时,门户中方案基础结构视图中的相应组件旁边会显示“有可用的更新”按钮。 In addition, when updates are available, in the infrastructure view for your scenario in the portal, an Update available button appears next to the component. 单击此按钮会重定向到某个链接,可通过该链接下载最新组件版本。This button redirects you to a link for downloading the latest component version.
  • 如果复制 Hyper-V VM,则不会显示保管库仪表板通知,Vaults dashboard notifications aren't available if you're replicating Hyper-V VMs.

而是发送电子邮件通知,如下所示。Emails notifications are sent as follows.

时间Time 频率Frequency
组件过期前的 60 天60 days before component expiry 每两周一次Once bi-weekly
后续 53 天Next 53 days 每周一次Once a week
过去 7 天Last 7 days 每天 1 次Once a day
过期后After expiry 每两周一次Once bi-weekly

在不接受官方支持的情况下升级Upgrading outside official support

如果组件版本与最新版本之间的差大于 4,则此组件将被视为已终止支持。If the difference between your component version and the latest release version is greater than four, this is considered out of support. 在这种情况下,请按如下所述进行升级:In this case, upgrade as follows:

  1. 将当前安装的组件升级到当前版本加 4。Upgrade the currently installed component to your current version plus four. 例如,如果当前版本为 9.16,则升级到 9.20。For example, if your version if 9.16, then upgrade to 9.20.
  2. 然后升级到下一个兼容的版本。Then, upgrade to the next compatible version. 沿用上面的示例,将 9.16 升级到 9.20 后,再升级到 9.24。So in our example, after upgrading 9.16 to 9.20, upgrade to 9.24.

对所有相关组件遵循相同的过程。Follow the same process for all relevant components.

最新操作系统/内核的支持Support for latest operating systems/kernels

Note

如果你已计划维护时段,并且维护后需要重新启动,则我们建议先升级 Site Recovery 组件,然后在维护时段内继续执行剩余的计划活动。If you have a maintenance window scheduled, and a reboot is included in it, we recommend that you first upgrade Site Recovery components, and then proceed with the rest of the scheduled activities in the maintenance window.

  1. 在升级操作系统/内核版本之前,请验证 Site Recovery 是否支持目标版本。Before upgrading operating system/kernel versions, verify if the target version is supported Site Recovery.

  2. 查看可用的更新来了解需要升级的组件。Review available updates to find out what you want to upgrade.

  3. 升级到最新的 Site Recovery 版本。Upgrade to the latest Site Recovery version.

  4. 将操作系统/内核升级到所需版本。Upgrade the operating system/kernel to the required versions.

  5. 重新启动。Reboot.

此过程可确保将计算机操作系统/内核升级到最新版本,并将支持新版本所需的最新 Site Recovery 更改加载到计算机。This process ensures that the machine operating system/kernel is upgraded to the latest version, and that the latest Site Recovery changes needed to support the new version are loaded on to the machine.

Azure VM 灾难恢复到 AzureAzure VM disaster recovery to Azure

在这种情况下,可以允许 Site Recovery 管理更新,如下所述:In this scenario, You can allow Site Recovery to manage updates as follows:

  • 在启用复制过程期间。During the enable replication process.
  • 在保管库中指定扩展更新设置。By setting the extension update settings inside the vault.

若要手动管理更新,请执行以下操作:If you want to manually manage updates, do the following:

  1. 在保管库 >“复制的项”中,单击屏幕顶部的此通知: In the vault > Replicated Items, click this notification at the top of the screen:

    “有新的 Site Recovery 复制代理更新可用。 单击以安装 ->”New Site Recovery replication agent update is available. Click to install ->

  2. 选择要将更新应用到的 VM,然后单击“确定”。 Select the VMs for which you want to apply the update, and then click OK.

将 VMware VM/物理服务器灾难恢复到 AzureVMware VM/physical server disaster recovery to Azure

  1. 根据当前版本和支持声明,遵照这些说明先在本地配置服务器上安装更新。Based on your current version and the support statement, install the update first on the on-premises configuration server, using these instructions.
  2. 如果有横向扩展进程服务器,接下来请遵照这些说明更新这些服务器。If you have scale-out process servers, update them next, using these instructions.
  3. 若要更新每台受保护计算机上的移动代理,请参阅此文To update the Mobility agent on each protected machine, refer to this article.

升级移动服务后重新启动Reboot after Mobility service upgrade

建议在每次升级移动服务后重新启动,以确保在源计算机上加载所有最新更改。A reboot is recommended after every upgrade of the Mobility service, to ensure that all the latest changes are loaded on the source machine.

除非上次重新启动时的代理版本与当前版本之差大于 4,否则不一定要重新启动。A reboot isn't mandatory, unless the difference between the agent version during last reboot, and the current version, is greater than four.

下表中的示例对此做了解释。The example in the table shows how this works.

代理版本(上次重新启动时)Agent version (last reboot) 升级到Upgrade to 是否需要重新启动?Mandatory reboot?
9.169.16 9.189.18 不是必需的Not mandatory
9.169.16 9.199.19 不是必需的Not mandatory
9.169.16 9.209.20 不是必需的Not mandatory
9.169.16 9.219.21 必需。Mandatory.

升级到 9.20,然后在升级到 9.21 之前重新启动。Upgrade to 9.20, then reboot before upgrading to 9.21.

Hyper-V VM 灾难恢复到 AzureHyper-V VM disaster recovery to Azure

在 Hyper-V 站点与 Azure 之间Between a Hyper-V site and Azure

  1. 下载 Azure Site Recovery 提供程序的更新。Download the update for the Azure Site Recovery Provider.
  2. 在 Site Recovery 中注册的每个 Hyper-V 服务器上安装该提供程序。Install the Provider on each Hyper-V server registered in Site Recovery. 如果你正在运行群集,请在所有群集节点上升级。If you're running a cluster, upgrade on all cluster nodes.

在本地 VMM 站点与 Azure 之间Between an on-premises VMM site and Azure

  1. 下载 Azure Site Recovery 提供程序的更新。Download the update for the Azure Site Recovery Provider.
  2. 在 VMM 服务器上安装该提供程序。Install the Provider on the VMM server. 如果 VMM 部署在群集中,请在所有群集节点上安装该提供程序。If VMM is deployed in a cluster, install the Provider on all cluster nodes.
  3. 在所有 Hyper-V 主机或群集节点上安装最新的 Azure 恢复服务代理。Install the latest Azure Recovery Services agent on all Hyper-V hosts or cluster nodes.

在两个本地 VMM 站点之间Between two on-premises VMM sites

  1. 下载 Azure Site Recovery 提供程序的最新更新。Download the latest update for the Azure Site Recovery Provider.
  2. 在管理辅助恢复站点的 VMM 服务器上安装最新的提供程序。Install the latest Provider on the VMM server managing the secondary recovery site. 如果 VMM 部署在群集中,请在所有群集节点上安装该提供程序。If VMM is deployed in a cluster, install the Provider on all cluster nodes.
  3. 更新恢复站点后,在管理主站点的 VMM 服务器上安装该提供程序。After the recovery site is updated, install the Provider on the VMM server that's managing the primary site.

后续步骤Next steps

请关注我们的 Azure 更新页来了解新的更新和版本。Follow our Azure Updates page to track new updates and releases.