有关 Azure Site Recovery 的一般问题General questions about Azure Site Recovery

本文总结有关 Azure Site Recovery 的常见问题。This article summarizes frequently asked questions about Azure Site Recovery. 有关具体方案,请查看以下文章For specific scenarios review these articles

常规General

站点恢复的功能是什么?What does Site Recovery do?

通过协调和自动化 Azure VM 复制(本地区域虚拟机和物理服务器到 Azure;本地计算机到辅助数据中心),Site Recovery 可帮助实现业务连续性与灾难恢复 (BCDR) 策略。Site Recovery contributes to your business continuity and disaster recovery (BCDR) strategy, by orchestrating and automating replication of Azure VMs between regions, on-premises virtual machines and physical servers to Azure, and on-premises machines to a secondary datacenter. 了解详细信息Learn more.

是否可以保护具有 Docker 磁盘的虚拟机?Can I protect a virtual machine that has a Docker disk?

否,此方案不受支持。No, this is an unsupported scenario.

Site Recovery 如何确保数据完整性?What does Site Recovery do to ensure data integrity?

Site Recovery 采取各种措施来确保数据完整性。There are various measures taken by Site Recovery to ensure data integrity. 使用 HTTPS 协议在所有服务之间建立安全连接。A secure connection is established between all services by using the HTTPS protocol. 这可确保任何恶意软件或外部实体都无法篡改数据。This makes sure that any malware or outside entities can't tamper the data. 采用的另一个措施是使用校验和。Another measure taken is using checksums. 源和目标之间的数据传输是通过计算它们之间数据的校验和来执行的。The data transfer between source and target is executed by computing checksums of data between them. 这可确保传输的数据是一致的。This ensures that the transferred data is consistent.

服务提供商Service providers

我是服务提供商。I'm a service provider. 站点恢复适用于专用和共享的基础结构模型吗?Does Site Recovery work for dedicated and shared infrastructure models?

是的,站点恢复同时支持专用与共享的基础结构模型。Yes, Site Recovery supports both dedicated and shared infrastructure models.

对于服务提供商而言,我的租户标识是否与 Site Recovery 服务共享?For a service provider, is the identity of my tenant shared with the Site Recovery service?

不是。No. 租户标识是匿名的。Tenant identity remains anonymous. 租户不需要访问 Site Recovery 门户。Your tenants don't need access to the Site Recovery portal. 只有服务提供商管理员才能与门户交互。Only the service provider administrator interacts with the portal.

租户应用程序数据是否会发往 Azure?Will tenant application data ever go to Azure?

在服务提供商拥有的站点之间进行复制时,永远不会将应用程序数据发送到 Azure。When replicating between service provider-owned sites, application data never goes to Azure. 数据进行传输中加密并直接在服务提供商站点之间复制。Data is encrypted in-transit, and replicated directly between the service provider sites.

如果是复制到 Azure,应用程序数据将发送到 Azure 存储而不是站点恢复服务。If you're replicating to Azure, application data is sent to Azure storage but not to the Site Recovery service. 数据进行传输中加密并在 Azure 中保持加密状态。Data is encrypted in-transit, and remains encrypted in Azure.

我的租户会收到来自 Azure 服务的帐单吗?Will my tenants receive a bill for any Azure services?

不是。No. Azure 直接与服务提供商保持计费关系。Azure's billing relationship is directly with the service provider. 服务提供商责任为其租户生成特定的帐单。Service providers are responsible for generating specific bills for their tenants.

如果我复制到 Azure,需要在 Azure 中随时运行虚拟机吗?If I'm replicating to Azure, do we need to run virtual machines in Azure at all times?

不需要,数据会复制到订阅中的 Azure 存储。No, Data is replicated to Azure storage in your subscription. 执行测试故障转移(灾难恢复演练)或实际的故障转移时,站点恢复会在订阅中自动创建虚拟机。When you perform a test failover (DR drill) or an actual failover, Site Recovery automatically creates virtual machines in your subscription.

当我复制到 Azure 时,们确保提供租户级的隔离吗?Do you ensure tenant-level isolation when I replicate to Azure?

是的。Yes.

目前支持哪些平台?What platforms do you currently support?

我们支持 Azure Pack、云平台系统和基于 System Center 的(2012 和更高版本)的部署。We support Azure Pack, Cloud Platform System, and System Center based (2012 and higher) deployments. 了解更多有关 Azure Pack 和 Site Recovery 集成的信息。Learn more about Azure Pack and Site Recovery integration.

是否支持单一 Azure Pack 和单一 VMM 服务器部署?Do you support single Azure Pack and single VMM server deployments?

是,可以复制 Hyper-V 虚拟机到 Azure,或者在服务提供商站点之间复制。Yes, you can replicate Hyper-V virtual machines to Azure, or between service provider sites. 请注意,如果在服务提供商站点之间复制,将无法使用 Azure Runbook 集成。Note that if you replicate between service provider sites, Azure runbook integration isn't available.

定价Pricing

我可以在哪里找到定价信息?Where can I find pricing information?

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

在使用 Site Recovery 的过程中,如何计算大致的费用?How can I calculate approximate charges during the use of Site Recovery?

可以使用定价计算器来估算使用 Site Recovery 时的费用。You can use the pricing calculator to estimate costs while using Site Recovery.

若要对费用进行详细估算,请运行 VMwareHyper-V 的部署规划器工具并使用成本估算报告For detailed estimate on costs, run the deployment planner tool for VMware or Hyper-V, and use the cost estimation report.

现在,托管磁盘用于复制 VMware VM 和物理服务器。Managed disks are now used to replicate VMware VMs and physical servers. 使用托管磁盘的缓存存储帐户是否会产生其他费用?Do I incur additional charges for the cache storage account with managed disks?

不会,缓存不会产生其他费用。No, there are no additional charges for cache. 复制到标准存储帐户时,此缓存存储是同一目标存储帐户的一部分。When you replicate to standard storage account, this cache storage is part of the same target storage account.

我已成为 Azure Site Recovery 用户一个多月。I have been an Azure Site Recovery user for over a month. 对于每个受保护的实例,是否仍享受前 31 天免费?Do I still get the first 31 days free for every protected instance?

是的。Yes. 在前 31 天内,每个受保护的实例不会产生任何 Azure Site Recovery 费用。Every protected instance incurs no Azure Site Recovery charges for the first 31 days. 例如,你在过去 6 个月内保护了 10 个实例,现在你将第 11 个实例连接到 Azure Site Recovery,在连接后的前 31 天内,第 11 个实例不会产生任何费用。For example, if you have been protecting 10 instances for the last 6 months and you connect an 11th instance to Azure Site Recovery, there are no charges for the 11th instance for the first 31 days. 而前 10 个实例将继续产生 Azure Site Recovery 费用,因为它们受到保护的时间已超过 31 天。The first 10 instances continue to incur Azure Site Recovery charges since they've been protected for more than 31 days.

在前 31 天的期限内,会产生其他 Azure 费用吗?During the first 31 days, will I incur any other Azure charges?

是,尽管受保护实例的 Site Recovery 在前 31 天内为免费,但可能会产生 Azure 存储、存储事务和数据传输的费用。Yes, even though Site Recovery is free during the first 31 days of a protected instance, you might incur charges for Azure Storage, storage transactions, and data transfer. 恢复后的虚拟机也可能会产生 Azure 计算费用。A recovered virtual machine might also incur Azure compute charges.

进行灾难恢复演练/测试故障转移时,是否有与之相关联的费用?Is there a cost associated to perform disaster recovery drills/test failover?

DR 演练没有单独的费用。There is no separate cost for DR drill. 如果在测试故障转移后创建 VM,则会有计算费用。There will be compute charges after the VM is created after the test failover.

安全性Security

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

不会。站点恢复不拦截复制的数据,也不拥有虚拟机或物理服务器上运行哪些项目的任何相关信息。No, Site Recovery doesn't intercept replicated data, and doesn't have any information about what's running on your virtual machines or physical servers. 复制数据在本地 Hyper-V 主机、VMware 虚拟机监控程序或物理服务器和 Azure 存储或辅助站点之间交换。Replication data is exchanged between on-premises Hyper-V hosts, VMware hypervisors, or physical servers and Azure storage or your secondary site. 站点恢复并不具有拦截该数据的能力。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.

为了遵从法规,即使是本地元数据也必须保留在同一个地理区域。For compliance reasons, even our on-premises metadata must remain within the same geographic region. 站点恢复可以帮助我们吗?Can Site Recovery help us?

是的。Yes. 在某个区域中创建站点恢复保管库时,我们确保启用和协调复制与故障转移时所需的一切元数据都保留在该区域的地理边界范围内。When you create a Site Recovery vault in a region, we ensure that all metadata that we need to enable and orchestrate replication and failover remains within that region's geographic boundary.

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

在本地站点之间复制虚拟机和物理服务器时,支持传输中加密。For virtual machines and physical servers, replicating between on-premises sites encryption-in-transit is supported. 将虚拟机和物理服务器复制到 Azure 时,同时支持传输中加密和静态加密(Azure 中)For virtual machines and physical servers replicating to Azure, both encryption-in-transit and encryption-at-rest (in Azure) are supported.

Azure 到 Azure Site Recovery 是否使用 TLS 1.2 进行 Azure 微服务之间的所有通信?Does Azure-to-Azure Site Recovery use TLS 1.2 for all communications across microservices of Azure?

是,对于 Azure 到 Azure Site Recovery 方案,默认强制实施 TLS 1.2 协议。Yes, TLS 1.2 protocol is enforced by default for Azure-to-Azure Site Recovery scenario.

如何在 VMware 到 Azure 和物理服务器到 Azure Site Recovery 方案中强制实施 TLS 1.2?How can I enforce TLS 1.2 on VMware-to-Azure and Physical Server-to-Azure Site Recovery scenarios?

复制项上安装的移动代理仅通过 TLS 1.2 与进程服务器通信。Mobility agents installed on the replicated items communicate to Process Server only on TLS 1.2. 但是,从配置服务器到 Azure 以及从进程服务器到 Azure 的通信可以通过 TLS 1.1 或 1.0 进行。However, communication from Configuration Server to Azure and from Process Server to Azure could be on TLS 1.1 or 1.0. 请按照指南在设置的所有配置服务器和进程服务器上强制实施 TLS 1.2。Please follow the guidance to enforce TLS 1.2 on all Configuration Servers and Process Servers set up by you.

如何在 HyperV 到 Azure Site Recovery 方案中强制实施 TLS 1.2?How can I enforce TLS 1.2 on HyperV-to-Azure Site Recovery scenarios?

Azure Site Recovery 的微服务之间的所有通信均通过 TLS 1.2 协议进行。All communication between the microservices of Azure Site Recovery happens on TLS 1.2 protocol. Site Recovery 使用系统 (OS) 中配置的安全提供程序,并使用可用的最新 TLS 协议。Site Recovery uses security providers configured in the system (OS) and uses the latest available TLS protocol. 用户需要在注册表中显式启用 TLS 1.2,然后 Site Recovery 将开始使用 TLS 1.2 与服务进行通信。One will need to explicitly enable the TLS 1.2 in the Registry and then Site Recovery will start using TLS 1.2 for communication with services.

如何对存储帐户强制实施受限访问权限(Site Recovery 服务访问这些帐户来读取/写入复制数据)?How can I enforce restricted access on my storage accounts, which are accessed by Site Recovery service for reading/writing replication data?

可转到“标识”设置来打开恢复服务保管库的托管标识。You can switch on the managed identity of the recovery services vault by going to the Identity setting. 将保管库注册到 Azure Active Directory 后,便可以转到存储帐户,向保管库分配以下角色:Once the vault gets registered with Azure Active Directory, you can go to your storage accounts and give the following role-assignments to the vault:

灾难恢复Disaster recovery

站点恢复可以保护哪些计算机?What can Site Recovery protect?

  • Azure VM :Site Recovery 可复制受支持 Azure VM 上运行的任何工作负载Azure VMs : Site Recovery can replicate any workload running on a supported Azure VM
  • Hyper-V 虚拟机 :站点恢复可以保护 Hyper-V VM 上运行的任何工作负载。Hyper-V virtual machines : Site Recovery can protect any workload running on a Hyper-V VM.
  • 物理服务器 :站点恢复可以保护运行 Windows 或 Linux 的物理服务器。Physical servers : Site Recovery can protect physical servers running Windows or Linux.
  • VMware 虚拟机 :站点恢复可以保护 VMware VM 上运行的任何工作负载。VMware virtual machines : Site Recovery can protect any workload running in a VMware VM.

我可以使用站点恢复来保护哪些工作负荷?What workloads can I protect with Site Recovery?

可以使用站点恢复来保护在支持的 VM 或物理服务器上运行的大多数工作负荷。You can use Site Recovery to protect most workloads running on a supported VM or physical server. 站点恢复为应用程序感知型复制提供支持,因此,应用可以恢复为智能状态。Site Recovery provides support for application-aware replication, so that apps can be recovered to an intelligent state. 它除了与 Microsoft 应用程序(例如 SharePoint、Exchange、Dynamics、SQL Server 及 Active Directory)集成之外,还能与行业领先的供应商(包括 Oracle、SAP、IBM 及 Red Hat)紧密配合。It 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.

我可以使用站点恢复来管理分支机构的灾难恢复吗?Can I manage disaster recovery for my branch offices with Site Recovery?

是的。Yes. 使用站点恢复来协调分支机构的复制与故障转移时,可以在一个中心位置获得所有分支机构工作负载的统一视图。When you use Site Recovery to orchestrate replication and failover in your branch offices, you'll get a unified orchestration and view of all your branch office workloads in a central location. 不需要前往分支机构,就可以从总部轻松对所有分支机构运行故障转移和管理灾难恢复。You can easily run failovers and administer disaster recovery of all branches from your head office, without visiting the branches.

Azure VM 是否支持灾难恢复?Is disaster recovery supported for Azure VMs?

是,Site Recovery 支持 Azure 区域之间的 Azure VM 灾难恢复。Yes, Site Recovery supports disaster for Azure VMs between Azure regions. 查看有关 Azure VM 灾难恢复的常见问题Review common questions about Azure VM disaster recovery. 如果要在同一大洲的两个 Azure 区域之间进行复制,请使用 Azure 到 Azure DR 产品/服务。If you want to replicate between two Azure regions on the same continent, please use our Azure to Azure DR offering. 无需设置配置服务器/进程服务器和 ExpressRoute 连接。No need to set up configuration server/process server and ExpressRoute connections.

VMware VM 是否支持灾难恢复?Is disaster recovery supported for VMware VMs?

是,Site Recovery 支持本地 VMware VM 的灾难恢复。Yes, Site Recovery supports disaster recovery of on-premises VMware VMs. 查看有关 VMware VM 灾难恢复的常见问题Review common questions for disaster recovery of VMware VMs.

Hyper-V VM 是否支持灾难恢复?Is disaster recovery supported for Hyper-V VMs?

是,Site Recovery 支持本地 Hyper-V VM 的灾难恢复。Yes, Site Recovery supports disaster recovery of on-premises Hyper-V VMs. 查看有关 Hyper-V VM 灾难恢复的常见问题Review common questions for disaster recovery of Hyper-V VMs.

物理服务器是否支持灾难恢复?Is disaster recovery supported for physical servers?

是,Site Recovery 支持将运行 Windows 和 Linux 的本地物理服务器灾难恢复到 Azure 或辅助站点。Yes, Site Recovery supports disaster recovery of on-premises physical servers running Windows and Linux to Azure or to a secondary site. 了解灾难恢复到 Azure辅助站点的要求。Learn about requirements for disaster recovery to Azure, and toa secondary site. 请注意,故障转移后,物理服务器将在 Azure 中作为 VM 运行。Note that physical servers will run as VMs in Azure after failover. 当前不支持从 Azure 故障回复到本地物理服务器。Failback from Azure to an on-premises physical server isn't currently supported. 只能故障回复到 VMware 虚拟机。You can only fail back to a VMware virtual machine.

复制Replication

能否通过站点到站点 VPN 复制到 Azure?Can I replicate over a site-to-site VPN to Azure?

Azure Site Recovery 通过公共终结点将数据复制到 Azure 存储帐户或托管磁盘。Azure Site Recovery replicates data to an Azure storage account or managed disks, over a public endpoint. 复制不是通过站点到站点 VPN 进行。Replication isn't over a site-to-site VPN.

为何不能通过 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. 因此,只能通过公共 Internet 或 ExpressRoute(Azure 对等互连或现有的公共对等互连)进行复制。Thus you can only replicate over the public internet or via ExpressRoute (Azure peering or an existing public peering).

是否可以使用 Riverbed SteelHeads 进行复制?Can I use Riverbed SteelHeads for replication?

我们的合作伙伴 Riverbed 提供有关使用 Azure Site Recovery 的详细指导。Our partner, Riverbed, provides detailed guidance on working with Azure Site Recovery. 查看其解决方案指南Review their solution guide.

能否使用 ExpressRoute 将虚拟机复制到 Azure?Can I use ExpressRoute to replicate virtual machines to Azure?

能,可以使用 ExpressRoute 将本地虚拟机复制到 Azure。Yes, ExpressRoute can be used to replicate on-premises virtual machines to Azure.

  • Azure Site Recovery 通过公共终结点将数据复制到 Azure 存储。Azure Site Recovery replicates data to an Azure Storage over a public endpoint. 需要设置 Azure 对等互连或使用现有公共对等互连(新线路不适用)来使用 ExpressRoute 进行 Site Recovery 复制。You need to set up Azure peering or use an existing public peering (deprecated for new circuits) to use ExpressRoute for Site Recovery replication.
  • 在复制时,建议使用 Azure 对等互连作为路由域。Azure peering is the recommended routing domain for replication.
  • 私有对等互连不支持复制。Replication is not supported over private peering.
  • 如果要保护 VMware 计算机或物理计算机,请确保也满足配置服务器的网络要求If you're protecting VMware machines or physical machines, ensure that the Networking Requirements for Configuration Server are also met. 配置服务器需要与特定 URL 连接才能编排 Site Recovery 复制。Connectivity to specific URLs is required by Configuration Server for orchestration of Site Recovery replication. ExpressRoute 不能用于此连接。ExpressRoute cannot be used for this connectivity.
  • 将虚拟机故障转移到 Azure 虚拟网络以后,即可使用通过 Azure 虚拟网络设置的专用对等互连对其进行访问。After the virtual machines have been failed over to an Azure virtual network you can access them using the private peering setup with the Azure virtual network.

如果要复制到 Azure,我需要哪种存储帐户或托管磁盘?If I replicate to Azure, what kind of storage account or managed disk do I need?

需要 LRS 或 GRS 存储。You need an LRS or GRS storage. 建议使用 GRS,以便在发生区域性故障或无法恢复主要区域时,能够复原数据。We recommend GRS so that data is resilient if a regional outage occurs, or if the primary region can't be recovered. 该帐户必须位于与恢复服务保管库相同的区域中。The account must be in the same region as the Recovery Services vault. 在 Azure 门户中部署 Site Recovery 时,支持将高级存储用于 VMware VM、Hyper-V VM 和物理服务器复制。Premium storage is supported for VMware VM, Hyper-V VM, and physical server replication, when you deploy Site Recovery in the Azure portal. 托管磁盘仅支持 LRS。Managed disks only support LRS.

我可以多久复制数据一次?How often can I replicate data?

  • Hyper-V :可以每隔 30 秒(高级存储除外)、5 分钟或 15 分钟复制一次 Hyper-V VM。Hyper-V: Hyper-V VMs can be replicated every 30 seconds (except for premium storage), five minutes or 15 minutes.
  • Azure VM、VMware VM、物理服务器 :复制频率无关紧要。Azure VMs, VMware VMs, physical servers: A replication frequency isn't relevant here. 复制是连续的。Replication is continuous.

我可以将复制从现有的恢复站点扩展到其他站点吗?Can I extend replication from existing recovery site to another tertiary site?

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

在首次复制到 Azure 时可以进行脱机复制吗?Can I do an offline replication the first time I replicate to Azure?

Azure 中国目前不支持这种情况。This isn't supported on Azure China currently.

可以从复制中排除特定的磁盘吗?Can I exclude specific disks from replication?

使用 Azure 门户将 VMware VM 和 Hyper-V VM 复制到 Azure 时支持此操作。This is supported when you're replicating VMware VMs and Hyper-V VMs to Azure, using the Azure portal.

可以使用动态磁盘来复制虚拟机吗?Can I replicate virtual machines with dynamic disks?

复制 Hyper-V 虚拟机以及将 VMware VM 和物理计算机复制到 Azure 时,支持动态磁盘。Dynamic disks are supported when replicating Hyper-V virtual machines, and when replicating VMware VMs and physical machines to Azure. 操作系统磁盘必须为基本磁盘。The operating system disk must be a basic disk.

是否可以限制为复制流量分配的带宽?Can I throttle bandwidth allotted for replication traffic?

是的。Yes. 可从以下文章详细了解如何限制带宽:You can read more about throttling bandwidth in these articles:

能否在 Linux 服务器中启用应用一致性复制?Can I enable replication with app-consistency in Linux servers?

是的。Yes. 适用于 Linux 操作系统的 Azure Site Recovery 支持通过应用程序自定义脚本实现应用一致性。Azure Site Recovery for Linux Operation System supports application custom scripts for app-consistency. 在保障应用程序一致性时,Azure Site Recovery 移动代理将使用带有 pre 和 post 选项的自定义脚本。The custom script with pre and post-options will be used by the Azure Site Recovery Mobility Agent during app-consistency. 以下是启用此功能的步骤。Below are the steps to enable it.

  1. 以 root 身份登录计算机。Sign in as root into the machine.

  2. 将目录更改为 Azure Site Recovery 移动代理安装位置。Change directory to Azure Site Recovery Mobility Agent install location. 默认位置为“/usr/local/ASR”Default is "/usr/local/ASR"
    # cd /usr/local/ASR

  3. 在安装位置下将目录更改为“VX/scripts”Change directory to "VX/scripts" under install location
    # cd VX/scripts

  4. 使用 root 用户的执行权限创建名为“customscript.sh”的 bash shell 脚本。Create a bash shell script named "customscript.sh" with execute permissions for root user.
    a.a. 脚本应支持“--pre”和“--post”(请注意双短划线)命令行选项The script should support "--pre" and "--post" (Note the double dashes) command-line options
    b.b. 使用 pre 选项调用脚本时,它应冻结应用程序输入/输出;使用 post 选项调用时,它应解冻应用程序输入/输出。When the script is called with pre-option, it should freeze the application input/output and when called with post-option, it should thaw the application input/output.
    c.c. 示例模板 -A sample template -

    # cat customscript.sh

    #!/bin/bash
    
    if [ $# -ne 1 ]; then
        echo "Usage: $0 [--pre | --post]"
        exit 1
    elif [ "$1" == "--pre" ]; then
        echo "Freezing app IO"
        exit 0
    elif [ "$1" == "--post" ]; then
        echo "Thawed app IO"
        exit 0
    fi
    
  5. 对于需要应用一致性的应用程序,请在 pre 和 post 步骤中添加冻结和解冻输入/输出命令。Add the freeze and unfreeze input/output commands in pre and post-steps for the applications requiring app-consistency. 可以选择添加另一个脚本来指定这些命令,并使用 pre 和 post 选项从“customscript.sh”调用该脚本。You can choose to add another script specifying those and invoke it from "customscript.sh" with pre and post-options.

备注

Site Recovery 代理版本应为 9.24 或更高版本才能支持自定义脚本。The Site Recovery agent version should be 9.24 or above to support custom scripts.

复制策略Replication policy

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

复制策略定义了恢复点的保留历史记录设置。A replication policy defines the settings for the retention history of recovery points. 此策略还定义了应用一致性快照的频率。The policy also defines the frequency of app-consistent snapshots. 默认情况下,Azure Site Recovery 使用以下默认设置创建新的复制策略:By default, Azure Site Recovery creates a new replication policy with default settings of:

  • 恢复点历史记录的保留期为 24 小时。24 hours for the retention history of recovery points.
  • 应用一致性快照的频率为 4 小时。4 hours for the frequency of app-consistent snapshots.

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

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

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

崩溃一致性恢复点生成的频率是多少?What is the frequency of crash-consistent recovery point generation?

Site Recovery 每隔 5 分钟创建崩溃一致性恢复点。Site Recovery creates a crash-consistent recovery point every 5 minutes.

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

应用程序一致性恢复点是从应用程序一致性快照创建的。Application-consistent recovery points are created from application-consistent snapshots. 应用一致性恢复点除了捕获与故障一致性快照相同的数据,还捕获内存中数据以及进程中的所有事务。Application-consistent recovery points capture the same data as crash-consistent snapshots while also capturing data in memory and all transactions in process.

由于包含额外内容,因此应用一致性快照涉及最多且耗时最长。Because of their extra content, application-consistent snapshots are the most involved and take the longest. 我们建议对数据库操作系统以及 SQL Server 等应用程序使用应用程序一致性恢复点。We recommend application-consistent recovery points for database operating systems and applications such as SQL Server.

应用程序一致性恢复点对应用程序性能有何影响?What is the impact of application-consistent recovery points on application performance?

应用一致性恢复点捕获内存中和进程中的所有数据。Application-consistent recovery points capture all the data in memory and in process. 因为恢复点捕获此类数据,所以它们需要 Windows 上的卷影复制服务等框架来让应用处于静止状态。Because recovery points capture that data, they require framework like Volume Shadow Copy Service on Windows to quiesce the application. 如果捕获过程频繁发生,当工作负荷已经很忙时,它可能会影响性能。If the capturing process is frequent, it can affect performance when the workload is already busy. 对于非数据库工作负荷,建议不要对应用一致性恢复点使用低频率。We don't recommend that you use low frequency for app-consistent recovery points for non-database workloads. 即使对于数据库工作负荷,1 小时也足够了。Even for database workload, 1 hour is enough.

应用程序一致性恢复点生成的最低频率是多少?What is the minimum frequency of application-consistent recovery point generation?

Site Recovery 可以创建最低频率为 1 小时的应用一致性恢复点。Site Recovery can create an application-consistent recovery point with a minimum frequency of 1 hour.

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

为了理解 Site Recovery 如何生成恢复点,让我们来看一个复制策略示例。To understand how Site Recovery generates recovery points, let's see an example of a replication policy. 此复制策略有一个恢复点,它的保留期为 24 小时,应用一致性快照频率为 1 小时。This replication policy has a recovery point with a 24-hour retention window and an app-consistent frequency snapshot of 1 hour.

Site Recovery 每隔 5 分钟创建崩溃一致性恢复点。Site Recovery creates a crash-consistent recovery point every 5 minutes. 你无法更改此频率。You can't change this frequency. 对于过去一个小时,你可以从 12 个故障一致性恢复点和 1 个应用一致性恢复点中进行选择。For the last hour, you can choose from 12 crash-consistent points and 1 app-consistent point. 随着时间的推移,Site Recovery 会删除过去一个小时之外的所有恢复点,并且每小时只保存 1 个恢复点。As time progresses, Site Recovery prunes all the recovery points beyond the last hour and saves only 1 recovery point per hour.

以下屏幕截图演示了该示例。The following screenshot illustrates the example. 在屏幕截图中:In the screenshot:

  • 在过去一个小时内,有一些频率为 5 分钟的恢复点。Within the past hour, there are recovery points with a frequency of 5 minutes.

  • 在过去一个小时之外,Site Recovery 只保留 1 个恢复点。Beyond the past hour, Site Recovery keeps only 1 recovery point.

    生成的恢复点列表

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

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

我有保留期为 24 小时的复制策略。I have a replication policy of 24 hours. 如果某个问题导致 Site Recovery 超过 24 小时无法生成恢复点,将会怎样?What will happen if a problem prevents Site Recovery from generating recovery points for more than 24 hours? 以前的恢复点是否将丢失?Will my previous recovery points be lost?

不会,Site Recovery 将保留以前的所有恢复点。No, Site Recovery will keep all your previous recovery points. 根据恢复点的保留期,Site Recovery 仅在生成新点时才替换最早的点。Depending on the recovery points' retention window, Site Recovery replaces the oldest point only if it generates new points. 由于此问题,Site Recovery 无法生成任何新的恢复点。Because of the problem, Site Recovery can't generate any new recovery points. 在有新的恢复点之前,所有旧的恢复点都将在到达保留期后保留。Until there are new recovery points, all the old points will remain after you reach the window of retention.

在 VM 上启用复制后,如何更改复制策略?After replication is enabled on a VM, how do I change the replication policy?

转到“Site Recovery 保管库” > “Site Recovery 基础结构” > “复制策略”。 Go to Site Recovery Vault > Site Recovery Infrastructure > Replication policies. 选择要编辑的策略,然后保存所做的更改。Select the policy that you want to edit, and save the changes. 任何更改也会应用到现有的所有复制。Any change will apply to all the existing replications too.

所有恢复点是包含 VM 的完整副本还是差异副本?Are all the recovery points a complete copy of the VM or a differential?

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

增大恢复点保留期是否会增加存储成本?Does increasing the retention period of recovery points increase the storage cost?

是,如果你将保留期从 24 小时延长到 72 小时,Site Recovery 会额外保存恢复点 48 小时。Yes, if you increase the retention period from 24 hours to 72 hours, Site Recovery will save the recovery points for an additional 48 hours. 增加的时间会产生存储费用。The added time will incur storage charges. 例如,一个恢复点可能有 10GB 的增量更改,每月每 GB 的费用为 $0.16。For example, a single recovery point might have delta changes of 10 GB with a per-GB cost of $0.16 per month. 额外费用为每月 $1.60 × 48。Additional charges would be $1.60 × 48 per month.

故障转移Failover

如果故障转移到 Azure,则在故障转移后如何访问 Azure VM?If I'm failing over to Azure, how do I access the Azure VMs after failover?

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

如果我故障转移到 Azure,Azure 如何确保我的数据可恢复?If I fail over to Azure how does Azure make sure my data is resilient?

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

如果我在两个数据中心之间进行复制,当我的主数据中心发生意外的服务中断时,会出现什么情况?If I'm replicating between two datacenters what happens if my primary datacenter experiences an unexpected outage?

可以从辅助站点触发非计划的故障转移。You can trigger an unplanned failover from the secondary site. 站点恢复不需要来自主站点的连接即可执行故障转移。Site Recovery doesn't need connectivity from the primary site to perform the failover.

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

故障转移不是自动的。Failover isn't automatic. 可以在门户中单击一下来启动故障转移,或者使用站点恢复 PowerShell 来触发故障转移。You initiate failovers with single click in the portal, or you can use Site Recovery PowerShell to trigger a failover. 在站点恢复门户中可以轻松进行故障回复。Failing back is a simple action in the Site Recovery portal.

要自动化,可以使用本地 Orchestrator 或 Operations Manager 来检测虚拟机故障,并使用 SDK 来触发故障转移。To automate you could use on-premises Orchestrator or Operations Manager to detect a virtual machine failure, and then trigger the failover using the SDK.

如果我的本地主机未响应或崩溃,我是否可以故障回复到另一个主机?If my on-premises host is not responding or crashed, can I fail back to a different host?

是,可以使用备用位置恢复从 Azure 故障回复到另一个主机。Yes, you can use the alternate location recovery to failback to a different host from Azure.

自动化Automation

是否可以使用 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 部署站点恢复的方案:Currently supported scenarios for deploying Site Recovery using PowerShell:

组件/提供程序升级Component/provider upgrade

在哪里可以找到 Site Recovery 升级的发行说明/更新汇总Where can I find the release notes/update rollups of Site Recovery upgrades

了解有关新更新的信息,并获取汇总信息Learn about new updates, and get rollup information.

后续步骤Next steps