关于本地灾难恢复故障转移/故障回复About on-premises disaster recovery failover/failback

本文概述在将本地计算机灾难恢复到 Azure 期间如何使用 Azure Site Recovery 进行故障转移和故障回复。This article provides an overview of failover and failback during disaster recovery of on-premises machines to Azure with Azure Site Recovery.

恢复阶段Recovery stages

Site Recovery 中的故障转移和故障回复分为四个阶段:Failover and failback in Site Recovery has four stages:

  • 第 1 阶段:从本地故障转移 :设置将本地计算机复制到 Azure 后,当本地站点发生故障时,这些计算机将故障转移到 Azure。Stage 1: Fail over from on-premises : After setting up replication to Azure for on-premises machines, when your on-premises site goes down, you fail those machines over to Azure. 故障转移后,将会基于复制的数据创建 Azure VM。After failover, Azure VMs are created from replicated data.
  • 第 2 阶段:重新保护 Azure VM :在 Azure 中重新保护 Azure VM,使之开始复制回到本地站点。Stage 2: Reprotect Azure VMs : In Azure, you reprotect the Azure VMs so that they start replicating back to the on-premises site. 重新保护期间,为帮助确保数据一致性,本地 VM(如果可用)将会关闭。The on-premises VM (if available) is turned off during reprotection, to help ensure data consistency.
  • 第 3 阶段:从 Azure 故障转移 :如果本地站点再次恢复运行正常,则运行另一次故障转移,这一次是将 Azure VM 故障回复到本地站点。Stage 3: Fail over from Azure : When your on-premises site is running as normal again, you run another failover, this time to fail back Azure VMs to your on-premises site. 可以故障回复到从中进行故障转移的原始位置,或故障回复到备用位置。You can fail back to the original location from which you failed over, or to an alternate location.
  • 第 4 阶段:重新保护本地计算机 :故障回复后,再次启用本地计算机到 Azure 的复制。Stage 4: Reprotect on-premises machines : After failing back, again enable replication of the on-premises machines to Azure.

故障转移Failover

根据业务连续性和灾难恢复 (BCDR) 策略执行故障转移。You perform a failover as part of your business continuity and disaster recovery (BCDR) strategy.

  • BCDR 策略的第一步是持续将本地计算机复制到 Azure。As a first step in your BCDR strategy, you replicate your on-premises machines to Azure on an ongoing basis. 用户访问本地源计算机上运行的工作负荷和应用。Users access workloads and apps running on the on-premises source machines.
  • 如果有需要(例如,如果本地发生服务中断),可将复制计算机故障转移到 Azure。If the need arises, for example if there's an outage on-premises, you fail the replicating machines over to Azure. 使用复制的数据创建 Azure VM。Azure VMs are created using the replicated data.
  • 为实现业务连续性,用户可以继续访问 Azure VM 上的应用。For business continuity, users can continue accessing apps on the Azure VMs.

故障转移是由两个阶段组成的活动:Failover is a two-phase activity:

  • 故障转移 :使用所选恢复点创建并启动 Azure VM 的故障转移。Failover : The failover that creates and brings up an Azure VM using the selected recovery point.
  • 提交 :故障转移后,验证 Azure 中的 VM:Commit : After failover you verify the VM in Azure:
    • 然后,可将故障转移提交到所选的恢复点,或者为提交选择另一个恢复点。You can then commit the failover to the selected recovery point, or select a different point for the commit.
    • 提交故障转移后无法更改恢复点。After committing the failover, the recovery point can't be changed.

故障转移后连接到 AzureConnect to Azure after failover

若要使用 RDP/SSH 连接到故障转移后创建的 Azure VM,需要满足许多要求。To connect to the Azure VMs created after failover using RDP/SSH, there are a number of requirements.

故障转移Failover 位置Location 操作Actions
Azure VM (Windows(Azure VM (Windows( 故障转移之前在本地计算机上On the on-premises machine before failover 通过 Internet 访问 :启用 RDP。Access over the internet : Enable RDP. 确保已针对“公共”添加了 TCP 和 UDP 规则,并确保在“Windows 防火墙” > “允许的应用”中针对所有配置文件允许 RDP 。Make sure that TCP and UDP rules are added for Public , and that RDP is allowed for all profiles in Windows Firewall > Allowed Apps.

通过站点到站点 VPN 访问 :在计算机上启用 RDP。Access over site-to-site VPN : Enable RDP on the machine. 检查是否在“Windows 防火墙” -> “允许的应用和功能”中针对“域和专用”网络允许 RDP 。Check that RDP is allowed in the Windows Firewall -> Allowed apps and features , for Domain and Private networks.

确保操作系统 SAN 策略已设置为 OnlineAllMake sure the operating system SAN policy is set to OnlineAll. 了解详细信息Learn more.

在触发故障转移时,请确保 VM 上没有处于挂起状态的 Windows 更新。Make sure there are no Windows updates pending on the VM when you trigger a failover. Windows 更新可能会在故障转移时启动,在更新完成之前,无法登录到 VM。Windows Update might start when you fail over, and you won't be able to log onto the VM until updates are done.
运行 Windows 的 Azure VMAzure VM running Windows 故障转移之后在 Azure VM 上On the Azure VM after failover 为 VM 添加公共 IP 地址Add a public IP address for the VM.

已故障转移的 VM(及其连接到的 Azure 子网)上的网络安全组规则必须允许与 RDP 端口建立传入连接。The network security group rules on the failed over VM (and the Azure subnet to which it is connected) must allow incoming connections to the RDP port.

选中“启动诊断”可查看 VM 的屏幕截图 。Check Boot diagnostics to verify a screenshot of the VM. 如果无法连接,请检查 VM 是否正在运行,并查看故障排除提示If you can't connect, check that the VM is running, and review troubleshooting tips.
运行 Linux 的 Azure VMAzure VM running Linux 故障转移之前在本地计算机上On the on-premises machine before failover 确保 VM 上的安全外壳服务已设置为在系统引导时自动启动。Ensure that the Secure Shell service on the VM is set to start automatically on system boot.

确保防火墙规则允许 SSH 连接。Check that firewall rules allow an SSH connection to it.
运行 Linux 的 Azure VMAzure VM running Linux 故障转移之后在 Azure VM 上On the Azure VM after failover 已故障转移的 VM(及其连接到的 Azure 子网)上的网络安全组规则需要允许与 SSH 端口建立传入连接。The network security group rules on the failed over VM (and the Azure subnet to which it is connected) need to allow incoming connections to the SSH port.

为 VM 添加公共 IP 地址Add a public IP address for the VM.

选中“启动诊断”可查看 VM 的屏幕截图 。Check Boot diagnostics for a screenshot of the VM.

故障转移类型Types of failover

Site Recovery 提供不同的故障转移选项。Site Recovery provides different failover options.

故障转移Failover 详细信息Details 恢复Recovery WorkflowWorkflow
测试故障转移Test failover 用于运行演练,以在不丢失任何数据或造成停机的情况下验证 BCDR 策略。Used to run a drill that validates your BCDR strategy, without any data loss or downtime. 在 Azure 中创建 VM 的副本,这不会对进行中的复制或生产环境造成任何影响。Creates a copy of the VM in Azure, with no impact on ongoing replication, or on your production environment. 1.针对单个 VM 或恢复计划中的多个 VM 运行测试故障转移。1. Run a test failover on a single VM, or on multiple VMs in a recovery plan.

2.选择用于测试故障转移的恢复点。2. Select a recovery point to use for the test failover.

3.选择一个 Azure 网络,故障转移后创建的 Azure VM 将放入该网络。3. Select an Azure network in which the Azure VM will be located when it's created after failover. 该网络仅用于测试故障转移。The network is only used for the test failover.

4.验证演练是否按预期方式进行。4. Verify that the drill worked as expected. Site Recovery 将自动清理演练期间在 Azure 中创建的 VM。Site Recovery automatically cleans up VMs created in Azure during the drill.
计划内故障转移 - Hyper-VPlanned failover-Hyper-V 通常用于计划内停机。Usually used for planned downtime.

源 VM 已关闭。Source VMs are shut down. 在启动故障转移之前,将同步最新的数据。The latest data is synchronized before initiating the failover.
计划的工作流不会发生任何数据丢失。Zero data loss for the planned workflow. 1.规划停机维护时段并通知用户。1. Plan a downtime maintenance window and notify users.

2.使面向用户的应用脱机。2. Take user-facing apps offline.

3.使用最新的恢复点启动计划内故障转移。3. Initiate a planned failover with the latest recovery point. 如果计算机未关闭或遇到错误,则故障转移不会运行。The failover doesn't run if the machine isn't shut down, or if errors are encountered.

4.故障转移后,检查副本 Azure VM 是否在 Azure 中处于活动状态。4. After the failover, check that the replica Azure VM is active in Azure.

5.提交故障转移以完成操作。5. Commit the failover to finish up. 提交操作将删除所有恢复点。The commit action deletes all recovery points.
故障转移 - Hyper-VFailover-Hyper-V 通常在出现计划外服务中断或主站点不可用的情况时运行。Usually run if there's an unplanned outage, or the primary site isn't available.

(可选)关闭 VM,并在启动故障转移之前同步最终更改。Optionally shut down the VM, and synchronize final changes before initiating the failover.
应用只会出现极少量的数据丢失。Minimal data loss for apps. 1.启动 BCDR 计划。1. Initiate your BCDR plan.

2.启动故障转移。2. Initiate a failover. 指定在触发故障转移之前 Site Recovery 应关闭 VM 并同步/复制最新的更改。Specify whether Site Recovery should shut down the VM and synchronize/replicate the latest changes before triggering the failover.

3.可以故障转移到许多恢复点选项,下表对此做了汇总。3. You can fail over to a number of recovery point options, summarized in the table below.

如果未启用关闭 VM 的选项,或者 Site Recovery 无法关闭 VM,则会使用最新的恢复点。If you don't enable the option to shut down the VM, or if Site Recovery can't shut it down, the latest recovery point is used.
即使无法关闭计算机,也会运行故障转移。The failover runs even if the machine can't be shut down.

4.故障转移后,检查副本 Azure VM 是否在 Azure 中处于活动状态。4. After failover, you check that the replica Azure VM is active in Azure.
如果需要,可以从 24 小时保留时段中选择不同的恢复点。If required, you can select a different recovery point from the retention window of 24 hours.

5.提交故障转移以完成操作。5. Commit the failover to finish up. 提交操作将删除所有可用的恢复点。The commit action deletes all available recovery points.
故障转移 - VMwareFailover-VMware 通常在出现计划外服务中断或主站点不可用的情况时运行。Usually run if there's an unplanned outage, or the primary site isn't available.

(可选)指定在启动故障转移之前,Site Recovery 应尝试触发 VM 关闭,并同步和复制最终的更改。Optionally specify that Site Recovery should try to trigger a shutdown of the VM, and to synchronize and replicate final changes before initiating the failover.
应用只会出现极少量的数据丢失。Minimal data loss for apps. 1.启动 BCDR 计划。1. Initiate your BCDR plan.

2.从 Site Recovery 启动故障转移。2. Initiate a failover from Site Recovery. 指定在运行故障转移之前,Site Recovery 是否应尝试触发 VM 关闭并进行同步。Specify whether Site Recovery should try to trigger VM shutdown and synchronize before running the failover.
即使无法关闭计算机,也会运行故障转移。The failover runs even if the machines can't be shut down.

3.故障转移后,检查副本 Azure VM 是否在 Azure 中处于活动状态。3. After the failover, check that the replica Azure VM is active in Azure.
如果需要,可以从 72 小时保留时段中选择不同的恢复点。If required, you can select a different recovery point from the retention window of 72 hours.

5.提交故障转移以完成操作。5. Commit the failover to finish up. 提交操作将删除所有恢复点。The commit action deletes all recovery points.
对于 Windows VM,Site Recovery 在故障转移期间会禁用 VMware 工具。For Windows VMs, Site Recovery disables the VMware tools during failover.

故障转移处理Failover processing

在某些情况下,故障转移需要大约 8 到 10 分钟的时间完成其他进程。In some scenarios, failover requires additional processing that takes around 8 to 10 minutes to complete. 对于以下情况,你可能会发现测试故障转移会持续较长时间:You might notice longer test failover times for:

  • VMware VM 运行的移动服务版本低于 9.8。VMware VMs running a Mobility service version older than 9.8.
  • 物理服务器。Physical servers.
  • VMware Linux VM。VMware Linux VMs.
  • Hyper-V VM 作为物理服务器受到保护。Hyper-V VMs protected as physical servers.
  • VMware VM 未启用 DHCP 服务。VMware VMs that don't have the DHCP service enabled.
  • VMware VM 不包含以下启动驱动程序:storvsc、vmbus、storflt、intelide、atapi。VMware VMs that don't have the following boot drivers: storvsc, vmbus, storflt, intelide, atapi.

恢复点选项Recovery point options

在故障转移期间,可以选择许多恢复点选项。During failover, you can select a number of recovery point options.

选项Option 详细信息Details
最新(最低 RPO)Latest (lowest RPO) 此选项提供最低的恢复点目标 (RPO)。This option provides the lowest recovery point objective (RPO). 它会首先处理已发送到 Site Recovery 服务的所有数据,为每个 VM 创建恢复点,然后将其故障转移到该恢复点。It first processes all the data that has been sent to Site Recovery service, to create a recovery point for each VM, before failing over to it. 触发故障转移后,此恢复点的所有数据将复制到 Site Recovery。This recovery point has all the data replicated to Site Recovery when the failover was triggered.
最新处理Latest processed 此选项将 VM 故障转移到由 Site Recovery 处理的最新恢复点。This option fails over VMs to the latest recovery point processed by Site Recovery. 若要查看特定 VM 的最新恢复点,请检查 VM 设置中的“最新恢复点”。 To see the latest recovery point for a specific VM, check Latest Recovery Points in the VM settings. 此选项提供低 RTO(恢复时间目标),因为无需费时处理未经处理的数据。This option provides a low RTO (Recovery Time Objective), because no time is spent processing unprocessed data.
最新应用一致性Latest app-consistent 如果已启用应用一致性恢复点,此选项会将 VM 故障转移到 Site Recovery 处理的最新应用程序一致性恢复点。This option fails over VMs to the latest application-consistent recovery point processed by Site Recovery, if app-consistent recovery points are enabled. 在 VM 设置中检查最新的恢复点。Check the latest recovery point in the VM settings.
最新处理的多 VMLatest multi-VM processed 此选项适用于包含一个或多个已启用多 VM 一致性的 VM 的恢复计划。This option is available for recovery plans with one or more VMs that have multi-VM consistency enabled. 已启用该设置的 VM 会故障转移到最新的常用多 VM 一致恢复点。VMs with the setting enabled fail over to the latest common multi-VM consistent recovery point. 计划中的任何其他 VM 将故障转移到最新的已处理恢复点。Any other VMs in the plan fail over to the latest processed recovery point.
最新的多 VM 应用一致性Latest multi-VM app-consistent 此选项适用于包含一个或多个已启用多 VM 一致性的 VM 的恢复计划。This option is available for recovery plans with one or more VMs that have multi-VM consistency enabled. 属于复制组的 VM 会故障转移到最新的常用多 VM 应用程序一致恢复点。VMs that are part of a replication group fail over to the latest common multi-VM application-consistent recovery point. 其他 VM 故障转移到其最新的应用程序一致恢复点。Other VMs fail over to their latest application-consistent recovery point.
自定义Custom 使用此选项可将特定的 VM 故障转移到特定的恢复时间点。Use this option to fail over a specific VM to a particular recovery point in time. 此选项不适用于恢复计划。This option isn't available for recovery plans.

备注

恢复点无法迁移到另一个恢复服务保管库。Recovery points can't be migrated to another Recovery Services vault.

重新保护/故障回复Reprotection/failback

故障转移到 Azure 后,复制的 Azure VM 处于不受保护状态。After failover to Azure, the replicated Azure VMs are in an unprotected state.

  • 故障回复到本地站点的第一步是开始将 Azure VM 复制到本地。As a first step to failing back to your on-premises site, you need to start the Azure VMs replicating to on-premises. 重新保护过程取决于故障转移的计算机的类型。The reprotection process depends on the type of machines you failed over.
  • 将计算机从 Azure 复制到本地后,可以运行从 Azure 故障转移到本地站点的过程。After machines are replicating from Azure to on-premises, you can run a failover from Azure to your on-premises site.
  • 计算机再次在本地运行后,可以启用复制,以便将其复制到 Azure 进行灾难恢复。After machines are running on-premises again, you can enable replication so that they replicate to Azure for disaster recovery.

故障回复的工作原理如下:Failback works as follows:

  • VM 至少需有一个恢复点才能故障回复。To fail back, a VM needs at least one recovery point in order to fail back. 恢复计划中的所有 VM 至少需有一个恢复点。In a recovery plan, all VMs in the plan need at least one recovery point.
  • 我们建议使用 最新 恢复点进行故障回复(崩溃一致性恢复点)。We recommend that you use the Latest recovery point to fail back (this is a crash-consistent point).
    • 有一个应用一致性恢复点选项。There is an app-consistent recovery point option. 在这种情况下,单个 VM 将恢复到其最新可用的应用一致性恢复点。In this case, a single VM recovers to its latest available app-consistent recovery point. 对于包含复制组的恢复计划,每个复制组将恢复到其公共的可用恢复点。For a recovery plan with a replication group, each replication group recovers to its common available recovery point.
    • 应用一致性恢复点在时间上可能会落后,并且可能会发生数据丢失。App-consistent recovery points can be behind in time, and there might be loss in data.
  • 从 Azure 故障转移到本地站点期间,Site Recovery 将关闭 Azure VM。During failover from Azure to the on-premises site, Site Recovery shuts down the Azure VMs. 提交故障转移时,Site Recovery 将删除 Azure 中已故障回复的 Azure VM。When you commit the failover, Site Recovery removes the failed back Azure VMs in Azure.

VMware/物理机重新保护/故障回复VMware/physical reprotection/failback

若要重新保护 VMware 计算机和物理服务器并将其从 Azure 故障回复到本地,需要一个故障回复基础结构,并需要满足许多要求。To reprotect and fail back VMware machines and physical servers from Azure to on-premises, you need a failback infrastructure, and there are a number of requirements.

  • Azure 中的临时进程服务器 :若要从 Azure 进行故障回复,需要设置用作进程服务器的 Azure VM,以处理从 Azure 进行的复制。Temporary process server in Azure : To fail back from Azure, you set up an Azure VM to act as a process server to handle replication from Azure. 故障回复完成后,可以删除此 VM。You can delete this VM after failback finishes.
  • VPN 连接 :若要进行故障回复,需要设置从 Azure 网络到本地站点的 VPN 连接(或 ExpressRoute)。VPN connection : To fail back, you need a VPN connection (or ExpressRoute) from the Azure network to the on-premises site.
  • 单独的主目标服务器 :默认情况下,在本地 VMware VM 上与配置服务器一起安装的主目标服务器用于处理故障回复。Separate master target server : By default, the master target server that was installed with the configuration server on the on-premises VMware VM handles failback. 如果对大量流量进行故障回复,应创建专用于此目的的独立本地主目标服务器。If you need to fail back large volumes of traffic, set up a separate on-premises master target server for this purpose.
  • 故障回复策略 :若要复制回到本地站点,需要创建故障回复策略。Failback policy : To replicate back to your on-premises site, you need a failback policy. 此策略是在创建从本地到 Azure 的复制策略时自动创建的。This policy is automatically created when you create a replication policy from on-premises to Azure.
    • 此策略自动与配置服务器相关联。This policy is automatically associated with the configuration server.
    • 无法编辑此策略。You can't edit this policy.
    • 策略值:RPO 阈值 - 15 分钟;恢复点保留期 - 24 小时;应用一致性快照频率 - 60 分钟。Policy values: RPO threshold - 15 minutes; Recovery point retention - 24 Hours; App-consistent snapshot frequency - 60 minutes.

详细了解 VMware/物理机重新保护和故障回复:Learn more about VMware/physical reprotection and failback:

  • 查看重新保护和故障回复的其他要求。Review additional requirements for reprotection and failback.
  • 在 Azure 中部署进程服务器。Deploy a process server in Azure.
  • 部署单独的主目标服务器。Deploy a separate master target server.

在本地重新保护 Azure VM 时,可以指定是要故障回复到原始位置还是备用位置。When you reprotect Azure VMs to on-premises, you can specify that you want to fail back to the original location, or to an alternate location.

  • 原始位置恢复 :这会从 Azure 故障回复到同一台源本地计算机(如果存在)。Original location recovery : This fails back from Azure to the same source on-premises machine if it exists. 在这种情况下,只会将更改复制回到本地。In this scenario, only changes are replicated back to on-premises.
  • 备用位置恢复 :如果本地计算机不存在,可以从 Azure 故障回复到备用位置。Alternate location recovery : If the on-premises machine doesn't exist, you can fail back from Azure to an alternate location. 在本地重新保护 Azure VM 时,将创建本地计算机。When you reprotect the Azure VM to on-premises, the on-premises machine is created. 将发生从 Azure 到本地的完整数据复制。Full data replication occurs from Azure to on-premises. -- 查看位置故障回复的要求和限制。- - Review the requirements and limitations for location failback.

Hyper-V 重新保护/故障回复Hyper-V reprotection/failback

若要重新保护 Hyper-V VM 并将其从 Azure 故障回复到本地:To reprotect and fail back Hyper-V VMs from Azure to on-premises:

  • 只能故障回复使用存储帐户进行复制的 Hyper-V VM。You can only fail back Hyper-V VMs replicating using a storage account. 不支持故障回复使用托管磁盘复制的 Hyper-V VM。Failback of Hyper-V VMs that replicate using managed disks isn't supported.
  • 本地 Hyper-V 主机(或 System Center VMM,如果使用)应已连接到 Azure。On-premises Hyper-V hosts (or System Center VMM if used) should be connected to Azure.
  • 运行从 Azure 到本地的计划内故障回复。You run a planned failback from Azure to on-premises.
  • 不需要为 Hyper-V VM 故障回复设置特定的组件。No specific components need to be set up for Hyper-V VM failback.
  • 在计划内故障转移期间,可以选择相应的选项,以便在故障回复之前同步数据:During planned failover, you can select options to synchronize data before failback:
    • 在故障转移之前同步数据 :此选项可以最大程度地减少虚拟机的停机时间,因为它可以在不关闭虚拟机的情况下执行同步。Synchronize data before failover : This option minimizes downtime for virtual machines as it synchronizes machines without shutting them down.
      • 阶段 1:生成 Azure VM 快照,并将快照复制到本地 Hyper-V 主机。Phase 1: Takes a snapshot of the Azure VM and copies it to the on-premises Hyper-V host. 计算机将继续在 Azure 中运行。The machine continues running in Azure.
      • 阶段 2:关闭 Azure VM,确保其不会发生任何新的更改。Phase 2: Shuts down the Azure VM so that no new changes occur there. 将最终的增量更改集传输到本地服务器,并启动本地 VM。The final set of delta changes is transferred to the on-premises server and the on-premises VM is started up.
    • 仅在故障转移期间同步数据 :此选项速度更快,因为我们预计磁盘的大部分已经更改,因此无需执行校验和计算。Synchronize data during failover only : This option is faster because we expect that most of the disk has changed, and thus don't perform checksum calculations. 此选项会执行磁盘的下载。It performs a download of the disk. 如果 VM 已在 Azure 中运行了一段时间(一个月或以上)或者已删除本地 VM,则我们建议使用此选项。We recommend that you use this option if the VM has been running in Azure for a while (a month or more), or if the on-premises VM has been deleted.

详细了解 Hyper-V 重新保护和故障回复。Learn more about Hyper-V reprotection and failback.

在本地重新保护 Azure VM 时,可以指定是要故障回复到原始位置还是备用位置。When you reprotect Azure VMs to on-premises, you can specify that you want to fail back to the original location, or to an alternate location.

  • 原始位置恢复 :这会从 Azure 故障回复到同一台源本地计算机(如果存在)。Original location recovery : This fails back from Azure to the same source on-premises machine if it exists. 在这种情况下,请选择上一过程中所述的同步选项之一。In this scenario, you select one of the synchronization options described in the previous procedure.
  • 备用位置恢复 :如果本地计算机不存在,可以从 Azure 故障回复到备用位置。Alternate location recovery : If the on-premises machine doesn't exist, you can fail back from Azure to an alternate location. 在本地重新保护 Azure VM 时,将创建本地计算机。When you reprotect the Azure VM to on-premises, the on-premises machine is created. 如果使用此选项,我们建议选择在故障转移之前同步数据的选项With this option, we recommend that you select the option to synchronize data before failover
  • 查看位置故障回复的要求和限制。Review the requirements and limitations for location failback.

故障回复到本地站点后,启用“反向复制”以开始将 VM 复制到 Azure,并完成复制周期。 After failing back to the on-premises site, you enable Reverse Replicate to start replicating the VM to Azure, completing the cycle.

后续步骤Next steps