用于将 Azure VM 从一个区域复制到另一个区域的支持矩阵Support matrix for replicating Azure VMs from one region to another

本文总结了使用 Azure Site Recovery 服务设置在不同的 Azure 区域之间对 Azure VM 进行灾难恢复时的支持和先决条件。This article summarizes support and prerequisites when you set of disaster recovery of Azure VMs from one Azure region to another, using the Azure Site Recovery service.

部署方法支持Deployment method support

部署Deployment 支持Support
Azure 门户Azure portal 支持。Supported.
PowerShellPowerShell 支持。Supported. 了解详细信息Learn more
REST APIREST API 支持。Supported.
CLICLI 目前不支持Not currently supported

资源支持Resource support

资源操作Resource action 详细信息Details
跨资源组移动保管库Move vaults across resource groups 不支持Not supported
跨资源组移动计算/存储/网络资源Move compute/storage/network resources across resource groups 不支持。Not supported.

如果在 VM 复制后移动 VM 或相关组件(如存储/网络),则需要禁用并重新启用 VM 的复制。If you move a VM or associated components such as storage/network after the VM is replicating, you need to disable and then re-enable replication for the VM.
将 Azure VM 从一个订阅复制到另一个订阅以进行灾难恢复Replicate Azure VMs from one subscription to another for disaster recovery 在同一 Azure Active Directory 租户中受支持。Supported within the same Azure Active Directory tenant.
在受支持的地理群集内跨区域迁移虚拟机(订阅内和跨订阅)Migrate VMs across regions within supported geographical clusters (within and across subscriptions) 在同一 Azure Active Directory 租户中受支持。Supported within the same Azure Active Directory tenant.
在同一区域内迁移 VMMigrate VMs within the same region 不支持。Not supported.

区域支持Region support

可在同一地理群集中的任意两个区域之间复制和恢复 VM。You can replicate and recover VMs between any two regions within the same geographic cluster. 在定义地理群集时请注意数据延迟和主权。Geographic clusters are defined keeping data latency and sovereignty in mind.

地理群集 Geographic cluster Azure 区域Azure regions
中国China 中国东部、中国北部、中国东部 2、中国北部 2China East, China North, China East 2, China North 2

Note

  • 可以在你对其拥有相应访问权限的区域中操作。You can work within regions for which you have appropriate access.
  • 如果你要在其中创建保管库的区域未显示,请确保你的订阅有权在该区域中创建资源。If the region in which you want to create a vault doesn't show, make sure your subscription has access to create resources in that region.
  • 如果在启用复制时无法在地理群集中看到某个区域,请确保你的订阅有权在该区域中创建 VM。If you can't see a region within a geographic cluster when you enable replication, make sure your subscription has permissions to create VMs in that region.

缓存存储Cache storage

此表汇总了对复制期间 Site Recovery 使用的缓存存储帐户的支持。This table summarizes support for the cache storage account used by Site Recovery during replication.

设置Setting 支持Support 详细信息Details
常规用途 V2 存储帐户(热存储层和冷存储层)General purpose V2 storage accounts (Hot and Cool tier) 支持Supported 建议不要使用 GPv2,因为 V2 的事务成本远高于 V1 存储帐户。Usage of GPv2 is not recommended because transaction costs for V2 are substantially higher than V1 storage accounts.
高级存储Premium storage 不支持Not supported 标准存储帐户用于缓存存储,有助于优化成本。Standard storage accounts are used for cache storage, to help optimize costs.
虚拟网络的 Azure 存储防火墙Azure Storage firewalls for virtual networks 支持Supported 如果你使用的是启用了防火墙的缓存存储帐户或目标存储帐户,请确保“允许受信任的 Azure 服务”If you are using firewall enabled cache storage account or target storage account, ensure you 'Allow trusted Azure services'.

复制的计算机操作系统Replicated machine operating systems

Site Recovery 支持复制那些运行本节中所列操作系统的 Azure VM。Site Recovery supports replication of Azure VMs running the operating systems listed in this section.

WindowsWindows

操作系统Operating system 详细信息Details
Windows Server 2019Windows Server 2019 服务器核心、带桌面体验的服务器Server Core, Server with Desktop Experience
Windows Server 2016Windows Server 2016 服务器核心、带桌面体验的服务器Server Core, Server with Desktop Experience
Windows Server 2012 R2Windows Server 2012 R2
Windows Server 2012Windows Server 2012
Windows Server 2008 R2Windows Server 2008 R2 运行 SP1 或更高版本Running SP1 or later
Windows 10 (x64)Windows 10 (x64)

LinuxLinux

操作系统Operating system 详细信息Details
CentOSCentOS 6.5, 6.6, 6.7, 6.8, 6.9, 6.10, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.66.5, 6.6, 6.7, 6.8, 6.9, 6.10, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.6
Ubuntu 14.04 LTS ServerUbuntu 14.04 LTS Server 受支持的内核版本Supported kernel versions
Ubuntu 16.04 LTS ServerUbuntu 16.04 LTS Server 受支持的内核版本Supported kernel version

使用基于密码的身份验证和登录的 Ubuntu 服务器以及用于配置云 VM 的 cloud-init 包可能会在故障转移时禁用基于密码的登录(具体取决于 cloudinit 配置)。Ubuntu servers using password-based authentication and sign in, and the cloud-init package to configure cloud VMs, might have password-based sign in disabled on failover (depending on the cloudinit configuration). 通过从“支持”>“故障排除”>“设置”菜单(Azure 门户中的故障转移 VM)重置密码,可以在虚拟机上重新启用基于密码的登录。Password-based sign in can be re-enabled on the virtual machine by resetting the password from the Support > Troubleshooting > Settings menu (of the failed over VM in the Azure portal.
Debian 7Debian 7 受支持的内核版本Supported kernel versions
Debian 8Debian 8 受支持的内核版本Supported kernel versions
SUSE Linux Enterprise Server 12SUSE Linux Enterprise Server 12 SP1、SP2、SP3、SP4。SP1, SP2, SP3, SP4. (受支持的内核版本)(Supported kernel versions)
SUSE Linux Enterprise Server 11SUSE Linux Enterprise Server 11 SP3SP3

不支持将复制计算机从 SP3 升级到 SP4。Upgrade of replicating machines from SP3 to SP4 isn't supported. 如果已升级复制的计算机,则需要禁用复制并在升级后重新启用复制。If a replicated machine has been upgraded, you need to disable replication and re-enable replication after the upgrade.
SUSE Linux Enterprise Server 11SUSE Linux Enterprise Server 11 SP4SP4

Azure 虚拟机支持的 Ubuntu 内核版本Supported Ubuntu kernel versions for Azure virtual machines

版本Release 移动服务版本Mobility service version 内核版本Kernel version
14.04 LTS14.04 LTS 9.279.27 3.13.0-24-generic 到 3.13.0-170-generic、3.13.0-24-generic to 3.13.0-170-generic,
3.16.0-25-generic 到 3.16.0-77-generic、3.16.0-25-generic to 3.16.0-77-generic,
3.19.0-18-generic 到 3.19.0-80-generic、3.19.0-18-generic to 3.19.0-80-generic,
4.2.0-18-generic 到 4.2.0-42-generic、4.2.0-18-generic to 4.2.0-42-generic,
4.4.0-21-generic 到 4.4.0-148-generic、4.4.0-21-generic to 4.4.0-148-generic,
4.15.0-1023-azure 到 4.15.0-1045-azure4.15.0-1023-azure to 4.15.0-1045-azure
14.04 LTS14.04 LTS 9.269.26 3.13.0-24-generic 到 3.13.0-170-generic、3.13.0-24-generic to 3.13.0-170-generic,
3.16.0-25-generic 到 3.16.0-77-generic、3.16.0-25-generic to 3.16.0-77-generic,
3.19.0-18-generic 到 3.19.0-80-generic、3.19.0-18-generic to 3.19.0-80-generic,
4.2.0-18-generic 到 4.2.0-42-generic、4.2.0-18-generic to 4.2.0-42-generic,
4.4.0-21-generic 到 4.4.0-148-generic、4.4.0-21-generic to 4.4.0-148-generic,
4.15.0-1023-azure 到 4.15.0-1045-azure4.15.0-1023-azure to 4.15.0-1045-azure
14.04 LTS14.04 LTS 9.259.25 3.13.0-24-generic 到 3.13.0-169-generic、3.13.0-24-generic to 3.13.0-169-generic,
3.16.0-25-generic 到 3.16.0-77-generic、3.16.0-25-generic to 3.16.0-77-generic,
3.19.0-18-generic 到 3.19.0-80-generic、3.19.0-18-generic to 3.19.0-80-generic,
4.2.0-18-generic 到 4.2.0-42-generic、4.2.0-18-generic to 4.2.0-42-generic,
4.4.0-21-generic 到 4.4.0-146-generic、4.4.0-21-generic to 4.4.0-146-generic,
4.15.0-1023-azure 到 4.15.0-1042-azure4.15.0-1023-azure to 4.15.0-1042-azure
14.04 LTS14.04 LTS 9.249.24 3.13.0-24-generic 到 3.13.0-167-generic、3.13.0-24-generic to 3.13.0-167-generic,
3.16.0-25-generic 到 3.16.0-77-generic、3.16.0-25-generic to 3.16.0-77-generic,
3.19.0-18-generic 到 3.19.0-80-generic、3.19.0-18-generic to 3.19.0-80-generic,
4.2.0-18-generic 到 4.2.0-42-generic、4.2.0-18-generic to 4.2.0-42-generic,
4.4.0-21-generic 到 4.4.0-143-generic、4.4.0-21-generic to 4.4.0-143-generic,
4.15.0-1023-azure 到 4.15.0-1040-azure4.15.0-1023-azure to 4.15.0-1040-azure
16.04 LTS16.04 LTS 9.279.27 4.4.0-21-generic 到 4.4.0-154-generic、4.4.0-21-generic to 4.4.0-154-generic,
4.8.0-34-generic 到 4.8.0-58-generic、4.8.0-34-generic to 4.8.0-58-generic,
4.10.0-14-generic 到 4.10.0-42-generic4.10.0-14-generic to 4.10.0-42-generic
4.11.0-13-generic 到 4.11.0-14-generic、4.11.0-13-generic to 4.11.0-14-generic,
4.13.0-16-generic 到 4.13.0-45-generic、4.13.0-16-generic to 4.13.0-45-generic,
4.15.0-13-generic 到 4.15.0-55-generic4.15.0-13-generic to 4.15.0-55-generic
4.11.0-1009-azure 到 4.11.0-1016-azure、4.11.0-1009-azure to 4.11.0-1016-azure,
4.13.0-1005-azure 到 4.13.0-1018-azure4.13.0-1005-azure to 4.13.0-1018-azure
4.15.0-1012-azure 到 4.15.0-1051-azure4.15.0-1012-azure to 4.15.0-1051-azure
16.04 LTS16.04 LTS 9.269.26 4.4.0-21-generic 到 4.4.0-148-generic、4.4.0-21-generic to 4.4.0-148-generic,
4.8.0-34-generic 到 4.8.0-58-generic、4.8.0-34-generic to 4.8.0-58-generic,
4.10.0-14-generic 到 4.10.0-42-generic4.10.0-14-generic to 4.10.0-42-generic
4.11.0-13-generic 到 4.11.0-14-generic、4.11.0-13-generic to 4.11.0-14-generic,
4.13.0-16-generic 到 4.13.0-45-generic、4.13.0-16-generic to 4.13.0-45-generic,
4.15.0-13-generic 到 4.15.0-50-generic4.15.0-13-generic to 4.15.0-50-generic
4.11.0-1009-azure 到 4.11.0-1016-azure、4.11.0-1009-azure to 4.11.0-1016-azure,
4.13.0-1005-azure 到 4.13.0-1018-azure4.13.0-1005-azure to 4.13.0-1018-azure
4.15.0-1012-azure 到 4.15.0-1045-azure4.15.0-1012-azure to 4.15.0-1045-azure
16.04 LTS16.04 LTS 9.259.25 4.4.0-21-generic 到 4.4.0-146-generic、4.4.0-21-generic to 4.4.0-146-generic,
4.8.0-34-generic 到 4.8.0-58-generic、4.8.0-34-generic to 4.8.0-58-generic,
4.10.0-14-generic 到 4.10.0-42-generic、4.10.0-14-generic to 4.10.0-42-generic,
4.11.0-13-generic 到 4.11.0-14-generic、4.11.0-13-generic to 4.11.0-14-generic,
4.13.0-16-generic 到 4.13.0-45-generic、4.13.0-16-generic to 4.13.0-45-generic,
4.15.0-13-generic 到 4.15.0-48-generic4.15.0-13-generic to 4.15.0-48-generic
4.11.0-1009-azure 到 4.11.0-1016-azure、4.11.0-1009-azure to 4.11.0-1016-azure,
4.13.0-1005-azure 到 4.13.0-1018-azure4.13.0-1005-azure to 4.13.0-1018-azure
4.15.0-1012-azure 到 4.15.0-1042-azure4.15.0-1012-azure to 4.15.0-1042-azure
16.04 LTS16.04 LTS 9.249.24 4.4.0-21-generic 到 4.4.0-143-generic、4.4.0-21-generic to 4.4.0-143-generic,
4.8.0-34-generic 到 4.8.0-58-generic、4.8.0-34-generic to 4.8.0-58-generic,
4.10.0-14-generic 到 4.10.0-42-generic、4.10.0-14-generic to 4.10.0-42-generic,
4.11.0-13-generic 到 4.11.0-14-generic、4.11.0-13-generic to 4.11.0-14-generic,
4.13.0-16-generic 到 4.13.0-45-generic、4.13.0-16-generic to 4.13.0-45-generic,
4.15.0-13-generic 到 4.15.0-46-generic4.15.0-13-generic to 4.15.0-46-generic
4.11.0-1009-azure 到 4.11.0-1016-azure、4.11.0-1009-azure to 4.11.0-1016-azure,
4.13.0-1005-azure 到 4.13.0-1018-azure4.13.0-1005-azure to 4.13.0-1018-azure
4.15.0-1012-azure 到 4.15.0-1040-azure4.15.0-1012-azure to 4.15.0-1040-azure

Azure 虚拟机支持的 Debian 内核版本Supported Debian kernel versions for Azure virtual machines

版本Release 移动服务版本Mobility service version 内核版本Kernel version
Debian 7Debian 7 9.24、9.25、9.26、9.279.24,9.25,9.26,9.27 3.2.0-4-amd64 到 3.2.0-6-amd64、3.16.0-0.bpo.4-amd643.2.0-4-amd64 to 3.2.0-6-amd64, 3.16.0-0.bpo.4-amd64
Debian 8Debian 8 9.279.27 3.16.0-4-amd64 到 3.16.0-9-amd64、4.9.0-0.bpo.4-amd64 到 4.9.0-0.bpo.9-amd643.16.0-4-amd64 to 3.16.0-9-amd64, 4.9.0-0.bpo.4-amd64 to 4.9.0-0.bpo.9-amd64
Debian 8Debian 8 9.25、9.269.25, 9.26 3.16.0-4-amd64 到 3.16.0-8-amd64、4.9.0-0.bpo.4-amd64 到 4.9.0-0.bpo.8-amd643.16.0-4-amd64 to 3.16.0-8-amd64, 4.9.0-0.bpo.4-amd64 to 4.9.0-0.bpo.8-amd64
Debian 8Debian 8 9.249.24 3.16.0-4-amd64 到 3.16.0-7-amd64、4.9.0-0.bpo.4-amd64 到 4.9.0-0.bpo.8-amd643.16.0-4-amd64 to 3.16.0-7-amd64, 4.9.0-0.bpo.4-amd64 to 4.9.0-0.bpo.8-amd64

Azure 虚拟机支持的 SUSE Linux Enterprise Server 12 内核版本Supported SUSE Linux Enterprise Server 12 kernel versions for Azure virtual machines

版本Release 移动服务版本Mobility service version 内核版本Kernel version
SUSE Linux Enterprise Server 12(SP1、SP2、SP3、SP4)SUSE Linux Enterprise Server 12 (SP1,SP2,SP3,SP4) 9.279.27 SP1 3.12.49-11-default 到 3.12.74-60.64.40-defaultSP1 3.12.49-11-default to 3.12.74-60.64.40-default

SP1(LTSS) 3.12.74-60.64.45-default 到 3.12.74-60.64.115-defaultSP1(LTSS) 3.12.74-60.64.45-default to 3.12.74-60.64.115-default

SP2 4.4.21-69-default 到 4.4.120-92.70-defaultSP2 4.4.21-69-default to 4.4.120-92.70-default

SP2(LTSS) 4.4.121-92.73-default 到 4.4.121-92.117-defaultSP2(LTSS) 4.4.121-92.73-default to 4.4.121-92.117-default

SP3 4.4.73-5-default 到 4.4.180-94.97-defaultSP3 4.4.73-5-default to 4.4.180-94.97-default

SP3 4.4.138-4.7-azure 到 4.4.180-4.31-azureSP3 4.4.138-4.7-azure to 4.4.180-4.31-azure

SP4 4.12.14-94.41-default 到 4.12.14-95.24-defaultSP4 4.12.14-94.41-default to 4.12.14-95.24-default
SP4 4.12.14-6.3-azure 到 4.12.14-6.18-azureSP4 4.12.14-6.3-azure to 4.12.14-6.18-azure
SUSE Linux Enterprise Server 12(SP1、SP2、SP3、SP4)SUSE Linux Enterprise Server 12 (SP1,SP2,SP3,SP4) 9.269.26 SP1 3.12.49-11-default 到 3.12.74-60.64.40-defaultSP1 3.12.49-11-default to 3.12.74-60.64.40-default

SP1(LTSS) 3.12.74-60.64.45-default 到 3.12.74-60.64.110-defaultSP1(LTSS) 3.12.74-60.64.45-default to 3.12.74-60.64.110-default

SP2 4.4.21-69-default 到 4.4.120-92.70-defaultSP2 4.4.21-69-default to 4.4.120-92.70-default

SP2(LTSS) 4.4.121-92.73-default 到 4.4.121-92.109-defaultSP2(LTSS) 4.4.121-92.73-default to 4.4.121-92.109-default

SP3 4.4.73-5-default 到 4.4.178-94.91-defaultSP3 4.4.73-5-default to 4.4.178-94.91-default

SP3 4.4.138-4.7-azure 到 4.4.178-4.28-azureSP3 4.4.138-4.7-azure to 4.4.178-4.28-azure

SP4 4.12.14-94.41-default 到 4.12.14-95.16-defaultSP4 4.12.14-94.41-default to 4.12.14-95.16-default
SP4 4.12.14-6.3-azure 到 4.12.14-6.9-azureSP4 4.12.14-6.3-azure to 4.12.14-6.9-azure
SUSE Linux Enterprise Server 12(SP1、SP2、SP3、SP4)SUSE Linux Enterprise Server 12 (SP1,SP2,SP3,SP4) 9.259.25 SP1 3.12.49-11-default 到 3.12.74-60.64.40-defaultSP1 3.12.49-11-default to 3.12.74-60.64.40-default

SP1(LTSS) 3.12.74-60.64.45-default 到 3.12.74-60.64.107-defaultSP1(LTSS) 3.12.74-60.64.45-default to 3.12.74-60.64.107-default

SP2 4.4.21-69-default 到 4.4.120-92.70-defaultSP2 4.4.21-69-default to 4.4.120-92.70-default

SP2(LTSS) 4.4.121-92.73-default 到 4.4.121-92.104-defaultSP2(LTSS) 4.4.121-92.73-default to 4.4.121-92.104-default

SP3 4.4.73-5-default 到 4.4.176-94.88-defaultSP3 4.4.73-5-default to 4.4.176-94.88-default

SP3 4.4.138-4.7-azure 到 4.4.176-4.25-azureSP3 4.4.138-4.7-azure to 4.4.176-4.25-azure

SP4 4.12.14-94.41-default 到 4.12.14-95.13-defaultSP4 4.12.14-94.41-default to 4.12.14-95.13-default
SP4 4.12.14-6.3-azure 到 4.12.14-6.9-azureSP4 4.12.14-6.3-azure to 4.12.14-6.9-azure
SUSE Linux Enterprise Server 12(SP1、SP2、SP3、SP4)SUSE Linux Enterprise Server 12 (SP1,SP2,SP3,SP4) 9.249.24 SP1 3.12.49-11-default 到 3.12.74-60.64.40-defaultSP1 3.12.49-11-default to 3.12.74-60.64.40-default

SP1(LTSS) 3.12.74-60.64.45-default 到 3.12.74-60.64.107-defaultSP1(LTSS) 3.12.74-60.64.45-default to 3.12.74-60.64.107-default

SP2 4.4.21-69-default 到 4.4.120-92.70-defaultSP2 4.4.21-69-default to 4.4.120-92.70-default

SP2(LTSS) 4.4.121-92.73-default 到 4.4.121-92.104-defaultSP2(LTSS) 4.4.121-92.73-default to 4.4.121-92.104-default

SP3 4.4.73-5-default 到 4.4.176-94.88-defaultSP3 4.4.73-5-default to 4.4.176-94.88-default

SP4 4.12.14-94.41-default 到 4.12.14-95.13-defaultSP4 4.12.14-94.41-default to 4.12.14-95.13-default

复制的计算机 - Linux 文件系统/来宾存储Replicated machines - Linux file system/guest storage

  • 文件系统:ext3、ext4、ReiserFS(仅限 Suse Linux Enterprise Server)和 XFS、BTRFSFile systems: ext3, ext4, ReiserFS (Suse Linux Enterprise Server only), XFS, BTRFS
  • 卷管理器:LVM2Volume manager: LVM2
  • 多路径软件:设备映射器Multipath software: Device Mapper

复制的计算机 - 计算设置Replicated machines - compute settings

设置Setting 支持Support 详细信息Details
大小Size 具有至少 2 个 CPU 内核和 1 GB RAM 的任意 Azure VM 大小Any Azure VM size with at least 2 CPU cores and 1-GB RAM 验证 Azure 虚拟机大小Verify Azure virtual machine sizes.
可用性集Availability sets 支持Supported 如果启用使用默认选项复制 Azure VM,则会根据源区域设置自动创建可用性集。If you enable replication for an Azure VM with the default options, an availability set is created automatically, based on the source region settings. 可以修改这些设置。You can modify these settings.
混合使用权益 (HUB)Hybrid Use Benefit (HUB) 支持Supported 如果源 VM 启用了 HUB 许可证,则测试故障转移或故障转移 VM 也使用 HUB 许可证。If the source VM has a HUB license enabled, a test failover or failed over VM also uses the HUB license.
VM 规模集VM scale sets 不支持Not supported
Azure 库映像 - 由 Azure 发布Azure gallery images - Azure published 支持Supported 如果 VM 在受支持的操作系统上运行,则支持该配置。Supported if the VM runs on a supported operating system.
Azure 库映像 - 由第三方发布Azure Gallery images - Third party published 支持Supported 如果 VM 在受支持的操作系统上运行,则支持该配置。Supported if the VM runs on a supported operating system.
自定义映像 - 由第三方发布Custom images - Third party published 支持Supported 如果 VM 在受支持的操作系统上运行,则支持该配置。Supported if the VM runs on a supported operating system.
使用 Site Recovery 迁移 VMVMs migrated using Site Recovery 支持Supported 如果使用 Site Recovery 将 VMware VM 或物理计算机迁移到 Azure,则需要卸载计算机上运行的旧版移动服务,并在重启计算机后将该计算机复制到另一个 Azure 区域。If a VMware VM or physical machine was migrated to Azure using Site Recovery, you need to uninstall the older version of Mobility service running on the machine, and restart the machine before replicating it to another Azure region.
RBAC 策略RBAC policies 不支持Not supported VM 上的基于角色的访问控制 (RBAC) 策略不会复制到目标区域中的故障转移 VM。Role based Access control (RBAC) policies on VMs are not replicated to the failover VM in target region.
扩展Extensions 不支持Not supported 扩展不会复制到目标区域中的故障转移 VM。Extensions are not replicated to the failover VM in target region. 需要在故障转移后手动安装。It needs to be installed manually after failover.

复制的计算机 - 磁盘操作Replicated machines - disk actions

操作Action 详细信息Details
调整复制的 VM 上的磁盘大小Resize disk on replicated VM 支持Supported
将磁盘添加到复制的 VMAdd a disk to a replicated VM 支持Supported

复制的计算机 - 存储Replicated machines - storage

此表汇总了对 Azure VM OS 磁盘、数据磁盘和临时磁盘的支持。This table summarized support for the Azure VM OS disk, data disk, and temporary disk.

  • 请务必遵循适用于 LinuxWindows VM 的 VM 磁盘限制以及目标,以避免任何性能问题。It's important to observe the VM disk limits and targets for Linux and Windows VMs to avoid any performance issues.
  • 如果使用默认设置进行部署,Site Recovery 会根据源设置自动创建磁盘和存储帐户。If you deploy with the default settings, Site Recovery automatically creates disks and storage accounts based on the source settings.
  • 如果自定义,请确保遵循指南。If you customize, ensure you follow the guidelines.
组件Component 支持Support 详细信息Details
OS 磁盘的最大大小OS disk maximum size 2048 GB2048 GB 深入了解 VM 磁盘相关信息。Learn more about VM disks.
临时磁盘Temporary disk 不支持Not supported 始终从复制中排除临时磁盘。The temporary disk is always excluded from replication.

请勿在临时磁盘上存储任何持久性数据。Don't store any persistent data on the temporary disk. 了解详细信息Learn more.
数据磁盘的最大大小Data disk maximum size 托管磁盘为 8192 GB8192 GB for managed disks
非托管磁盘为 4095 GB4095 GB for unmanaged disks
数据磁盘的最小大小Data disk minimum size 对非托管磁盘没有限制。No restriction for unmanaged disks. 托管磁盘为 2 GB2 GB for managed disks
数据磁盘的最大数量Data disk maximum number 最多为 64,根据对特定的 Azure VM 大小的支持而定Up to 64, in accordance with support for a specific Azure VM size 深入了解 VM 大小相关信息。Learn more about VM sizes.
数据磁盘更改率Data disk change rate 每个高级存储的磁盘最大为 10 MBps。Maximum of 10 MBps per disk for premium storage. 每个标准存储的磁盘最大为 2 MBps。Maximum of 2 MBps per disk for Standard storage. 如果磁盘上的平均数据更改率持续高于最大值,复制将跟不上。If the average data change rate on the disk is continuously higher than the maximum, replication won't catch up.

但是,如果偶尔超出最大值,则复制可跟上,但可能会看到稍有延迟的恢复点。However, if the maximum is exceeded sporadically, replication can catch up, but you might see slightly delayed recovery points.
数据磁盘 - 标准存储帐户Data disk - standard storage account 支持Supported
数据磁盘 - 高级存储帐户Data disk - premium storage account 支持Supported 如果 VM 将磁盘分散在高级和标准存储帐户上,则可以为每个磁盘选择不同的目标存储帐户,以确保在目标区域中具有相同的存储配置。If a VM has disks spread across premium and standard storage accounts, you can select a different target storage account for each disk, to ensure you have the same storage configuration in the target region.
托管磁盘 - 标准Managed disk - standard 在支持 Azure Site Recovery 的 Azure 区域中受支持。Supported in Azure regions in which Azure Site Recovery is supported.
托管磁盘 - 高级Managed disk - premium 在支持 Azure Site Recovery 的 Azure 区域中受支持。Supported in Azure regions in which Azure Site Recovery is supported.
标准 SSDStandard SSD 支持Supported
冗余Redundancy LRS 和 GRS 受支持。LRS and GRS are supported.

ZRS 不受支持。ZRS isn't supported.
冷存储和热存储Cool and hot storage 不支持Not supported 冷存储和热存储不支持 VM 磁盘VM disks aren't supported on cool and hot storage
存储空间Storage Spaces 支持Supported
静态加密 (SSE)Encryption at rest (SSE) 支持Supported SSE 是存储帐户的默认设置。SSE is the default setting on storage accounts.
适用于 Linux OS 的 Azure 磁盘加密 (ADE)Azure Disk Encryption (ADE) for Linux OS 不支持Not supported
热添加Hot add 支持Supported 使用托管磁盘的 VM 支持对添加到已复制 Azure VM 的数据磁盘启用复制。Enabling replication for a data disk that you add to a replicated Azure VM is supported for VMs that use managed disks.
热删除磁盘Hot remove disk 不支持Not supported 如果在 VM 上删除数据磁盘,需要先禁用复制然后重新为 VM 启用复制。If you remove data disk on the VM, you need to disable replication and enable replication again for the VM.
排除磁盘Exclude disk 支持。Support. 必须使用 Powershell 进行配置。You must use Powershell to configure. 默认会排除临时磁盘。Temporary disks are excluded by default.
存储空间直通Storage Spaces Direct 崩溃一致恢复点支持。Supported for crash consistent recovery points. 不支持应用程序一致恢复点。Application consistent recovery points are not supported.
横向扩展文件服务器Scale-out File Server 崩溃一致恢复点支持。Supported for crash consistent recovery points. 不支持应用程序一致恢复点。Application consistent recovery points are not supported.
LRSLRS 支持Supported
GRSGRS 支持Supported
RA-GRSRA-GRS 支持Supported
ZRSZRS 不支持Not supported
冷存储和热存储Cool and Hot Storage 不支持Not supported 冷存储和热存储不支持虚拟机磁盘Virtual machine disks are not supported on cool and hot storage
虚拟网络的 Azure 存储防火墙Azure Storage firewalls for virtual networks 支持Supported 如果限制通过虚拟网络访问存储帐户,请启用允许受信任的 Azure 服务If restrict virtual network access to storage accounts, enable Allow trusted Azure services.
常规用途 V2 存储帐户(包括热存储层和冷存储层)General purpose V2 storage accounts (Both Hot and Cool tier) Yes 与常规用途 V1 存储帐户相比,事务成本大幅增加Transaction costs increase substantially compared to General purpose V1 storage accounts

Important

为了避免出现性能问题,请务必遵守 LinuxWindows VM 的 VM 磁盘可伸缩性和性能目标。To avoid performance issues, make sure that you follow VM disk scalability and performance targets for Linux or Windows VMs. 如果使用默认设置,Site Recovery 会基于源配置创建所需的磁盘和存储帐户。If you use default settings, Site Recovery creates the required disks and storage accounts, based on the source configuration. 如果自定义和选择自己的设置,请遵守源 VM 的磁盘可伸缩性和性能目标。If you customize and select your own settings,follow the disk scalability and performance targets for your source VMs.

限制和数据更改率Limits and data change rates

下表汇总了 Site Recovery 的限制。The following table summarizes Site Recovery limits.

  • 这些限制基于我们的测试,但很明显,它们并未涵盖所有可能的应用程序 I/O 组合。These limits are based on our tests, but obviously don't cover all possible application I/O combinations.
  • 实际结果可能因应用 I/O 的混合形式而异。Actual results can vary based on you app I/O mix.
  • 有两个限制需要考虑:每个磁盘的数据变动率,以及每个虚拟机的数据变动率。There are two limits to consider, per disk data churn and per virtual machine data churn.
  • 例如,如果使用下表中所述的高级 P20 磁盘,则 Site Recovery 能够处理每个磁盘 5 MB/秒的变动率,但由于每个 VM 的总变动率限制为 25 MB/秒,因此,它最多可以处理每个 VM 中 5 个这样的磁盘。As an example, if we use a Premium P20 disk as described in the table below, Site Recovery can handle 5 MBs of churn per disk, with at max of five such disks per VM, due to the limit of 25 MB/s total churn per VM.
存储目标Storage target 平均源磁盘 I/OAverage source disk I/O 平均源磁盘数据变动量Average source disk data churn 每天的总源磁盘数据变动量Total source disk data churn per day
标准存储Standard storage 8 KB8 KB 2 MB/秒2 MB/s 每个磁盘 168 GB168 GB per disk
高级 P10 或 P15 磁盘Premium P10 or P15 disk 8 KB8 KB 2 MB/秒2 MB/s 每个磁盘 168 GB168 GB per disk
高级 P10 或 P15 磁盘Premium P10 or P15 disk 16 KB16 KB 4 MB/秒4 MB/s 每个磁盘 336 GB336 GB per disk
高级 P10 或 P15 磁盘Premium P10 or P15 disk 至少 32 KB32 KB or greater 8 MB/秒8 MB/s 每个磁盘 672 GB672 GB per disk
高级 P20、P30、P40 或 P50 磁盘Premium P20 or P30 or P40 or P50 disk 8 KB8 KB 5 MB/秒5 MB/s 每个磁盘 421 GB421 GB per disk
高级 P20、P30、P40 或 P50 磁盘Premium P20 or P30 or P40 or P50 disk 至少 16 KB16 KB or greater 20 MB/秒20 MB/s 每个磁盘 1684 GB1684 GB per disk

复制的计算机 - 网络Replicated machines - networking

设置Setting 支持Support 详细信息Details
NICNIC 特定 Azure VM 大小支持的最大数量Maximum number supported for a specific Azure VM size 在故障转移期间创建 VM 时会创建 NIC。NICs are created when the VM is created during failover.

故障转移 VM 上的 NIC 数目取决于启用复制时源 VM 上的 NIC 数目。The number of NICs on the failover VM depends on the number of NICs on the source VM when replication was enabled. 如果在启用复制后添加或删除 NIC,不会影响故障转移后复制的 VM 上的 NIC 数目。If you add or remove a NIC after enabling replication, it doesn't impact the number of NICs on the replicated VM after failover. 另请注意,不保证故障转移后的 NIC 顺序与原始顺序相同。Also note that the order of NICs after failover is not guaranteed to be the same as the original order.
Internet 负载均衡器Internet Load Balancer 支持Supported 在恢复计划中使用 Azure 自动化脚本关联预配置的负载均衡器。Associate the preconfigured load balancer using an Azure Automation script in a recovery plan.
内部负载均衡器Internal Load balancer 支持Supported 在恢复计划中使用 Azure 自动化脚本关联预配置的负载均衡器。Associate the preconfigured load balancer using an Azure Automation script in a recovery plan.
公共 IP 地址Public IP address 支持Supported 将现有的公共 IP 地址与 NIC 关联。Associate an existing public IP address with the NIC. 或者,在恢复计划中使用 Azure 自动化脚本创建公共 IP 地址并将其与 NIC 关联。Or, create a public IP address and associate it with the NIC using an Azure Automation script in a recovery plan.
NIC 上的 NSGNSG on NIC 支持Supported 在恢复计划中使用 Azure 自动化脚本将 NSG 与 NIC 关联。Associate the NSG with the NIC using an Azure Automation script in a recovery plan.
子网上的 NSGNSG on subnet 支持Supported 在恢复计划中使用 Azure 自动化脚本将 NSG 与子网关联。Associate the NSG with the subnet using an Azure Automation script in a recovery plan.
保留(静态)IP 地址Reserved (static) IP address 支持Supported 如果源 VM 上的 NIC 具有静态 IP 地址,并且目标子网具有相同的可用 IP 地址,则会将它分配给故障转移 VM。If the NIC on the source VM has a static IP address, and the target subnet has the same IP address available, it's assigned to the failed over VM.

如果目标子网没有相同的可用 IP 地址,则为 VM 保留子网中的某个可用 IP 地址。If the target subnet doesn't have the same IP address available, one of the available IP addresses in the subnet is reserved for the VM.

此外可以在“复制的项” > “设置” > “计算和网络” > “网络接口” 中指定固定的 IP 地址和子网。You can also specify a fixed IP address and subnet in Replicated items > Settings > Compute and Network > Network interfaces.
动态 IP 地址Dynamic IP address 支持Supported 如果源上的 NIC 具有动态 IP 地址,故障转移 VM 上的 NIC 也默认为动态。If the NIC on the source has dynamic IP addressing, the NIC on the failed over VM is also dynamic by default.

如果有需要,可以将其修改为固定的 IP 地址。You can modify this to a fixed IP address if required.
多个 IP 地址Multiple IP addresses 不支持Not supported 如果故障转移的 VM 包含采用多个 IP 地址的 NIC,则只会保留源区域中 NIC 的主要 IP 地址。When you fail over a VM that has a NIC with multiple IP addresses, only the primary IP address of the NIC in the source region is kept. 若要分配多个 IP 地址,可将 VM 添加到 恢复计划,并附加一个脚本用于将其他 IP 地址分配到该计划,或者,可以手动进行更改,或故障转移后使用脚本进行更改。To assign multiple IP addresses, you can add VMs to a recovery plan and attach a script to assign additional IP addresses to the plan, or you can make the change manually or with a script after failover.
流量管理器Traffic Manager 支持Supported 可以预配置流量管理器,这样在正常情况下,流量路由到源区域中的终结点;发生故障转移时,流量路由到目标区域中的终结点。You can preconfigure Traffic Manager so that traffic is routed to the endpoint in the source region on a regular basis, and to the endpoint in the target region in case of failover.
Azure DNSAzure DNS 支持Supported
自定义 DNSCustom DNS 支持Supported
未经身份验证的代理Unauthenticated proxy 支持Supported 了解详细信息Learn more
经过身份验证的代理Authenticated Proxy 不支持Not supported 如果 VM 正在使用经过身份验证的代理进行出站连接,则不可使用 Azure Site Recovery 进行复制。If the VM is using an authenticated proxy for outbound connectivity, it cannot be replicated using Azure Site Recovery.
与本地建立 VPN 站点到站点连接VPN site-to-site connection to on-premises

(使用或不使用 ExpressRoute)(with or without ExpressRoute)
支持Supported 确保将 UDR 和 NSG 配置为 Site Recovery 流量不会路由到本地。Ensure that the UDRs and NSGs are configured in such a way that the Site Recovery traffic is not routed to on-premises. 了解详细信息Learn more
VNET 到 VNET 连接VNET to VNET connection 支持Supported 了解详细信息Learn more
虚拟网络服务终结点Virtual Network Service Endpoints 支持Supported 若要限制对存储帐户的虚拟网络访问,请确保允许受信任的 Azure 服务访问存储帐户。If you are restricting the virtual network access to storage accounts, ensure that the trusted Azure services are allowed access to the storage account.
加速网络Accelerated networking 支持Supported 必须在源 VM 上启用加速网络。Accelerated networking must be enabled on source VM. 了解详细信息Learn more.

后续步骤Next steps