将 VMware VM 和物理服务器灾难恢复到 Azure 时的支持矩阵Support matrix for disaster recovery of VMware VMs and physical servers to Azure

本文汇总了使用 Azure Site Recovery 服务执行从 VMware VM 和物理服务器到 Azure 的灾难恢复时支持的组件和设置。This article summarizes supported components and settings for disaster recovery of VMware VMs and physical servers to Azure using Azure Site Recovery.

  • 详细了解 VMware VM/物理服务器灾难恢复体系结构。Learn more about VMware VM/physical server disaster recovery architecture.
  • 遵循我们的教程尝试进行灾难恢复。Follow our tutorials to try out disaster recovery.

部署方案Deployment scenarios

方案Scenario 详细信息Details
VMware VM 的灾难恢复Disaster recovery of VMware VMs 将本地 VMware VM 复制到 Azure。Replication of on-premises VMware VMs to Azure. 可以在 Azure 门户中部署此方案,也可使用 PowerShell 进行部署。You can deploy this scenario in the Azure portal or by using PowerShell.
物理服务器的灾难恢复Disaster recovery of physical servers 将本地 Windows/Linux 物理服务器复制到 Azure。Replication of on-premises Windows/Linux physical servers to Azure. 可以在 Azure 门户中部署此方案。You can deploy this scenario in the Azure portal.

本地虚拟化服务器On-premises virtualization servers

ServerServer 要求Requirements 详细信息Details
vCenter ServervCenter Server 版本 6.7、6.5、6.0 或 5.5Version 6.7, 6.5, 6.0, or 5.5 建议在灾难恢复部署中使用 vCenter 服务器。We recommend that you use a vCenter server in your disaster recovery deployment.
vSphere 主机vSphere hosts 版本 6.7、6.5、6.0 或 5.5Version 6.7, 6.5, 6.0, or 5.5 建议 vSphere 主机和 vCenter 服务器与进程服务器位于同一网络。We recommend that vSphere hosts and vCenter servers are located in the same network as the process server. 默认情况下,进程服务器在配置服务器上运行。By default the process server runs on the configuration server. 了解详细信息Learn more.

Site Recovery 配置服务器Site Recovery configuration server

配置服务器是运行 Site Recovery 组件的本地计算机,这些组件包括配置服务器、进程服务器和主目标服务器。The configuration server is an on-premises machine that runs Site Recovery components, including the configuration server, process server, and master target server.

  • 对于 VMware VM,请下载用于创建 VMware VM 的 OVF 模板来设置配置服务器。For VMware VMs, you set the configuration server by downloading an OVF template to create a VMware VM.
  • 对于物理服务器,请手动设置配置服务器计算机。For physical servers, you set up the configuration server machine manually.
组件Component 要求Requirements
CPU 核心数CPU cores 88
RAMRAM 16 GB16 GB
磁盘数目Number of disks 3 磁盘3 disks

磁盘包括 OS 磁盘、进程服务器缓存磁盘和用于故障回复的保留驱动器。Disks include the OS disk, process server cache disk, and retention drive for failback.
磁盘可用空间Disk free space 提供 600 GB 空间用作进程服务器缓存。600 GB of space for the process server cache.
磁盘可用空间Disk free space 为保留驱动器提供 600 GB 空间。600 GB of space for the retention drive.
操作系统Operating system Windows Server 2012 R2,或具有桌面体验的 Windows Server 2016Windows Server 2012 R2, or Windows Server 2016 with Desktop experience

如果计划使用此设备的内置主目标进行故障回复,请确保操作系统版本与复制的项相同或为更高版本。If you plan to use the in-built Master Target of this appliance for failback, ensure that the OS version is same or higher than the replicated items.
操作系统区域设置Operating system locale 英语 (en-us)English (en-us)
PowerCLIPowerCLI 在配置服务器版本 9.14 或更高版本中不需要。Not needed for configuration server version 9.14 or later.
Windows Server 角色Windows Server roles 不要启用 Active Directory 域服务、Internet Information Services (IIS) 或 Hyper-V。Don't enable Active Directory Domain Services; Internet Information Services (IIS) or Hyper-V.
组策略Group policies - 阻止访问命令提示符。- Prevent access to the command prompt.
- 阻止访问注册表编辑工具。- Prevent access to registry editing tools.
- 信任文件附件的逻辑。- Trust logic for file attachments.
- 打开脚本执行。- Turn on Script Execution.
- 了解详细信息- Learn more
IISIIS 确保:Make sure you:

- 无预先存在的默认网站- Don't have a pre-existing default website
- 启用匿名身份验证- Enable anonymous authentication
- 启用 FastCGI 设置- Enable FastCGI setting
- 端口 443 上没有预先存在的网站/应用侦听- Don't have preexisting website/app listening on port 443
NIC 类型NIC type VMXNET3(部署为 VMware VM 时)VMXNET3 (when deployed as a VMware VM)
IP 地址类型IP address type 静态Static
端口Ports 443,用于控制通道协调443 used for control channel orchestration
9443,用于数据传输9443 for data transport

复制的计算机Replicated machines

Site Recovery 支持复制在支持的计算机上运行的任何工作负荷。Site Recovery supports replication of any workload running on a supported machine.

Note

下表列出了对包含 BIOS 启动的计算机的支持。The following table lists the support for machines with BIOS boot. 有关对基于 UEFI 的计算机的支持,请参阅存储部分。Please refer to Storage section for support on UEFI based machines.

组件Component 详细信息Details
计算机设置Machine settings 复制到 Azure 的计算机必须满足 Azure 要求Machines that replicate to Azure must meet Azure requirements.
计算机工作负载Machine workload Site Recovery 支持复制在支持的计算机上运行的任何工作负荷。Site Recovery supports replication of any workload running on a supported machine. 了解详细信息Learn more.
计算机名称Machine name 确保计算机的显示名称不属于 Azure 保留的资源名称Ensure that the display name of machine does not fall into Azure reserved resource names

逻辑卷名称不区分大小写。Logical volume names are not case-sensitive. 请确保设备上不存在两个卷具有相同名称的情况。Ensure that no two volumes on a device have same name. 例如:无法通过 Azure Site Recovery 保护名称为“voLUME1”、“volume1”的卷。Ex: Volumes with names "voLUME1", "volume1" cannot be protected through Azure Site Recovery.
Windows Server 2019Windows Server 2019 更新汇总 34 开始受支持(移动服务版本 9.22 和更高版本)。Supported from Update rollup 34 (version 9.22 of the Mobility service) onwards.
Windows Server 2016 64 位Windows Server 2016 64-bit 支持服务器核心、带桌面体验的服务器。Supported for Server Core, Server with Desktop Experience.
Windows Server 2012 R2/Windows Server 2012Windows Server 2012 R2 / Windows Server 2012 Supported.
Windows Server 2008 R2 SP1 及更高版本。Windows Server 2008 R2 with SP1 onwards. Supported.

在移动服务代理的 9.30 版本中,需要在运行 Windows 2008 R2 SP1 或更高版本的计算机上安装服务堆栈更新 (SSU)SHA-2 更新From version 9.30 of the Mobility service agent, you need servicing stack update (SSU) and SHA-2 update installed on machines running Windows 2008 R2 with SP1 or later. 从 2019 年 9 月开始不再支持 SHA-1,如果未启用 SHA-2 代码签名,则无法按预期方式安装/升级代理扩展。SHA-1 isn't supported from September 2019, and if SHA-2 code signing isn't enabled the agent extension won't install/upgrade as expected. 详细了解 SHA-2 升级和要求Learn more about SHA-2 upgrade and requirements.
Windows Server 2008 SP2 或更高版本(64 位/32 位)Windows Server 2008 with SP2 or later (64-bit/32-bit) 仅支持迁移。Supported for migration only. 了解详细信息Learn more.

在移动服务代理的 9.30 版本中,需要在 Windows 2008 SP2 计算机上安装服务堆栈更新 (SSU)SHA-2 更新From version 9.30 of the Mobility service agent, you need servicing stack update (SSU) and SHA-2 update installed on Windows 2008 SP2 machines. 从 2019 年 9 月开始不再支持 SHA-1,如果未启用 SHA-2 代码签名,则无法按预期方式安装/升级代理扩展。ISHA-1 isn't supported from September 2019, and if SHA-2 code signing isn't enabled the agent extension won't install/upgrade as expected. 详细了解 SHA-2 升级和要求Learn more about SHA-2 upgrade and requirements.
Windows 10、Windows 8.1 和 Windows 8Windows 10, Windows 8.1, Windows 8 Supported.
包含 SP1 的 Windows 7 64 位Windows 7 with SP1 64-bit 更新汇总 36 开始受支持(移动服务版本 9.22 和更高版本)。Supported from Update rollup 36 (version 9.22 of the Mobility service) onwards.

在移动服务代理的 9.30 中,需要在 Windows 7 SP1 计算机上安装服务堆栈更新 (SSU)SHA-2 更新From 9.30 of the Mobility service agent, you need servicing stack update (SSU) and SHA-2 update installed on Windows 7 SP1 machines. 从 2019 年 9 月开始不再支持 SHA-1,如果未启用 SHA-2 代码签名,则无法按预期方式安装/升级代理扩展。SHA-1 isn't supported from September 2019, and if SHA-2 code signing isn't enabled the agent extension won't install/upgrade as expected. 详细了解 SHA-2 升级和要求Learn more about SHA-2 upgrade and requirements.
LinuxLinux 仅支持 64 位系统。Only 64-bit system is supported. 不支持 32 位系统。32-bit system isn't supported.

每个 Linux 服务器上应该装有 Linux Integration Services (LIS) 组件Every Linux server should have Linux Integration Services (LIS) components installed. 测试故障转移/故障转移后,需要在 Azure 中启动该服务器。It is required to boot the server in Azure after test failover/failover. 如果缺少内置 LIS 组件,请确保在启用复制之前安装这些组件,使计算机在 Azure 中启动。If in-built LIS components are missing, ensure to install the components before enabling replication for the machines to boot in Azure.

Site Recovery 会协调故障转移,以在 Azure 中运行 Linux 服务器。Site Recovery orchestrates failover to run Linux servers in Azure. 但是,Linux 供应商可能会限制仅支持尚未达到使用寿命的分发版本。However Linux vendors might limit support to only distribution versions that haven't reached end-of-life.

在 Linux 发行版中,仅支持属于分发次要版本/更新的原版内核。On Linux distributions, only the stock kernels that are part of the distribution minor version release/update are supported.

不支持跨主要 Linux 发行版升级受保护的计算机。Upgrading protected machines across major Linux distribution versions isn't supported. 若要升级,请禁用复制,升级操作系统,然后再重新启用复制。To upgrade, disable replication, upgrade the operating system, and then enable replication again.

详细了解 Azure 中的 Linux 和开源技术支持。Learn more about support for Linux and open-source technology in Azure.
Linux:CentOSLinux: CentOS 5.2 到 5.115.2 to 5.11
6.1 到 6.106.1 to 6.10
7.0 到 7.67.0 to 7.6

8.0 到 8.18.0 to 8.1

运行 CentOS 5.2-5.11 和 6.1-6.10 的服务器上较旧的内核基本都预装了 Linux Integration Services (LIS) 组件Few older kernels on servers running CentOS 5.2-5.11 & 6.1-6.10 do not have Linux Integration Services (LIS) components pre-installed. 如果缺少内置 LIS 组件,请确保在启用复制之前安装这些组件,使计算机在 Azure 中启动。If in-built LIS components are missing, ensure to install the components before enabling replication for the machines to boot in Azure.
UbuntuUbuntu Ubuntu 14.04 LTS 服务器(查看支持的内核版本)Ubuntu 14.04 LTS server (review supported kernel versions)

Ubuntu 16.04 LTS 服务器(查看支持的内核版本)Ubuntu 16.04 LTS server (review supported kernel versions)
Ubuntu 18.04 LTS 服务器(查看支持的内核版本)Ubuntu 18.04 LTS server (review supported kernel versions)
DebianDebian Debian 7/Debian 8(查看支持的内核版本)Debian 7/Debian 8 (review supported kernel versions)
SUSE LinuxSUSE Linux SUSE Linux Enterprise Server 12 SP1、SP2、SP3、SP4 (支持的内核版本)SUSE Linux Enterprise Server 12 SP1, SP2, SP3, SP4 (review supported kernel versions)
SUSE Linux Enterprise Server 15、15 SP1 (查看支持的内核版本)SUSE Linux Enterprise Server 15, 15 SP1 (review supported kernel versions)
SUSE Linux Enterprise Server 11 SP3、SUSE Linux Enterprise Server 11 SP4SUSE Linux Enterprise Server 11 SP3, SUSE Linux Enterprise Server 11 SP4
不支持将复制计算机从 SUSE Linux Enterprise Server 11 SP3 升级到 SP4。Upgrading replicated machines from SUSE Linux Enterprise Server 11 SP3 to SP4 isn't supported. 若要升级,请禁用复制并在升级后重新启用它。To upgrade, disable replication and re-enable after the upgrade.

Note

对于每个 Windows 版本,Azure Site Recovery 仅支持长期服务渠道 (LTSC) 生成。For each of the Windows versions, Azure Site Recovery only supports Long-Term Servicing Channel (LTSC) builds. 目前不支持半年渠道版本。Semi-Annual Channel releases are currently unsupported at this time.

Ubuntu 内核版本Ubuntu kernel versions

支持的版本Supported release 移动服务版本Mobility service version 内核版本Kernel version
14.04 LTS14.04 LTS 9.329.32 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.319.31 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.309.30 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.299.29 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
16.04 LTS16.04 LTS 9.329.32 4.4.0-21-generic 到 4.4.0-171-generic、4.4.0-21-generic to 4.4.0-171-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-74-generic4.15.0-13-generic to 4.15.0-74-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-1066-azure4.15.0-1012-azure to 4.15.0-1066-azure
16.04 LTS16.04 LTS 9.319.31 4.4.0-21-generic 到 4.4.0-170-generic、4.4.0-21-generic to 4.4.0-170-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-72-generic4.15.0-13-generic to 4.15.0-72-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-1063-azure4.15.0-1012-azure to 4.15.0-1063-azure
16.04 LTS16.04 LTS 9.309.30 4.4.0-21-generic 到 4.4.0-166-generic、4.4.0-21-generic to 4.4.0-166-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-66-generic4.15.0-13-generic to 4.15.0-66-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-1061-azure4.15.0-1012-azure to 4.15.0-1061-azure
16.04 LTS16.04 LTS 9.299.29 4.4.0-21-generic 到 4.4.0-164-generic、4.4.0-21-generic to 4.4.0-164-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-64-generic4.15.0-13-generic to 4.15.0-64-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-1059-azure4.15.0-1012-azure to 4.15.0-1059-azure
18.04 LTS18.04 LTS 9.329.32 4.15.0-20-generic 到 4.15.0-74-generic4.15.0-20-generic to 4.15.0-74-generic
4.18.0-13-generic 到 4.18.0-25-generic4.18.0-13-generic to 4.18.0-25-generic
5.0.0-15-generic 到 5.0.0-37-generic5.0.0-15-generic to 5.0.0-37-generic
5.3.0-19-generic 到 5.3.0-24-generic5.3.0-19-generic to 5.3.0-24-generic
4.15.0-1009-azure 到 4.15.0-1037-azure4.15.0-1009-azure to 4.15.0-1037-azure
4.18.0-1006-azure 到 4.18.0-1025-azure4.18.0-1006-azure to 4.18.0-1025-azure
5.0.0-1012-azure 到 5.0.0-1028-azure5.0.0-1012-azure to 5.0.0-1028-azure
5.3.0-1007-azure 到 5.3.0-1009-azure5.3.0-1007-azure to 5.3.0-1009-azure
18.04 LTS18.04 LTS 9.319.31 4.15.0-20-generic 到 4.15.0-72-generic4.15.0-20-generic to 4.15.0-72-generic
4.18.0-13-generic 到 4.18.0-25-generic4.18.0-13-generic to 4.18.0-25-generic
5.0.0-15-generic 到 5.0.0-37-generic5.0.0-15-generic to 5.0.0-37-generic
5.3.0-19-generic 到 5.3.0-24-generic5.3.0-19-generic to 5.3.0-24-generic
4.15.0-1009-azure 到 4.15.0-1037-azure4.15.0-1009-azure to 4.15.0-1037-azure
4.18.0-1006-azure 到 4.18.0-1025-azure4.18.0-1006-azure to 4.18.0-1025-azure
5.0.0-1012-azure 到 5.0.0-1025-azure5.0.0-1012-azure to 5.0.0-1025-azure
5.3.0-1007-azure5.3.0-1007-azure
18.04 LTS18.04 LTS 9.309.30 4.15.0-20-generic 到 4.15.0-66-generic4.15.0-20-generic to 4.15.0-66-generic
4.18.0-13-generic 到 4.18.0-25-generic4.18.0-13-generic to 4.18.0-25-generic
5.0.0-15-generic 到 5.0.0-32-generic5.0.0-15-generic to 5.0.0-32-generic
4.15.0-1009-azure 到 4.15.0-1037-azure4.15.0-1009-azure to 4.15.0-1037-azure
4.18.0-1006-azure 到 4.18.0-1025-azure4.18.0-1006-azure to 4.18.0-1025-azure
5.0.0-1012-azure 到 5.0.0-1023-azure5.0.0-1012-azure to 5.0.0-1023-azure
18.04 LTS18.04 LTS 9.299.29 4.15.0-20-generic 到 4.15.0-62-generic4.15.0-20-generic to 4.15.0-62-generic
4.18.0-13-generic 到 4.18.0-25-generic4.18.0-13-generic to 4.18.0-25-generic
5.0.0-15-generic 到 5.0.0-27-generic5.0.0-15-generic to 5.0.0-27-generic
4.15.0-1009-azure 到 4.15.0-1037-azure4.15.0-1009-azure to 4.15.0-1037-azure
4.18.0-1006-azure 到 4.18.0-1025-azure4.18.0-1006-azure to 4.18.0-1025-azure
5.0.0-1012-azure 到 5.0.0-1018-azure5.0.0-1012-azure to 5.0.0-1018-azure

Debian 内核版本Debian kernel versions

支持的版本Supported release 移动服务版本Mobility service version 内核版本Kernel version
Debian 7Debian 7 9.29, 9.30, 9.31, 9.329.29, 9.30, 9.31, 9.32 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.30, 9.31, 9.329.30, 9.31, 9.32 3.16.0-4-amd64 到 3.16.0-10-amd64、4.9.0-0.bpo.4-amd64 到 4.9.0-0.bpo.11-amd643.16.0-4-amd64 to 3.16.0-10-amd64, 4.9.0-0.bpo.4-amd64 to 4.9.0-0.bpo.11-amd64
Debian 8Debian 8 9.299.29 3.16.0-4-amd64 到 3.16.0-10-amd64、4.9.0-0.bpo.4-amd64 到 4.9.0-0.bpo.9-amd643.16.0-4-amd64 to 3.16.0-10-amd64, 4.9.0-0.bpo.4-amd64 to 4.9.0-0.bpo.9-amd64

SUSE Linux Enterprise Server 12 支持的内核版本SUSE Linux Enterprise Server 12 supported kernel versions

版本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.289.28 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.118-defaultSP1(LTSS) 3.12.74-60.64.45-default to 3.12.74-60.64.118-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.100-defaultSP3 4.4.73-5-default to 4.4.180-94.100-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.29-defaultSP4 4.12.14-94.41-default to 4.12.14-95.29-default
SP4 4.12.14-6.3-azure 到 4.12.14-6.23-azureSP4 4.12.14-6.3-azure to 4.12.14-6.23-azure
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.114-defaultSP2(LTSS) 4.4.121-92.73-default to 4.4.121-92.114-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.19-defaultSP4 4.12.14-94.41-default to 4.12.14-95.19-default
SP4 4.12.14-6.3-azure 到 4.12.14-6.15-azureSP4 4.12.14-6.3-azure to 4.12.14-6.15-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 15 支持的内核版本SUSE Linux Enterprise Server 15 supported kernel versions

版本Release 移动服务版本Mobility service version 内核版本Kernel version
SUSE Linux Enterprise Server 15 和 15 SP1SUSE Linux Enterprise Server 15 and 15 SP1 9.329.32 默认情况下,支持所有库存 SUSE 15 和 15 SP1 内核By default, all stock SUSE 15 and 15 kernels are supported.

4.12.14-5.5-azure 到 4.12.14-8.22-azure4.12.14-5.5-azure to 4.12.14-8.22-azure

Linux 文件系统/来宾存储Linux file systems/guest storage

组件Component 支持Supported
文件系统File systems ext3、ext4、XFS、BTRFS(适用条件如本表所述)ext3, ext4, XFS, BTRFS (conditions applicable as per this table)
逻辑卷管理 (LVM) 预配Logical volume management (LVM) provisioning 复杂预配 - 是Thick provision - Yes
精简预配 - 否Thin provision - No
卷管理器Volume manager - 支持 LVM。- LVM is supported.
- 从更新汇总 31(移动服务版本 9.20)开始支持 LVM 上的 /boot。- /boot on LVM is supported from Update Rollup 31 (version 9.20 of the Mobility service) onwards. 早期移动的服务版本不支持它。It isn't supported in earlier Mobility service versions.
- 不支持多个 OS 磁盘。- Multiple OS disks aren't supported.
半虚拟化存储设备Paravirtualized storage devices 不支持半虚拟化驱动程序导出的设备。Devices exported by paravirtualized drivers aren't supported.
多队列块 IO 设备Multi-queue block IO devices 不支持。Not supported.
具有 HP CCISS 存储控制器的物理服务器Physical servers with the HP CCISS storage controller 不支持。Not supported.
设备/装入点命名约定Device/Mount point naming convention 设备名称或装入点名称应是唯一的。Device name or mount point name should be unique.
请确保两个设备/装入点的名称不仅仅是只区分大小写。Ensure that no two devices/mount points have case-sensitive names. 例如,不支持将同一 VM 的两个设备命名为 device1Device1For example, naming devices for the same VM as device1 and Device1 isn't supported.
目录Directories 如果运行的移动服务版本低于 9.20(在更新汇总 31 中发布),则存在以下限制:If you're running a version of the Mobility service earlier than version 9.20 (released in Update Rollup 31), then these restrictions apply:

- 这些目录(如果设置为单独的分区/文件系统)必须位于源服务器上的同一 OS 磁盘:/ (root)、/boot、/usr、/usr/local、/var 和 /etc。- These directories (if set up as separate partitions/file-systems) must be on the same OS disk on the source server: /(root), /boot, /usr, /usr/local, /var, /etc.
- /boot 目录应位于磁盘分区上,而不是位于 LVM 卷上。- The /boot directory should be on a disk partition and not be an LVM volume.

从版本 9.20 开始,这些限制不适用。From version 9.20 onwards, these restrictions don't apply.
启动目录Boot directory - 启动磁盘不能采用 GPT 分区格式。- Boot disks mustn't be in GPT partition format. 这是一种 Azure 体系结构限制。This is an Azure architecture limitation. 支持将 GPT 磁盘作为数据磁盘。GPT disks are supported as data disks.

VM 上不支持多个启动磁盘Multiple boot disks on a VM aren't supported

- 不支持跨多个磁盘的 LVM 卷上的 /boot。- /boot on an LVM volume across more than one disk isn't supported.
- 无法复制没有启动磁盘的计算机。- A machine without a boot disk can't be replicated.
可用空间要求Free space requirements /root 分区上的 2 GB2 GB on the /root partition

安装文件夹中的 250 MB250 MB on the installation folder
XFSv5XFSv5 支持 XFS 文件系统上的 XFSv5 功能,例如元数据校验和(从移动服务版本 9.10 开始)。XFSv5 features on XFS file systems, such as metadata checksum, are supported (Mobility service version 9.10 onwards).
可使用 xfs_info 实用工具来检查分区的 XFS 超级块。Use the xfs_info utility to check the XFS superblock for the partition. 如果 ftype 设置为 1,则表示正在使用 XFSv5 功能。If ftype is set to 1, then XFSv5 features are in use.
BTRFSBTRFS 更新汇总 34(移动服务版本 9.22)开始支持 BTRFS。BTRFS is supported from Update Rollup 34 (version 9.22 of the Mobility service) onwards. 如果存在以下情况,则不支持 BTRFS:BTRFS isn't supported if:

- 启用保护后 BTRFS 文件系统子卷发生更改。- The BTRFS file system subvolume is changed after enabling protection.
- BTRFS 文件系统分散在多个磁盘中。- The BTRFS file system is spread over multiple disks.
- BTRFS 文件系统支持 RAID。- The BTRFS file system supports RAID.

VM/磁盘管理VM/Disk management

操作Action 详细信息Details
调整复制的 VM 上的磁盘大小Resize disk on replicated VM 在故障转移之前,可直接在源 VM 上的 VM 属性中进行调整。Supported on the source VM before failover, directly in the VM properties. 无需禁用/重新启用复制。No need to disable/re-enable replication.

如果在故障转移后更改源 VM,则这些更改不会被捕获。If you change the source VM after failover, the changes aren't captures.

如果在故障转移之后更改 Azure VM 上的磁盘大小,则在进行故障回复时,Site Recovery 将创建一个包含更新的新 VM。If you change the disk size on the Azure VM after failover, when you fail back, Site Recovery creates a new VM with the updates.
在复制的 VM 上添加磁盘Add disk on replicated VM 不支持。Not supported.
为 VM 禁用复制,添加磁盘,然后重新启用复制。Disable replication for the VM, add the disk, and then re-enable replication.

网络Network

组件Component 支持Supported
主机网络 NIC 组合Host network NIC Teaming 对于 VMware VM,受支持。Supported for VMware VMs.

对于物理计算机复制,不支持。Not supported for physical machine replication.
主机网络 VLANHost network VLAN 是的。Yes.
主机网络 IPv4Host network IPv4 是的。Yes.
主机网络 IPv6Host network IPv6 否。No.
来宾/服务器网络 NIC 组合Guest/server network NIC Teaming 否。No.
来宾/服务器网络 IPv4Guest/server network IPv4 是的。Yes.
来宾/服务器网络 IPv6Guest/server network IPv6 否。No.
来宾/服务器网络静态 IP (Windows)Guest/server network static IP (Windows) 是的。Yes.
来宾/服务器网络静态 IP (Linux)Guest/server network static IP (Linux) 是的。Yes.

VM 配置为在故障回复时使用 DHCP。VMs are configured to use DHCP on failback.
来宾/服务器网络多个 NICGuest/server network multiple NICs 是的。Yes.

Azure VM 网络(故障转移后)Azure VM network (after failover)

组件Component 支持Supported
Azure ExpressRouteAzure ExpressRoute Yes
ILBILB Yes
ELBELB Yes
Azure 流量管理器Azure Traffic Manager Yes
多 NICMulti-NIC Yes
保留 IP 地址Reserved IP address Yes
IPv4IPv4 Yes
保留源 IP 地址Retain source IP address Yes
Azure 虚拟网络服务终结点Azure virtual network service endpoints
Yes
加速网络Accelerated networking No

存储Storage

组件Component 支持Supported
动态磁盘Dynamic disk OS 磁盘必须是基本磁盘。OS disk must be a basic disk.

数据磁盘可以是动态磁盘Data disks can be dynamic disks
Docker 磁盘配置Docker disk configuration No
主机 NFSHost NFS 在 VMware 上支持Yes for VMware

在物理服务器上不支持No for physical servers
主机 SAN (iSCSI/FC)Host SAN (iSCSI/FC) Yes
主机 vSANHost vSAN 在 VMware 上支持Yes for VMware

在物理服务器上不适用N/A for physical servers
主机多路径 (MPIO)Host multipath (MPIO) 是,针对以下项进行了测试:Microsoft DSM、EMC PowerPath 5.7 SP4、EMC PowerPath DSM for CLARiiONYes, tested with Microsoft DSM, EMC PowerPath 5.7 SP4, EMC PowerPath DSM for CLARiiON
主机虚拟卷 (VVols)Host Virtual Volumes (VVols) 在 VMware 上支持Yes for VMware

在物理服务器上不适用N/A for physical servers
来宾/服务器 VMDKGuest/server VMDK Yes
来宾/服务器共享群集磁盘Guest/server shared cluster disk No
来宾/服务器加密磁盘Guest/server encrypted disk No
来宾/服务器 NFSGuest/server NFS No
来宾/服务器 iSCSIGuest/server iSCSI 对于迁移 - 是For Migration - Yes
对于灾难恢复 - 否,iSCSI 将作为附加磁盘故障回复到 VMFor Disaster Recovery - No, iSCSI will failback as an attached disk to the VM
来宾/服务器 SMB 3.0Guest/server SMB 3.0 No
来宾/服务器 RDMGuest/server RDM Yes

在物理服务器上不适用N/A for physical servers
> 1 TB 的来宾/服务器磁盘Guest/server disk > 1 TB 是,磁盘必须大于 1024 MBYes, disk must be larger than 1024 MB

复制到托管磁盘时高达 8,192 GB(9.26 版及更高版本)Up to 8,192 GB when replicating to managed disks (9.26 version onwards)
复制到存储帐户时高达 4,095 GBUp to 4,095 GB when replicating to storage accounts
逻辑和物理扇区大小均为 4K 的来宾/服务器磁盘Guest/server disk with 4K logical and 4k physical sector size No
逻辑扇区大小为 4K 且物理扇区大小为 512 字节的来宾/服务器磁盘Guest/server disk with 4K logical and 512-bytes physical sector size No
包含 > 4 TB 的条带化磁盘的来宾/服务器卷Guest/server volume with striped disk >4 TB Yes
逻辑卷管理 (LVM)Logical volume management (LVM) 复杂预配 - 是Thick provisioning - Yes
精简预配 - 否Thin provisioning - No
来宾/服务器 - 存储空间Guest/server - Storage Spaces No
来宾/服务器热添加/删除磁盘Guest/server hot add/remove disk No
来宾/服务器 - 排除磁盘Guest/server - exclude disk Yes
来宾/服务器多路径 (MPIO)Guest/server multipath (MPIO) No
来宾/服务器 GPT 分区Guest/server GPT partitions 更新汇总 37(移动服务版本 9.25)开始支持五个分区。Five partitions are supported from Update Rollup 37 (version 9.25 of the Mobility service) onwards. 以前支持四个。Previously four were supported.
ReFSReFS 出行服务版本 9.23 或更高版本支持可复原文件系统Resilient File System is supported with Mobility service version 9.23 or higher
来宾/服务器 EFI/UEFI 启动Guest/server EFI/UEFI boot - 支持的版本包括 Windows Server 2012 或更高版本、SLES 12 SP4 和 RHEL 8.0(包含移动代理 9.30 及更高版本)- Supported for Windows Server 2012 or later, SLES 12 SP4 and RHEL 8.0 with mobility agent version 9.30 onwards
- 不支持安全 UEFI 启动类型。- Secure UEFI boot type is not supported.

复制通道Replication channels

复制类型Type of replication 支持Supported
卸载的数据传输 (ODX)Offloaded Data Transfers (ODX) No
脱机设定种子Offline Seeding No
Azure Data BoxAzure Data Box No

Azure 存储Azure storage

组件Component 支持Supported
本地冗余存储Locally redundant storage Yes
异地冗余存储Geo-redundant storage Yes
读取访问异地冗余存储Read-access geo-redundant storage Yes
冷存储Cool storage No
热存储Hot storage No
块 BlobBlock blobs No
静态加密 (SSE)Encryption-at-rest (SSE) Yes
静态加密 (CMK)Encryption-at-rest (CMK) 是(通过 PowerShell Az 3.3.0 及更高版本模块)Yes (via PowerShell Az 3.3.0 module onwards)
高级存储Premium storage Yes
导入/导出服务Import/export service No
VNet 的 Azure 存储防火墙Azure Storage firewalls for VNets 是的。Yes.
在目标存储/缓存存储帐户上配置(用于存储复制的数据)。Configured on target storage/cache storage account (used to store replication data).
常规用途 v2 存储帐户(热层和冷层)General-purpose v2 storage accounts (hot and cool tiers) 是(与 V1 相比,V2 的事务成本高得多)Yes (Transaction costs are substantially higher for V2 compared to V1)

Azure 计算Azure compute

功能Feature 支持Supported
可用性集Availability sets Yes
HUBHUB Yes
托管磁盘Managed disks Yes

Azure VM 要求Azure VM requirements

复制到 Azure 的本地 VM 必须满足此表中汇总的 Azure VM 要求。On-premises VMs replicated to Azure must meet the Azure VM requirements summarized in this table. Site Recovery 运行复制先决条件检查时,如果不符合某些要求,检查将会失败。When Site Recovery runs a prerequisites check for replication, the check will fail if some of the requirements aren't met.

组件Component 要求Requirements 详细信息Details
来宾操作系统Guest operating system 验证复制的计算机支持的操作系统Verify supported operating systems for replicated machines. 如果不支持,检查会失败。Check fails if unsupported.
来宾操作系统体系结构Guest operating system architecture 64 位。64-bit. 如果不支持,检查会失败。Check fails if unsupported.
操作系统磁盘大小Operating system disk size 最大 2,048 GB。Up to 2,048 GB. 如果不支持,检查会失败。Check fails if unsupported.
操作系统磁盘计数Operating system disk count 11 如果不支持,检查会失败。Check fails if unsupported.
数据磁盘计数Data disk count 64 或更少。64 or less. 如果不支持,检查会失败。Check fails if unsupported.
数据磁盘大小Data disk size 复制到托管磁盘时高达 8,192 GB(9.26 版及更高版本)Up to 8,192 GB when replicating to managed disk (9.26 version onwards)
复制到存储帐户时高达 4,095 GBUp to 4,095 GB when replicating to storage account
如果不支持,检查会失败。Check fails if unsupported.
网络适配器Network adapters 支持多个适配器。Multiple adapters are supported.
共享 VHDShared VHD 不支持。Not supported. 如果不支持,检查会失败。Check fails if unsupported.
FC 磁盘FC disk 不支持。Not supported. 如果不支持,检查会失败。Check fails if unsupported.
BitLockerBitLocker 不支持。Not supported. 为计算机启用复制之前,必须先禁用 BitLocker。BitLocker must be disabled before you enable replication for a machine.
VM 名称VM name 1 到 63 个字符。From 1 to 63 characters.

限制为字母、数字和连字符。Restricted to letters, numbers, and hyphens.

计算机名称必须以字母或数字开头和结尾。The machine name must start and end with a letter or number.
请在 Site Recovery 中的计算机属性中更新该值。Update the value in the machine properties in Site Recovery.

资源组限制Resource group limits

若要了解可以在单个资源组下保护的虚拟机数量,请参阅有关订阅限制和配额的文章。To understand the number of virtual machines that can be protected under a single resource group, refer to the article on subscription limits and quotas.

变动率限制Churn limits

下表提供了 Azure Site Recovery 限制。The following table provides the Azure Site Recovery limits.

  • 这些限制基于我们的测试,但不涵盖所有可能的应用 I/O 组合。These limits are based on our tests, but don't cover all possible app I/O combinations.
  • 实际结果可能因应用程序 I/O 组合而异。Actual results can vary based on your application I/O mix.
  • 为了获得最佳结果,我们强烈建议运行部署规划器工具并通过使用测试性故障转移命令来执行广泛的应用程序测试,以获得应用的真实性能图。For best results, we strongly recommend that you run the Deployment Planner tool, and perform extensive application testing using test failovers to get the true performance picture for your app.
复制目标Replication target 平均源磁盘 I/O 大小Average source disk I/O size 平均源磁盘数据变动量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
源数据变动量Source data churn 最大限制Maximum Limit
VM 上所有磁盘的峰值数据变动量Peak data churn across all disks on a VM 54 MB/秒54 MB/s
进程服务器支持的每日最大数据变动量Maximum data churn per day supported by a Process Server 2 TB2 TB
  • 这是在假设存在 30% 的 I/O 重叠的情况下给出的平均数。These are average numbers assuming a 30 percent I/O overlap.
  • Site Recovery 能够根据重叠率、较大的写入大小和实际工作负荷 I/O 行为处理更高的吞吐量。Site Recovery is capable of handling higher throughput based on overlap ratio, larger write sizes, and actual workload I/O behavior.
  • 这些数字假设通常情况下存在大约 5 分钟的积压工作。These numbers assume a typical backlog of approximately five minutes. 也就是说,数据在上传后会在 5 分钟内进行处理并创建恢复点。That is, after data is uploaded, it is processed and a recovery point is created within five minutes.

保管库任务Vault tasks

操作Action 支持Supported
跨资源组移动保管库Move vault across resource groups No
在订阅内部和订阅之间移动保管库Move vault within and across subscriptions No
跨资源组移动存储、网络和 Azure VMMove storage, network, Azure VMs across resource groups No
在订阅内部和订阅之间移动存储、网络、Azure VM。Move storage, network, Azure VMs within and across subscriptions. No

获取最新组件Obtain latest components

名称Name 说明Description 详细信息Details
配置服务器Configuration server 在本地安装。Installed on-premises.
协调本地 VMware 服务器或物理机与 Azure 之间的通信。Coordinates communications between on-premises VMware servers or physical machines, and Azure.
- 了解配置服务器。- Learn about the configuration server.
- 了解如何升级到最新版本。- Learn about upgrading to the latest version.
- 了解如何设置配置服务器。- Learn about setting up the configuration server.
进程服务器Process server 默认安装在配置服务器上。Installed by default on the configuration server.
接收复制数据,通过缓存、压缩和加密对其进行优化,然后将数据发送到 Azure。Receives replication data, optimizes it with caching, compression, and encryption, and sends it to Azure.
随着部署扩大,可以另外添加进程服务器来处理更大的复制流量。As your deployment grows, you can add additional process servers to handle larger volumes of replication traffic.
- 了解进程服务器。- Learn about the process server.
- 了解如何升级到最新版本。- Learn about upgrading to the latest version.
- 了解如何设置横向扩展进程服务器。- Learn about setting up scale-out process servers.
移动服务Mobility Service 在想要复制的 VMware VM 或物理服务器上安装。Installed on VMware VM or physical servers you want to replicate.
协调本地 VMware 服务器/物理服务器与 Azure 之间的复制。Coordinates replication between on-premises VMware servers/physical servers and Azure.
- 了解移动服务。- Learn about the Mobility service.
- 了解如何升级到最新版本。- Learn about upgrading to the latest version.

后续步骤Next steps

了解如何为 VMware VM 的灾难恢复准备 Azure。Learn how to prepare Azure for disaster recovery of VMware VMs.