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

本文解答有关如何使用 Azure Site Recovery 服务进行到另一 Azure 区域的 Azure VM 灾难恢复的常见问题。This article answers common questions about disaster recovery of Azure VMs to another Azure region, using the Azure Site Recovery service.

常规General

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

了解 Azure VM 灾难恢复的费用Learn about cost for Azure VM disaster recovery.

免费层如何工作?How does the free tier work?

每个使用 Site Recovery 保护的实例在前 31 天均可免费享受保护。Every instance that's protected with Site Recovery is free for the first 31 days of protection. 在该时间段后,对每个实例的保护将按照定价详细信息中汇总的费率进行收费。After that period, protection for each instance is at the rates summarized in pricing details. 你可以使用 Azure 定价计算器估算费用。You can estimate costs using the Azure pricing calculator.

在前 31 天内是否会产生其他 Azure 费用?Do I incur other Azure charges in the first 31 days?

是的。Yes. 尽管 Azure Site Recovery 在实例受保护的前 31 天是免费的,但你可能需要支付 Azure 存储、存储交易和数据传输费用。Even though Azure Site Recovery is free during the first 31 days of a protected instance, you might incur charges for Azure Storage, storage transactions, and data transfers. 恢复后的 VM 也可能会产生 Azure 计算费用。A recovered VM might also incur Azure compute charges.

VM 灾难恢复如何入门?How do I get started with Azure VM disaster recovery?

  1. 了解 Azure VM 灾难恢复体系结构。Understand the Azure VM disaster recovery architecture.
  2. 查看支持要求。Review support requirements.
  3. 设置 Azure VM 灾难恢复。Set up disaster recovery for Azure VMs.
  4. 使用测试故障转移运行灾难恢复演练Run a disaster recovery drill with a test failover.
  5. 对次要 Azure 区域运行完全故障转移Run a full failover to a secondary Azure region.
  6. 从次要区域故障转移回主要区域。Fail back from the secondary region to the primary region.

如何确保目标区域中的容量?How do we ensure capacity in the target region?

Site Recovery 团队和 Azure 容量管理团队规划了足够的基础结构容量。The Site Recovery team, and the Azure capacity management team, plan for sufficient infrastructure capacity. 启动故障转移时,团队还会帮助确保将受 Site Recovery 保护的 VM 实例部署到目标区域。When you start a failover, the teams also help ensure that VM instances protected by Site Recovery deploy to the target region.

复制Replication

是否可以复制包含磁盘加密的 VM?Can I replicate VMs with disk encryption?

是的。Yes. Site Recovery 支持对已启用 Azure 磁盘加密 (ADE) 的 VM 进行灾难恢复。Site Recovery supports disaster recovery of VMs that have Azure Disk Encryption (ADE) enabled. 启用复制后,Azure 会将所有必需的磁盘加密密钥和机密从用户上下文中的源区域复制到目标区域。When you enable replication, Azure copies all the required disk encryption keys and secrets from the source region to the target region, in the user context. 如果你没有所需的权限,则安全管理员可以使用脚本来复制密钥和机密。If you don't have required permissions, your security administrator can use a script to copy the keys and secrets.

  • Site Recovery 支持运行 Windows 的 Azure VM 的 ADE。Site Recovery supports ADE for Azure VMs running Windows.
  • Site Recovery 支持:Site Recovery supports:
    • ADE 版本 0.1,该版本包含需要 Azure Active Directory (Azure AD) 的架构。ADE version 0.1, which has a schema that requires Azure Active Directory (Azure AD).
    • ADE 版本 1.1,该版本无需 Azure AD。ADE version 1.1, which doesn't require Azure AD. 对于版本 1.1,Windows Azure VM 必须具有托管磁盘。For version 1.1, Windows Azure VMs must have managed disks.
    • 了解详细信息Learn more. 有关扩展架构的信息。about the extension schemas.

详细了解如何为加密 VM 启用复制。Learn more about enabling replication for encrypted VMs.

是否可以从不同的资源组中选择自动化帐户?Can I select an automation account from a different resource group?

当允许 Site Recovery 为在复制的 Azure VM 上运行的出行服务扩展管理更新时,它会通过 Azure 自动化帐户部署全局 runbook(由 Azure 服务使用)。When you allow Site Recovery to manage updates for the Mobility service extension running on replicated Azure VMs, it deploys a global runbook (used by Azure services), via an Azure automation account. 可以使用 Site Recovery 创建的自动化帐户,也可以选择使用现有的自动化帐户。You can use the automation account that Site Recovery creates, or select to use an existing automation account.

当前,在门户中,只能选择与保管库位于同一资源组中的自动化帐户。Currently, in the portal, you can only select an automation account in the same resource group as the vault. 你可以使用 PowerShell 从不同的资源组中选择自动化帐户。You can select an automation account from a different resource group using PowerShell.

如果我使用的客户自动化帐户不在保管库资源组中,是否可以删除默认的 runbook?If I use a customer automation account that's not in the vault resource group, can I delete the default runbook?

是,如果不需要它,可以将其删除。Yes, you can delete it if you don't need it.

是否可将 VM 复制到另一个订阅?Can I replicate VMs to another subscription?

是,可以将 Azure VM 复制到同一 Azure AD 租户中的任何订阅。Yes, you can replicate Azure VMs to any subscription within the same Azure AD tenant. 为 VM 启用灾难恢复时,默认情况下显示的目标订阅是源 VM 的订阅。When you enable disaster recovery for VMs, by default the target subscription shown is that of the source VM. 你可以修改目标订阅,其他设置(如资源组和虚拟网络)将根据所选的订阅自动填充。You can modify the target subscription, and other settings (such as resource group and virtual network), are populated automatically from the selected subscription.

是否可从复制中排除磁盘?Can I exclude disks from replication?

是,你可以在使用 PowerShell 设置复制时排除磁盘。Yes, you can exclude disks when you set up replication, using PowerShell. 了解详细信息Learn more.

是否可以复制添加到复制的 VM 的新磁盘?Can I replicate new disks added to replicated VMs?

对于具有托管磁盘的复制的 VM,可以添加新磁盘,并为其启用复制。For replicated VMs with managed disks, you can add new disks, and enable replication for them. 添加新磁盘时,复制的 VM 将显示一条警告消息,指出 VM 上的一个或多个磁盘可用于保护。When you add a new disk, the replicated VM shows a warning message that one or more disks on the VM are available for protection.

  • 如果为添加的磁盘启用复制,此警告会在初次复制后消失。If you enable replication for the added disks, the warning disappears after the initial replication.
  • 如果你不想为磁盘启用复制,则可以消除警告。If you don't want to enable replication for the disk, you can dismiss the warning.
  • 如果对添加了磁盘的 VM 进行故障转移,复制点将显示可用于恢复的磁盘。If you fail over a VM with added disks, replication points show the disks available for recovery. 例如,如果向包含一个磁盘的 VM 添加第二个磁盘,则在添加之前创建的复制点会显示为“第 1 个磁盘,共 2 个”。For example, if you add a second disk to a VM with one disk, a replication point created before you added shows as "1 of 2 disks."

Site Recovery 不支持将磁盘从复制的 VM 中“热删除”。Site Recovery doesn't support "hot remove" of disks from a replicated VM. 如果删除某个 VM 磁盘,则需先禁用该 VM 的复制,然后为其重新启用复制。If you remove a VM disk, you need to disable and then reenable replication for the VM.

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

将 Azure VM 复制到另一个 Azure 区域时,复制是持续性的。Replication is continuous when replicating Azure VMs to another Azure region. 详细了解复制的工作原理。Learn more about how replication works.

是否可以在某个区域中复制虚拟机?Can I replicate virtual machines within a region?

不能使用 Site Recovery 在区域中复制磁盘。You can't use Site Recovery to replicate disks within a region.

能否将 VM 实例复制到任意 Azure 区域?Can I replicate VM instances to any Azure region?

可以在同一地理群集中的任意两个区域之间复制和恢复 VM。You can replicate and recover VMs between any two regions within the same geographic cluster. 地理群集的定义考虑到了数据延迟和主权。Geographic clusters are defined with data latency and sovereignty in mind. 详细了解区域支持。Learn more about region support.

Site Recovery 是否需要建立 Internet 连接?Does Site Recovery need internet connectivity?

不需要,但 VM 需要访问 Site Recovery URL 和 IP 范围。No, but VMs need access to Site Recovery URLs and IP ranges. 了解详细信息Learn more.

是否可以跨资源组分层复制应用程序?Can I replicate an application tiered across resource groups?

是,你可以复制应用并在另一个资源组中保留灾难恢复配置。Yes, you can replicate the app, and keep the disaster recovery configuration in a separate resource group.

例如,如果应用在不同的资源组中有三个层(应用程序/数据库/web),则需要启用三次复制,才能保护所有层。For example, if the apps has three tiers (application/database/web) in different resource groups, you need to enable replication three times, to protect all tiers. Site Recovery 会将这三个层复制到三个不同的资源组中。Site Recovery replicates the three tiers into three different resource groups.

能否跨资源组移动存储帐户?Can I move storage accounts across resource groups?

否,不支持这种情况。No, this is unsupported. 如果你意外地将存储帐户移到不同的资源组并删除了原始资源组,则可以创建一个与旧资源组同名的新资源组,然后将该存储帐户移到此资源组。If you accidentally move storage accounts to a different resource group and delete the original resource group, then you can create a new resource group with the same name as the old resource group, and then move the storage account to this resource group.

复制策略Replication policy

什么是复制策略?What is a replication policy?

复制策略定义恢复点的保留历史记录,以及应用一致性快照的频率。A replication policy defines the retention history of recovery points, and the frequency of app-consistent snapshots. Site Recovery 创建默认复制策略,如下所示:Site Recovery creates a default replication policy as follows:

  • 将恢复点保留 24 小时。Retain recovery points for 24 hours.
  • 每 4 小时捕获一次应用一致性快照。Take app-consistent snapshots every four hours.

详细了解复制设置。Learn more about replication settings.

什么是崩溃一致性恢复点?What's a crash-consistent recovery point?

崩溃一致性恢复点包含创建快照期间拔下服务器的电源线时磁盘上的数据。A crash-consistent recovery point contains on-disk data, as if you pulled the power cord from the server during the snapshot. 它不包括创建快照时内存中存在的任何数据。It doesn't include anything that was in memory when the snapshot was taken.

目前,大多数应用都可以从崩溃一致性快照正常恢复。Today, most apps can recover well from crash-consistent snapshots. 对于无数据库的操作系统以及应用(如文件服务器、DHCP 服务器、打印服务器),崩溃一致性恢复点通常已足够。A crash-consistent recovery point is usually enough for non-database operating systems, and apps such as file servers, DHCP servers, and print servers.

Site Recovery 每隔五分钟自动创建一个崩溃一致性恢复点。Site Recovery automatically creates a crash-consistent recovery point every five minutes.

什么是应用程序一致性恢复点?What's an application-consistent recovery point?

应用一致性恢复点是基于应用一致性快照创建的。App-consistent recovery points are created from app-consistent snapshots. 它们捕获的数据与崩溃一致性快照相同,此外还会捕获内存中的数据,以及进程中的所有事务。They capture the same data as crash-consistent snapshots, and in addition capture data in memory, and all transactions in process.

由于包含额外的内容,应用一致性快照涉及的操作最多,且花费的时间最长。Because of extra content, app-consistent snapshots are the most involved, and take the longest. 我们建议对数据库操作系统以及 SQL Server 等应用使用应用一致性恢复点。We recommend app-consistent recovery points for database operating systems, and apps such as SQL Server. 对于 Windows,应用一致性快照使用卷影复制服务 (VSS)。For Windows, app-consistent snapshots use the Volume Shadow Copy Service (VSS).

应用一致性恢复点是否会影响性能?Do app-consistent recovery points impact performance?

因为应用一致性恢复点会捕获内存和进程中的所有数据,如果它们频繁地捕获,则在工作负载已经很繁忙的情况下可能会影响性能。Because app-consistent recovery points capture all data in memory and process, if they capture frequently, it can affect performance when the workload is already busy. 对于无数据库工作负载,我们建议不要太频繁地进行捕获。We don't recommend that you capture too often for non-database workloads. 即使对于数据库工作负载,一小时也应该足以满足需要。Even for database workloads, one hour should be enough.

生成应用一致性恢复点的最小频率是多少?What's the minimum frequency for generating app-consistent recovery points?

Site Recovery 可以创建应用一致性恢复点,其最小频率为一小时。Site Recovery can create app-consistent recovery points with a minimum frequency of one hour.

是否可以为 Linux VM 启用应用一致性复制?Can I enable app-consistent replication for Linux VMs?

是的。Yes. 适用于 Linux 的移动代理支持用于应用一致性的自定义脚本。The Mobility agent for Linux support custom scripts for app-consistency. 该代理使用带有前置和后置选项的自定义脚本。A custom script with pre and post-options is used by the agent. 了解详细信息Learn more

如何生成和保存恢复点?How are recovery points generated and saved?

为了了解 Site Recovery 如何生成恢复点,让我们使用一个示例。To understand how Site Recovery generates recovery points, let's use an example.

  • 复制策略将恢复点保留 24 小时,并每小时获取一个应用一致性频率快照。A replication policy retains recovery points for 24 hours, and takes an app-consistent frequency snapshot every hour.
  • Site Recovery 每隔五分钟创建一个崩溃一致性恢复点。Site Recovery creates a crash-consistent recovery point every five minutes. 你无法更改此频率。You can't change this frequency.
  • Site Recovery 在一小时后删除恢复点,每小时保存一个点。Site Recovery prunes recovery points after an hour, saving one point per hour.

因此,在过去一小时,可以从 12 个崩溃一致性恢复点和 1 个应用一致性恢复点中进行选择,如图所示。So, in the last hour, you can choose from 12 crash-consistent points, and one app-consistent point, as shown in the graphic.

生成的恢复点列表

可以恢复到哪个最早的时间点?How far back can I recover?

可以使用的最早恢复点是 72 小时。The oldest recovery point that you can use is 72 hours.

如果 Site Recovery 无法生成恢复点超过 24 小时,会发生什么情况?What happens if Site Recovery can't generate recovery points for more than 24 hours?

如果复制策略为 24 小时,并且 Site Recovery 无法生成恢复点超过 24 小时,则将保留旧恢复点。If you have a replication policy of 24 hours, and Site Recovery can't generate recovery points for more than 24 hours, your old recovery points remain. Site Recovery 仅在生成新点时替换最旧的点。Site Recovery only replaces the oldest point if it generates new points. 到达保留期之后,在出现新的恢复点之前,所有旧恢复点将会保留。Until there are new recovery points, all the old points remain after you reach the retention window.

启用复制后,是否可以更改复制策略?Can I change the replication policy after replication is enabled?

是的。Yes. 在保管库 >“Site Recovery 基础结构” > “复制策略”中,选择并编辑策略 。In the vault > Site Recovery Infrastructure > Replication policies, select and edit the policy. 更改也适用于现有策略。Changes apply to existing policies too.

是否所有恢复点都是完整的 VM 副本?Are all recovery points a complete VM copy?

生成的第一个恢复点包含完整副本。The first recovery point that's generated has the complete copy. 后续恢复点包含增量更改。Successive recovery points have delta changes.

恢复点保留期的增加是否会增加存储费用?Do increases in recovery point retention increase storage costs?

是的。Yes. 例如,如果将保留期从 24 小时增大到 72 小时,则 Site Recovery 会保存额外 48 小时的恢复点。For example, if you increase retention from 24 hours to 72, Site Recovery saves recovery points for an additional 48 hours. 添加的时间会导致存储更改。The added time incurs storage changes. 例如,如果单个恢复点包含 10 GB 的增量更改,每 GB 费用为 0.16 美元/月,则每月会产生 1.60 美元 × 48 的额外费用。As an example only, if a single recovery point had delta changes of 10 GB, with a per-GB cost of $0.16 per month, then additional charges would be $1.60 × 48 per month.

多 VM 一致性Multi-VM consistency

什么是多 VM 一致性?What is multi-VM consistency?

多 VM 一致性可以确保恢复点在复制的虚拟机之间保持一致。Multi-VM consistency ensures that recovery points are consistent across replicated virtual machines.

  • 当启用多 VM 一致性时,Site Recovery 会创建启用了该选项并包含所有计算机的复制组。When you enable multi-VM consistency, Site Recovery creates a replication group of all the machines with the option enabled.
  • 对复制组中的计算机进行故障转移时,它们共享崩溃一致性恢复点和应用一致性恢复点。When you fail over the machines in the replication group, they have shared crash-consistent and app-consistent recovery points.

了解如何启用多 VM 一致性。Learn how to enable multi-VM consistency.

是否可以对复制组中的单个 VM 进行故障转移?Can I fail over a single VM in a replication group?

不是。No. 启用多 VM 一致性时,它会推断应用依赖于复制组中的所有 VM,并且不允许对单个 VM 进行故障转移。When you enable multi-VM consistency, it infers that an app has a dependency on all VMs in the replication group, and single VM failover isn't allowed.

可以在一个组中同时复制多少个 VM?How many VM can I replicate together in a group?

在一个复制组中,可以一同复制 16 个 VM。You can replicate 16 VMs together in a replication group.

何时应启用多 VM 一致性?When should I enable multi-VM consistency?

由于多 VM 一致性会占用大量 CPU 资源,启用它可能会影响工作负载性能。Multi-VM consistency is CPU intensive, and enabling it can affect workload performance. 仅当 VM 运行相同的工作负载并且需要在多个计算机之间保持一致时才启用。Enable only if VMs are running the same workload, and you need consistency across multiple machines. 例如,如果应用程序中有两个 SQL Server 实例和两个 Web 服务器,则只为 SQL Server 实例启用多 VM 一致性。For example, if you have two SQL Server instances and two web servers in an application, enable multi-VM consistency for the SQL Server instances only.

是否可以将复制的 VM 添加到复制组?Can I add a replicating VM to a replication group?

为 VM 启用复制时,可以将其添加到新的复制组或现有组中。When you enable replication for a VM, you can add it to a new replication group, or to an existing group. 无法添加已复制到组中的 VM。You can't add a VM that's already replicating to a group.

故障转移Failover

如何确保目标区域中的容量?How do we ensure capacity in the target region?

Site Recovery 团队和 Azure 容量管理团队规划了足够的基础结构容量。The Site Recovery team, and Azure capacity management team, plan for sufficient infrastructure capacity. 启动故障转移时,团队还会帮助确保受 Site Recovery 保护的 VM 实例可以部署到目标区域。When you start a failover, the teams also help ensure VM instances that are protected by Site Recovery can deploy to the target region.

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

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

是否可以在故障转移后保留公共 IP 地址?Can I keep a public IP address after failover?

无法在故障转移后保留生产应用的公共 IP 地址。You can't keep the public IP address for a production app after a failover.

在故障转移过程中启动某个工作负载时,需要为其分配一个 Azure 公共 IP 地址资源。When you bring up a workload as part of the failover process, you need to assign an Azure public IP address resource to it. 该资源必须在目标区域中可用。The resource must be available in the target region. 可以手动分配 Azure 公共 IP 地址资源,也可以使用恢复计划来自动分配。You can assign the Azure public IP address resource manually, or you can automate it with a recovery plan. 了解如何设置故障转移后的公共 IP 地址。Learn how to set up public IP addresses after failover.

是否可以在故障转移后保留专用 IP 地址?Can I keep a private IP address after failover?

是的。Yes. 默认情况下,为 Azure VM 启动灾难恢复时,Site Recovery 将根据源资源设置创建目标资源。By default, when you enable disaster recovery for Azure VMs, Site Recovery creates target resources, based on source resource settings. 对于配置有静态 IP 地址的 Azure VM,Site Recovery 将尝试对目标 VM 预配相同的 IP 地址(如果未占用)。For Azure VMs configured with static IP addresses, Site Recovery tries to provision the same IP address for the target VM, if it's not in use. 详细了解如何在故障转移后保留 IP 地址。Learn more about keeping IP addresses after failover.

为什么在故障转移后为 VM 分配了新的 IP 地址?Why is a VM assigned a new IP address after failover?

故障转移时,Site Recovery 会尽量提供 IP 地址。Site Recovery tries to provide the IP address at the time of failover. 如果该地址被另一个 VM 使用,则 Site Recovery 会将下一个可用 IP 地址设为目标。If another VM uses that address, Site Recovery sets the next available IP address as the target.

详细了解如何设置虚拟网络的网络映射和 IP 寻址。Learn more about setting up network mapping and IP addressing for virtual networks.

什么是最新恢复点?What's the Latest recovery point?

“最新(最低 RPO)”恢复点选项执行以下操作:The Latest (lowest RPO) recovery point option does the following:

  1. 它首先处理已发送到 Site Recovery 的所有数据。It first processes all the data that has been sent to Site Recovery.
  2. 服务处理数据后,将为每个 VM 创建恢复点,然后故障转移到该 VM。After the service processes the data, it creates a recovery point for each VM, before failing over to the VM. 此选项提供了最低恢复点目标 (RPO)。This option provides the lowest recovery point objective (RPO).
  3. 故障转移后创建的 VM 包含触发故障转移时复制到 Site Recovery 的所有数据。The VM created after failover has all the data replicated to Site Recovery, from when the failover was triggered.

“最新”恢复点是否会影响故障转移 RTO?Do latest recovery points impact failover RTO?

是的。Yes. Site Recovery 在故障转移之前需要处理所有挂起的数据,因此,此选项的恢复时间目标 (RTO) 比其他选项更高。Site Recovery processes all pending data before failing over, so this option has a higher recovery time objective (RTO) than other options.

什么是“最新已处理”恢复选项?What's the Latest processed recovery option?

“最新已处理”选项将执行以下操作:The Latest processed option does the following:

  1. 它将所有 VM 故障转移到由 Site Recovery 处理的最新恢复点。It fails over all VMs to the latest recovery point processed by Site Recovery . 此选项提供低的 RTO,因为无需费时处理未经处理的数据。This option provides a low RTO, because no time is spent processing unprocessed data.

如果主要区域发生意外中断怎么办?What if there's an unexpected outage in the primary region?

可以启动故障转移。You can start failover. Site Recovery 不需要从主要区域进行连接,即可执行故障转移。Site Recovery doesn't need connectivity from the primary region to do the failover.

什么是 VM 故障转移的 RTO?What is the RTO of a VM failover?

Site Recovery 的 RTO SLA 为两小时Site Recovery has an RTO SLA of two hours. 大多数情况下,Site Recovery 会在几分钟内对 VM 进行故障转移。Most of the time, Site Recovery fails over VMs within minutes. 若要计算 RTO,请查看故障转移作业,该作业显示启动 VM 所需的时间。To calculate the RTO, review the failover job, which shows the time it took to bring up a VM.

恢复计划Recovery plans

什么是恢复计划?What's a recovery plan?

Site Recovery 中的恢复计划可以协调 VM 的故障转移和恢复。A recovery plan in Site Recovery orchestrates the failover and recovery of VMs. 它有助于实现恢复的一致准确性、可重复性和自动化。It helps make recovery consistently accurate, repeatable, and automated. 此选项执行以下操作:It does the following:

  • 定义一组一起进行故障转移的 VMDefines a group of VMs that fail over together
  • 定义 VM 之间的依赖关系,使应用程序能够适时启动。Defines the dependencies between VMs, so that the application comes up accurately.
  • 自动恢复,可以选择对 VM 故障转移以外的任务执行自定义手动操作。Automates recovery, with the option of custom manual actions for tasks other than VM failover.

排序如何工作?How does sequencing work?

在恢复计划中,可以创建多个 VM 组进行排序。In a recovery plan, you can create multiple groups of VM for sequencing. 一次只能对一个组进行故障转移,因此属于同一组的 VM 会一起进行故障转移。Groups fails over one at one time, so that VMs that are part of the same group fail over together. 了解详细信息Learn more.

如何找到恢复计划的 RTO?How can I find the RTO of a recovery plan?

若要检查恢复计划的 RTO,请对恢复计划执行测试故障转移。To check the RTO of a recovery plan, do a test failover for the recovery plan. 在“Site Recovery 作业”中,检查测试故障转移持续时间。In Site Recovery jobs, check the test failover duration. 在示例屏幕截图中,“SAPTestRecoveryPlan”测试故障转移作业耗时 8 分 59 秒。In the example screenshot, the SAPTestRecoveryPlan test failover job took 8 minutes and 59 seconds.

列出显示 RTO 的测试故障转移持续时间的作业

重新保护和故障回复Reprotection and failback

故障转移后,次要区域中的 VM 是否自动受到保护?After failover, are VMs in the secondary region protected automatically?

不是。No. 将 VM 从一个区域故障转移到另一个区域后,VM 将在目标灾难恢复区域中启动,但处于不受保护状态。When you fail over VMs from one region to another, the VMs start up in the target disaster recovery region in an unprotected state. 若要重新保护次要区域中的 VM,可以启用到主要区域的复制。To reprotect VMs in the secondary region, you enable replication back to the primary region.

重新保护时,是否将所有数据从次要区域复制到主要区域?When I reprotect, is all data replicated from the secondary region to primary?

不一定。如果源区域 VM 存在,则只会同步源磁盘与目标磁盘之间的更改。It depends.If the source region VM exists, then only changes between the source disk and the target disk are synchronized. Site Recovery 将磁盘与不同的磁盘进行比较,然后传输数据。Site Recovery compares the disks to what's different, and then it transfers the data. 此过程通常需要几个小时。This process usually takes a few hours. 了解详细信息Learn more.

故障回复需要多长时间?How long does it take fail back?

完成重新保护后,故障回复所需的时间类似于从主要区域故障转移到次要区域所需的时间。After reprotection, failback takes about the same amount of time it took to fail over from the primary region to a secondary region.

容量Capacity

如何确保目标区域中的容量?How do we ensure capacity in the target region?

Site Recovery 团队和 Azure 容量管理团队计划了足够的基础结构容量。The Site Recovery team and Azure capacity management team plan for sufficient infrastructure capacity. 启动故障转移时,团队还会帮助确保受 Site Recovery 保护的 VM 实例可以部署到目标区域。When you start a failover, the teams also help ensure VM instances that are protected by Site Recovery can deploy to the target region.

安全性Security

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

否。Site Recovery 不会截获已复制数据,也不包含 VM 上运行的组件的任何相关信息。No, Site Recovery doesn't intercept replicated data, and it doesn't have any information about what's running on your VMs. 只有协调复制与故障转移所需的元数据将发送到站点恢复服务。Only the metadata needed to orchestrate replication and failover is sent to the Site Recovery service.

Site Recovery 获得了 ISO 27001:2013、27018、HIPAA 和 DPA 认证。Site Recovery is ISO 27001:2013, 27018, HIPAA, and DPA certified. 此服务正在接受 SOC2 和 FedRAMP JAB 评估。The service is undergoing SOC2 and FedRAMP JAB assessments.

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

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

后续步骤Next steps