常见问题 - Hyper-V 到 Azure 的灾难恢复Common questions - Hyper-V to Azure disaster recovery

本文提供将本地 Hyper-V VM 复制到 Azure 时可能遇到的常见问题的解答。This article provides answers to common questions we see when replicating on-premises Hyper-V VMs to Azure.

常规General

Site Recovery 如何计费?How is Site Recovery priced?

请查看 Azure Site Recovery 定价详细信息Review Azure Site Recovery pricing details.

Azure VM 如何计费?How do I pay for Azure VMs?

在复制期间,数据将复制到 Azure 存储,因此,VM 不会产生任何费用。During replication, data is replicated to Azure storage, and you don't pay any VM changes. 故障转移到 Azure 时,Site Recovery 会自动创建 Azure IaaS 虚拟机。When you run a failover to Azure, Site Recovery automatically creates Azure IaaS virtual machines. 然后,在 Azure 中使用的计算资源会产生费用。After that you're billed for the compute resources that you consume in Azure.

复制到常规用途 v2 存储帐户时,开销是否有什么不同?Is there any difference in cost when replicating to General Purpose v2 storage account?

你通常会发现 GPv2 存储帐户产生的事务成本增加,因为 Azure Site Recovery 的事务量很大。You will typically see an increase in the transactions cost incurred on GPv2 storage accounts since Azure Site Recovery is transactions heavy. 阅读更多信息以估计更改。Read more to estimate the change.

AzureAzure

为什么需要在 Hyper-V 中使用站点恢复协调复制?What do I need in Hyper-V to orchestrate replication with Site Recovery?

对于 Hyper-V 主机服务器,所需取决于部署方案。For the Hyper-V host server what you need depends on the deployment scenario. 在以下内容中查看 Hyper-V 先决条件:Check out the Hyper-V prerequisites in:

当 Hyper-V 在客户端操作系统上运行时,我可以保护 VM 吗?Can I protect VMs when Hyper-V is running on a client operating system?

不可以。VM 必须位于在受支持的 Windows 服务器计算机上运行的 Hyper-V 主机服务器上。No, VMs must be located on a Hyper-V host server that's running on a supported Windows server machine. 如果需要保护客户端计算机,可以将其作为物理计算机复制到 Azure辅助数据中心If you need to protect a client computer you could replicate it as a physical machine to Azure or a secondary datacenter.

Hyper-V 主机是否需要位于 VMM 云中?Do Hyper-V hosts need to be in VMM clouds?

如果要复制到辅助数据中心,那么 Hyper-V VM 就必须位于 VMM 云中的 Hyper-V 主机服务器上。If you want to replicate to a secondary datacenter, then Hyper-V VMs must be on Hyper-V hosts servers located in a VMM cloud. 如果想要复制到 Azure,那么可以复制 VM(无论是否使用 VMM 云)。If you want to replicate to Azure, then you can replicate VMs with or without VMM clouds. 详细了解从 Hyper-V 复制到 Azure。Read more about Hyper-V replication to Azure.

我可以将 Hyper-V 第 2 代虚拟机复制到 Azure 吗?Can I replicate Hyper-V generation 2 virtual machines to Azure?

是的。Yes. 站点恢复在故障转移过程中将从第 2 代转换成第 1 代。Site Recovery converts from generation 2 to generation 1 during failover. 在故障回复时,计算机将转换回到第 2 代。At failback the machine is converted back to generation 2. 了解详细信息Read more.

如果我只有一个 VMM 服务器,可以部署站点恢复来配合 VMM 吗?Can I deploy Site Recovery with VMM if I only have one VMM server?

是的。Yes. 可以将 VMM 云中 Hyper-V 服务器上的 VM 复制到 Azure,或者在同一台服务器上的 VMM 云之间进行复制。You can either replicate VMs in Hyper-V servers in the VMM cloud to Azure, or you can replicate between VMM clouds on the same server. 对于本地到本地复制,我们建议在主站点与辅助站点中都部署一个 VMM 服务器。For on-premises to on-premises replication, we recommend that you have a VMM server in both the primary and secondary sites.

需要在 Azure 中做好哪些准备?What do I need in Azure?

需要一个 Azure 订阅、一个恢复服务保管库、一个存储帐户和一个虚拟网络。You need an Azure subscription, a Recovery Services vault, a storage account, and a virtual network. 保管库、存储帐户和网络必须位于同一区域。The vault, storage account and network must be in the same region.

需要哪个 Azure 存储帐户?What Azure storage account do I need?

需要 LRS 或 GRS 存储帐户。You need an LRS or GRS storage account. 建议使用 GRS,以便在发生区域性故障或无法恢复主要区域时,能够复原数据。We recommend GRS so that data is resilient if a regional outage occurs, or if the primary region can't be recovered. 支持高级存储。Premium storage is supported.

我的 Azure 帐户是否需要拥有创建 VM 的权限?Does my Azure account need permissions to create VMs?

如果你是订阅管理员,则已经获得了所需的复制权限。If you're a subscription administrator, you have the replication permissions you need. 否则,需要有权在配置 Site Recovery 时指定的资源组和虚拟网络中创建 Azure VM,并有权写入选定的存储帐户。If you're not, you need permissions to create an Azure VM in the resource group and virtual network you specify when you configure Site Recovery, and permissions to write to the selected storage account. 了解详细信息Learn more.

复制数据是否会发送到 Site Recovery?Is replication data sent to Site Recovery?

不会。Site Recovery 不会拦截复制的数据,也不包含 VM 上运行的组件的任何相关信息。No, Site Recovery doesn't intercept replicated data, and doesn't have any information about what's running on your VMs. 复制数据在 Hyper-V 主机与 Azure 存储之间交换。Replication data is exchanged between Hyper-V hosts and Azure storage. 站点恢复并不具有拦截该数据的能力。Site Recovery has no ability to intercept that data. 只有协调复制与故障转移所需的元数据将发送到站点恢复服务。Only the metadata needed to orchestrate replication and failover is sent to the Site Recovery service.

站点恢复已通过 ISO 27001:2013、27018、HIPAA、DPA 认证,目前正在接受 SOC2 和 FedRAMP JAB 评估。Site Recovery is ISO 27001:2013, 27018, HIPAA, DPA certified, and is in the process of SOC2 and FedRAMP JAB assessments.

是否可将本地元数据保留在某个地理区域中?Can we keep on-premises metadata within a geographic region?

是的。Yes. 当你在某个区域中创建保管库时,我们会确保 Site Recovery 使用的所有元数据保留在该区域的地理边界内。When you create a vault in a region, we ensure that all metadata used by Site Recovery remains within that region's geographic boundary.

站点恢复是否将复制数据加密?Does Site Recovery encrypt replication?

是的,传输中加密和 Azure 中加密均受支持。Yes, both encryption-in-transit and encryption in Azure are supported.

部署Deployment

可通过哪些方法实现 Hyper-V 到 Azure 的复制?What can I do with Hyper-V to Azure replication?

  • 灾难恢复:可以设置完整的灾难恢复。Disaster recovery: You can set up full disaster recovery. 在此场景中,可将本地 Hyper-V VM 复制到 Azure 存储:In this scenario, you replicate on-premises Hyper-V VMs to Azure storage:
    • 可将 VM 复制到 Azure。You can replicate VMs to Azure. 如果本地基础结构不可用,则可以故障转移到 Azure。If your on-premises infrastructure is unavailable, you fail over to Azure.
    • 在故障转移时,将使用复制的数据创建 Azure VM。When you fail over, Azure VMs are created using the replicated data. 可以访问 Azure VM 上的应用和工作负载。You can access apps and workloads on the Azure VMs.
    • 本地数据中心重新可用时,可从 Azure 故障回复到本地站点。When your on-premises datacenter is available again, you can fail back from Azure to your on-premises site.
  • 迁移:可以使用 Site Recovery 将本地 Hyper-V VM 迁移到 Azure 存储。Migration: You can use Site Recovery to migrate on-premises Hyper-V VMs to Azure storage. 然后从本地故障转移到 Azure。Then, you fail over from on-premises to Azure. 故障转移后,应用和工作负荷可供使用并在 Azure VM 上运行。After failover, your apps and workloads are available and running on Azure VMs.

需要在本地做好哪些准备?What do I need on-premises?

需要一个或多个在一个或多个独立或群集 Hyper-V 主机上运行的 VM。You need one or more VMs running on one or more standalone or clustered Hyper-V hosts. 还可以复制 System Center Virtual Machine Manager (VMM) 托管的主机上运行的 VM。You can also replicate VMs running on hosts managed by System Center Virtual Machine Manager (VMM).

  • 如果不运行 VMM,则在 Site Recovery 部署期间,将 Hyper-V 主机和群集收集到 Hyper-V 站点中。If you're not running VMM, during Site Recovery deployment, you gather Hyper-V hosts and clusters into Hyper-V sites. 在每个 Hyper-V 主机上安装 Site Recovery 代理(Azure Site Recovery 提供程序和 Recovery Services 代理)。You install the Site Recovery agents (Azure Site Recovery Provider and Recovery Services agent) on each Hyper-V host.
  • 如果 Hyper-V 主机位于 VMM 云中,则在 VMM 中协调复制。If Hyper-V hosts are located in a VMM cloud, you orchestrate replication in VMM. 在 VMM 服务器上安装 Site Recovery 提供程序,在每个 Hyper-V 主机上安装恢复服务代理。You install the Site Recovery Provider on the VMM server, and the Recovery Services agent on each Hyper-V host. 在 VMM 逻辑/VM 网络和 Azure VNet 之间进行映射。You map between VMM logical/VM networks, and Azure VNets.
  • 详细了解 Hyper-V 到 Azure 的体系结构。Learn more about Hyper-V to Azure architecture.

是否可以复制 Hyper-V 群集上的 VM?Can I replicate VMs located on a Hyper-V cluster?

可以,Site Recovery 支持群集 Hyper-V 主机。Yes, Site Recovery supports clustered Hyper-V hosts. 请注意:Note that:

  • 群集的所有节点应注册到同一保管库。All nodes of the cluster should be registered to the same vault.
  • 如果不使用 VMM,则应将群集中的所有 Hyper-V 主机添加到同一 Hyper-V 站点。If you're not using VMM, all Hyper-V hosts in the cluster should be added to the same Hyper-V site.
  • 在群集中每个 Hyper-V 主机上安装 Azure Site Recovery 提供程序和恢复服务代理,并将每个主机添加到 Hyper-V 站点。You install the Azure Site Recovery Provider and Recovery Services agent on each Hyper-V host in the cluster, and add each host to a Hyper-V site.
  • 无需在群集上执行任何特定步骤。No specific steps need to be done on the cluster.
  • 如果对 Hyper-V 运行部署规划器工具,此工具会从正在运行且其中运行此 VM 的节点收集配置文件数据。If you run the Deployment Planner tool for Hyper-V, the tool collects the profile data from the node which is running and where the VM is running. 该工具不会从已关闭的节点中收集任何数据,但会跟踪该节点。The tool can't collect any data from a node that's turned off, but it will track that node. 该节点启用和运行后,此工具开始从其中收集 VM 配置文件数据(如果此 VM 是配置文件 VM 列表的一部分且在该节点上运行)。After the node is up and running, the tool starts collecting the VM profile data from it (if the VM is part of the profile VM list and is running on the node).
  • 如果 Site Recovery 保管库中的 Hyper-V 主机上的某个 VM 迁移到同一群集中的其他 Hyper-V 主机或迁移到独立主机,则该 VM 的复制不受影响。If a VM on a Hyper-V host in a Site Recovery vault migrates to a different Hyper-V host in the same cluster, or to a standalone host, replication for the VM isn't impacted. Hyper-V 主机必须满足先决条件,且必须在 Site Recovery 保管库中进行配置。The Hyper-V host must meet prerequisites, and be configured in a Site Recovery vault.

当 Hyper-V 在客户端操作系统上运行时,我可以保护 VM 吗?Can I protect VMs when Hyper-V is running on a client operating system?

不可以。VM 必须位于在受支持的 Windows 服务器计算机上运行的 Hyper-V 主机服务器上。No, VMs must be located on a Hyper-V host server that's running on a supported Windows server machine. 如果需要保护客户端计算机,可以将其作为物理计算机复制到 Azure。If you need to protect a client computer you could replicate it as a physical machine to Azure.

我可以将 Hyper-V 第 2 代虚拟机复制到 Azure 吗?Can I replicate Hyper-V generation 2 virtual machines to Azure?

是的。Yes. 站点恢复在故障转移过程中将从第 2 代转换成第 1 代。Site Recovery converts from generation 2 to generation 1 during failover. 在故障回复时,计算机将转换回到第 2 代。At failback the machine is converted back to generation 2.

是否可以使用 SDK 自动化 Site Recovery 方案?Can I automate Site Recovery scenarios with an SDK?

是的。Yes. 可以使用 Rest API、PowerShell 或 Azure SDK 将站点恢复工作流自动化。You can automate Site Recovery workflows using the Rest API, PowerShell, or the Azure SDK. 以下为通过 PowerShell 将 Hyper-V 复制到 Azure 的当前支持方案:Currently supported scenarios for replicating Hyper-V to Azure using PowerShell:

复制Replication

本地 VM 将复制到哪个位置?Where do on-premises VMs replicate to?

数据将复制到 Azure 存储。Data replicates to Azure storage. 运行故障转移时,Site Recovery 会自动从存储帐户创建 Azure VM。When you run a failover, Site Recovery automatically creates Azure VMs from the storage account.

可以复制哪些应用?What apps can I replicate?

可以复制任何运行符合复制要求的 Hyper-V VM 的应用或工作负荷均。You can replicate any app or workload running a Hyper-V VM that complies with replication requirements. Site Recovery 支持应用程序感知型复制,因此,应用可以故障转移或故障回复到智能状态。Site Recovery provides support for application-aware replication, so that apps can be failed over and failed back to an intelligent state. Site Recovery 除了与 Microsoft 应用程序(例如 SharePoint、Exchange、Dynamics、SQL Server 及 Active Directory)集成之外,还能与行业领先的供应商(包括 Oracle、SAP、IBM 及 Red Hat)紧密配合。Site Recovery integrates with Microsoft applications such as SharePoint, Exchange, Dynamics, SQL Server and Active Directory, and works closely with leading vendors, including Oracle, SAP, IBM and Red Hat. 详细了解工作负荷保护。Learn more about workload protection.

复制过程是什么?What's the replication process?

  1. 当触发初始复制时,系统会拍摄 Hyper-V VM 快照。When initial replication is triggered, a Hyper-V VM snapshot is taken.
  2. VM 上的虚拟硬盘是逐一复制的,直至全部复制到 Azure 为止。Virtual hard disks on the VM are replicated one by one, until they're all copied to Azure. 该过程可能需要一些时间,具体取决于 VM 大小和网络带宽。This might take a while, depending on the VM size, and network bandwidth. 了解如何增加网络带宽。Learn how to increase network bandwidth.
  3. 如果在初始复制期间发生磁盘更改,Hyper-V 副本复制跟踪器将跟踪这些更改,并将其记录在 Hyper-V 复制日志 (.hrl) 中。If disk changes occur while initial replication is in progress, the Hyper-V Replica Replication Tracker tracks the changes as Hyper-V replication logs (.hrl). 这些日志文件位于与磁盘相同的文件夹中。These log files are located in the same folder as the disks. 每个磁盘都有一个关联的 .hrl 文件,该文件将发送到辅助存储器。Each disk has an associated .hrl file that's sent to secondary storage. 当初始复制正在进行时,快照和日志将占用磁盘资源。The snapshot and log files consume disk resources while initial replication is in progress.
  4. 当初始复制完成时,将删除 VM 快照。When the initial replication finishes, the VM snapshot is deleted.
  5. 日志中的任何磁盘更改会进行同步,并合并到父磁盘中。Any disk changes in the log are synchronized and merged to the parent disk.
  6. 初始复制完成后,“在虚拟机上完成保护”作业将运行。After the initial replication finishes, the Finalize protection on the virtual machine job runs. 该作业会配置网络和其他复制后设置以便保护 VM。It configures network and other post-replication settings, so that the VM is protected.
  7. 在此阶段,可以检查 VM 设置以确保它已为故障转移做好准备。At this stage you can check the VM settings to make sure that it's ready for failover. 可针对 VM 运行灾难恢复钻取(测试故障转移)来检查它是否按预期进行故障转移。You can run a disaster recovery drill (test failover) for the VM, to check that it fails over as expected.
  8. 在完成初始复制后,根据复制策略开始增量复制同步。After the initial replication, delta replication begins, in accordance with the replication policy.
  9. 更改是所记录的 .hrl 文件。Changes are logged .hrl files. 为复制配置的每个磁盘都有一个关联的 .hrl 文件。Each disk that's configured for replication has an associated .hrl file.
  10. 此日志会发送到客户的存储帐户。The log is sent to the customer's storage account. 当日志正处于传输到 Azure 的过程中时,主磁盘中的变更会记录到同一文件夹的另一日志文件中。When a log is in transit to Azure, the changes in the primary disk are tracked in another log file, in the same folder.
  11. 在初始复制和增量复制过程中,均可以在 Azure 门户中监视 VM。During both initial and delta replication, you can monitor the VM in the Azure portal.

详细了解复制过程。Learn more about the replication process.

是否可以使用站点到站点 VPN 复制到 Azure?Can I replicate to Azure with a site-to-site VPN?

Site Recovery 通过公共终结点或使用 ExpressRoute Azure 对等互连将数据从本地复制到 Azure 存储。Site Recovery replicates data from on-premises to Azure storage over a public endpoint, or using ExpressRoute Azure peering. 不支持通过站点到站点 VPN 网络进行的复制。Replication over a site-to-site VPN network isn't supported.

是否可以使用 ExpressRoute 复制到 Azure?Can I replicate to Azure with ExpressRoute?

可以使用 ExpressRoute 将 VM 复制到 Azure。Yes, ExpressRoute can be used to replicate VMs to Azure. Site Recovery 通过公共终结点将数据复制到 Azure 存储帐户。需要设置 对等互连才能进行 Site Recovery 复制。Site Recovery replicates data to an Azure Storage Account over a public endpoint, and you need to set up Azure peering for Site Recovery replication. 将 VM 故障转移到 Azure 虚拟网络后,可以使用专用对等互连访问这些 VM。After VMs fail over to an Azure virtual network, you can access them using private peering.

为何不能通过 VPN 复制?Why can't I replicate over VPN?

复制到 Azure 时,复制流量将到达 Azure 存储帐户的公共终结点。When you replicate to Azure, replication traffic reaches the public endpoints of an Azure Storage account. 因此,只能使用 ExpressRoute(Azure 对等互连)通过公共 Internet 进行复制,VPN 不适用。Thus you can only replicate over the public internet with ExpressRoute (Azure peering), and VPN doesn't work.

复制的 VM 要满足哪些要求?What are the replicated VM requirements?

若要复制某个 Hyper-V VM,该 VM 必须运行受支持的操作系统。For replication, a Hyper-V VM must be running a supported operating system. 此外,该 VM 必须满足 Azure VM 的要求。In addition, the VM must meet the requirements for Azure VMs. 在支持矩阵中了解详细信息Learn more in the support matrix.

为什么将虚拟机磁盘复制到高级存储需要使用额外的标准存储帐户?Why is an additional standard storage account required if I replicate my virtual machine disks to premium storage?

将本地虚拟机/物理服务器复制到高级存储时,驻留在受保护计算机磁盘上的所有数据都将复制到高级存储帐户。When you replicate your on-premises virtual machines/physical servers to premium storage, all the data residing on the protected machine's disks is replicated to the premium storage account. 需要额外的标准存储帐户来存储复制日志。An additional standard storage account is required for storing replication logs. 复制磁盘数据的初始阶段完成之后,将持续跟踪对本地磁盘数据的所有更改,并将其作为复制日志存储到这一额外的标准存储帐户中。After the initial phase of replicating disk data is complete, all changes to the on-premises disk data are tracked continuously and stored as replication logs in this additional standard storage account.

可以多久复制到 Azure 一次?How often can I replicate to Azure?

可以每隔 30 秒(高级存储除外)或 5 分钟复制一次 Hyper-V VM。Hyper-V VMs can be replicated every 30 seconds (except for premium storage) or 5 minutes.

Azure Site Recovery 和 Hyper-V 副本能否在 Hyper-V 计算机上一起配置?Can Azure Site Recovery and Hyper-V Replica be configured together on a Hyper-V machine?

可以,Azure Site Recovery 和 Hyper-V 副本可以为计算机一起配置。Yes, both Azure Site Recovery and Hyper-V Replica can be configured together for a machine. 但是,必须将计算机作为物理计算机进行保护,并使用配置/进程服务器将其复制到 Azure。But the machine will have to protected as a physical machine and will be replicated to Azure using a Configuration / Process server. 此处详细了解如何保护物理计算机。Learn more about protecting physical machines here.

是否可以扩展复制?Can I extend replication?

Azure 中国世纪互联目前不支持扩展复制或链式复制。Extended or chained replication isn't supported on Azure China 21Vianet currently.

是否可以执行脱机初始复制?Can I do an offline initial replication?

Azure 中国世纪互联目前不支持这种情况。This isn't supported on Azure China 21Vianet currenlty.

是否可以排除磁盘?Can I exclude disks?

可以从复制中排除磁盘。Yes, you can exclude disks from replication.

是否可以复制包含动态磁盘的 VM?Can I replicate VMs with dynamic disks?

可以复制动态磁盘。Dynamic disks can be replicated. 操作系统磁盘必须为基本磁盘。The operating system disk must be a basic disk.

安全性Security

Site Recovery 需要对 Hyper-V 主机拥有哪些访问权限?What access does Site Recovery need to Hyper-V hosts

Site Recovery 需要对 Hyper-V 主机具备访问权限才能复制所选的 VM。Site Recovery needs access to Hyper-V hosts to replicate the VMs you select. Site Recovery 在 Hyper-V 主机上安装以下代理:Site Recovery installs the following on Hyper-V hosts:

  • 如果不运行 VMM,则在每个主机上安装 Azure Site Recovery 提供程序和恢复服务代理。If you're not running VMM, the Azure Site Recovery Provider and Recovery Services agent are installed on each host.
  • 如果运行 VMM,则在每个主机上安装恢复服务代理。If you're running VMM, the Recovery Services agent is installed on each host. 此提供程序在 VMM 服务器上运行。The Provider runs on the VMM server.

Site Recovery 在 Hyper-V VM 上安装什么内容?What does Site Recovery install on Hyper-V VMs?

Site Recovery 不会在启用复制的 Hyper-V VM 上显式安装任何内容。Site Recovery doesn't explicitly install anything on Hyper-V VMs enabled for replication.

故障转移和故障回复Failover and failback

如何故障转移到 Azure?How do I fail over to Azure?

可以运行从本地 Hyper-V VM 到 Azure 的计划内或计划外故障转移。You can run a planned or unplanned failover from on-premises Hyper-V VMs to Azure.

  • 如果运行计划的故障转移,源 VM 将关闭以确保不会丢失数据。If you run a planned failover, then source VMs are shut down to ensure no data loss.
  • 如果无法访问主站点,可以运行计划外故障转移。You can run an unplanned failover if your primary site isn't accessible.
  • 可以故障转移单个虚拟机,或者创建恢复计划来协调多个虚拟机的故障转移。You can fail over a single machine, or create recovery plans, to orchestrate failover of multiple machines.
  • 故障转移分为两部分:Failover is in two parts:
    • 故障转移的第一阶段完成后,应该会在 Azure 中看到创建的副本 VM。After the first stage of failover completes, you should be able to see the created replica VMs in Azure. 如果需要,可向 VM 分配公共 IP 地址。You can assign a public IP address to the VM if required.
    • 然后,提交故障转移以开始从副本 Azure VM 访问工作负载。You then commit the failover, to start accessing the workload from the replica Azure VM.

故障转移后如何访问 Azure VM?How do I access Azure VMs after failover?

故障转移后,可以通过安全的 Internet 连接、站点到站点 VPN 或 Azure ExpressRoute 来访问 Azure VM。After failover, you can access Azure VMs over a secure Internet connection, over a site-to-site VPN, or over Azure ExpressRoute. 在连接之前需要做许多准备。You'll need to prepare a number of things in order to connect. 了解详细信息Learn more.

故障转移的数据是否有复原能力?Is failed over data resilient?

Azure 具有复原能力。Azure is designed for resilience. Site Recovery 能够根据 Azure SLA 故障转移到辅助 Azure 数据中心。Site Recovery is engineered for failover to a secondary Azure datacenter, in accordance with the Azure SLA. 发生故障转移时,我们会确保元数据和保管库保留在为保管库选择的同一地理区域中。When failover occurs, we make sure your metadata and vaults remain within the same geographic region that you chose for your vault.

故障转移是自动发生的吗?Is failover automatic?

故障转移不是自动的。Failover isn't automatic. 可以在门户中单击一下鼠标来启动故障转移,也可以使用 PowerShell 来触发故障转移。You initiate failovers with single click in the portal, or you can use PowerShell to trigger a failover.

如何故障回复?How do I fail back?

在本地基础结构启动并再次运行后,即可进行故障回复。After your on-premises infrastructure is up and running again, you can fail back. 故障回复会出现在以下三个阶段:Failback occurs in three stages:

  1. 可以使用以下不同选项启动从 Azure 到本地站点的计划内故障转移:You kick off a planned failover from Azure to the on-premises site using a couple of different options:

    • 最大限度减少停机时间:如果使用此选项,Site Recovery 将在故障转移之前同步数据。Minimize downtime: If you use this option Site Recovery synchronizes data before failover. 它会检查更改的数据块并将它们下载到本地站点,同时让 Azure VM 保持运行并最大限度减少停机时间。It checks for changed data blocks and downloads them to the on-premises site, while the Azure VM keeps running, minimizing downtime. 当手动指定故障转移应完成时,Azure VM 会关闭,任何最终增量更改会被复制,而故障转移将启动。When you manually specify that the failover should complete, the Azure VM is shut down, any final delta changes are copied, and the failover starts.
    • 完整下载:使用此选项可在故障转移期间同步数据。Full download: With this option data is synchronized during failover. 此选项会下载整个磁盘。This option downloads the entire disk. 该操作更快,因为不计算校验和,但停机时间会增加。It's faster because no checksums are calculated, but there's more downtime. 如果运行副本 Azure VM 已有一段时间,或者如果本地 VM 已删除,请使用此选项。Use this option if you've been running the replica Azure VMs for some time, or if the on-premises VM was deleted.
  2. 可选择故障回复到同一 VM 或备用 VM。You can select to fail back to the same VM or to an alternate VM. 如果 VM 尚不存在,可指定 Site Recovery 应创建 VM。You can specify that Site Recovery should create the VM if it doesn't already exist.

  3. 初始数据同步完成后,选择完成故障转移。After initial synchronization finishes, you select to complete the failover. 该操作完成后,可以登录到本地 VM 验证一切是否按预期运行。After it completes, you can sign in to the on-premises VM to check everything's working as expected. 在 Azure 门户中,可以看到 Azure VM 均已停止。In the Azure portal, you can see that the Azure VMs have been stopped.

  4. 完成故障转移的提交,并重新开始从本地 VM 访问工作负载。You commit the failover to finish up, and start accessing the workload from the on-premises VM again.

  5. 在工作负载进行故障回复后,启用反向复制,以便本地 VM 重新复制到 Azure。After workloads have failed back, you enable reverse replication, so that the on-premises VMs replicate to Azure again.

是否可以故障回复到不同位置?Can I fail back to a different location?

可以。故障转移到 Azure 后,如果原始位置不可用,可以故障回复到不同的位置。Yes, if you failed over to Azure, you can fail back to a different location if the original one isn't available. 了解详细信息Learn more.