关于用于 VMware 到 Azure 部署的 Azure Site Recovery 部署规划器About the Azure Site Recovery Deployment Planner for VMware to Azure

本文为适用于 VMware 到 Azure 生产部署的 Azure Site Recovery 部署规划器用户指南。This article is the Azure Site Recovery Deployment Planner user guide for VMware to Azure production deployments.


在开始使用 Azure Site Recovery 保护任何 VMware 虚拟机 (VM) 之前,请根据每日数据变动率分配足够的带宽以满足所需的恢复点目标 (RPO)。Before you begin to protect any VMware virtual machines (VMs) by using Azure Site Recovery, allocate sufficient bandwidth, based on your daily data-change rate, to meet your desired recovery point objective (RPO). 请确保在本地部署适当数量的配置服务器和进程服务器。Be sure to deploy the right number of configuration servers and process servers on-premises.

此外还需创建适当类型和数量的目标 Azure 存储帐户。You also need to create the right type and number of target Azure Storage accounts. 考虑到使用量会随着时间的推移而增加,从而导致源生产服务器数目的增加,请创建标准或高级存储帐户。You create either standard or premium storage accounts, factoring in growth on your source production servers because of increased usage over time. 选择每个 VM 的存储类型时,需要考虑到工作负荷特征(例如每秒读/写 I/O 操作数 [IOPS] 或数据变动量)和 Site Recovery 限制。You choose the storage type per VM, based on workload characteristics (for example, read/write I/O operations per second [IOPS] or data churn) and Site Recovery limits.

Site Recovery 部署规划器是一个命令行工具,适用于 Hyper-V 到 Azure 和 VMware 到 Azure 灾难恢复方案。Site Recovery Deployment Planner is a command-line tool for both Hyper-V to Azure and VMware to Azure disaster recovery scenarios. 可以使用此工具远程分析 VMware VM(不会给生产造成任何影响),了解成功进行复制和测试性故障转移所需满足的带宽和存储要求。You can remotely profile your VMware VMs by using this tool (with no production impact whatsoever) to understand the bandwidth and storage requirements for successful replication and test failover. 不需要在本地安装任何 Site Recovery 组件即可运行此工具。You can run the tool without installing any Site Recovery components on-premises. 为了获得准确的吞吐量结果,请在满足最终需要部署的 Site Recovery 配置服务器(生产部署的前几个步骤之一)的最低要求的 Windows Server 上运行规划器。To get accurate achieved throughput results, run the planner on a Windows Server that meets the minimum requirements of the Site Recovery configuration server that you eventually need to deploy as one of the first steps in production deployment.

该工具提供以下详细信息:The tool provides the following details:

兼容性评估Compatibility assessment

  • 根据磁盘数量、磁盘大小、IOPS、变动量、启动类型 (EFI/BIOS) 和 OS 版本评估 VM 的合格性VM eligibility assessment, based on number of disks, disk size, IOPS, churn, boot type (EFI/BIOS), and OS version

网络带宽需求与 RPO 评估Network bandwidth need versus RPO assessment

  • 增量复制所需的估计网络带宽Estimated network bandwidth that's required for delta replication
  • Site Recovery 可以获得的从本地到 Azure 的吞吐量Throughput that Site Recovery can get from on-premises to Azure
  • 要批处理的 VM 数,具体取决于在给定时间内完成初始复制所需的估计带宽Number of VMs to batch, based on the estimated bandwidth to complete initial replication in a given amount of time
  • 给定带宽可以实现的 RPORPO that can be achieved for a given bandwidth
  • 在预配较低带宽的情况下,对所需 RPO 的影响Impact on the desired RPO if lower bandwidth is provisioned

Azure 基础结构要求Azure infrastructure requirements

  • 每个 VM 的存储类型(标准或高级存储)要求Storage type (standard or premium storage) requirement for each VM
  • 要为复制设置的标准和高级存储帐户总数(包括缓存存储帐户)Total number of standard and premium storage accounts to be set up for replication (Includes cache storage accounts)
  • 基于存储指南的存储帐户命名建议Storage-account naming suggestions, based on Storage guidance
  • 针对订阅执行测试性故障转移或故障转移之前要设置的 Azure 核心数Number of Azure cores to be set up before test failover or failover on the subscription
  • 适用于每个本地 VM 的 Azure VM 建议大小Azure VM-recommended size for each on-premises VM

本地基础结构要求On-premises infrastructure requirements

  • 需在本地部署的配置服务器和进程服务器数量Required number of configuration servers and process servers to be deployed on-premises

灾难恢复到 Azure 的估计成本Estimated disaster recovery cost to Azure

  • 灾难恢复到 Azure 的总估计成本:计算、存储、网络和 Site Recovery 许可证成本Estimated total disaster recovery cost to Azure: compute, storage, network, and Site Recovery license cost
  • 每个 VM 的详细成本分析Detail cost analysis per VM


由于使用量可能会随着时间的推移而增加,所有上述工具计算在执行时都会假定在工作负荷特征中存在一个 30% 的增长系数,Because usage is likely to increase over time, all the preceding tool calculations are performed assuming a 30 percent growth factor in workload characteristics. 而且所有分析指标(读/写 IOPS、变动量等)的值都会使用 95%。The calculations also use a 95th percentile value of all the profiling metrics, such as read/write IOPS and churn. 增长系数和百分位数计算均可配置。Both growth factor and percentile calculation are configurable. 若要详细了解增长系数,请参阅“增长系数考虑因素”部分。To learn more about growth factor, see the "Growth-factor considerations" section. 若要详细了解百分位值,请参阅“用于计算的百分位值”部分。To learn more about percentile value, see the "Percentile value used for the calculation" section.

支持矩阵Support matrix

类别Category VMware 到 AzureVMware to Azure Hyper-V 到 AzureHyper-V to Azure Azure 到 AzureAzure to Azure Hyper-V 到辅助站点Hyper-V to secondary site VMware 到辅助站点VMware to secondary site
支持的方案Supported scenarios Yes Yes No 是*Yes* No
支持的版本Supported version vCenter 6.7、6.5、6.0 或 5.5vCenter 6.7, 6.5, 6.0 or 5.5 Windows Server 2016、Windows Server 2012 R2Windows Server 2016, Windows Server 2012 R2 不可用NA Windows Server 2016、Windows Server 2012 R2Windows Server 2016, Windows Server 2012 R2 不可用NA
支持的配置Supported configuration vCenter、ESXivCenter, ESXi Hyper-V 群集、Hyper-V 主机Hyper-V cluster, Hyper-V host 不可用NA Hyper-V 群集、Hyper-V 主机Hyper-V cluster, Hyper-V host 不可用NA
可以按 Site Recovery 部署规划器的运行实例进行分析的服务器数Number of servers that can be profiled per running instance of Site Recovery Deployment Planner 单个(一次只能分析属于一个 vCenter Server 或一个 ESXi 服务器的 VM)Single (VMs belonging to one vCenter Server or one ESXi server can be profiled at a time) 多个(一次可以分析多个主机或主机群集的 VM)Multiple (VMs across multiple hosts or host clusters can be profiled at a time) 不可用NA 多个(一次可以分析多个主机或主机群集的 VM)Multiple (VMs across multiple hosts or host clusters can be profiled at a time) 不可用NA

*此工具主要用于 Hyper-V 到 Azure 灾难恢复方案。*The tool is primarily for the Hyper-V to Azure disaster recovery scenario. 对于 Hyper-V 到辅助站点灾难恢复,只能将其用于了解源端建议,例如所需网络带宽、每个源 Hyper-V 服务器上需要的可用存储空间,以及初始复制批处理数和批次定义。For Hyper-V to secondary site disaster recovery, it can be used only to understand source-side recommendations like required network bandwidth, required free storage space on each of the source Hyper-V servers, and initial replication batching numbers and batch definitions. 忽略报表中的 Azure 建议和成本。Ignore the Azure recommendations and costs from the report. 另外,“获取吞吐量”操作不适用于 Hyper-V 到辅助站点灾难恢复方案。Also, the Get Throughput operation is not applicable for the Hyper-V-to-secondary-site disaster recovery scenario.


该工具的操作分两个主要阶段:分析和报告生成。The tool has two main phases: profiling and report generation. 此外还有第三个选项,即仅计算吞吐量。There is also a third option to calculate throughput only. 下表提供了可以进行分析和吞吐量测量的服务器的要求。The requirements for the server from which the profiling and throughput measurement is initiated are presented in the following table.

服务器要求Server requirement 说明Description
分析和吞吐量测量Profiling and throughput measurement
  • 操作系统:Windows Server 2016 或 Windows Server 2012 R2Operating system: Windows Server 2016 or Windows Server 2012 R2
    (理想情况下,至少符合配置服务器的建议大小(ideally matching at least the size recommendations for the configuration server)
  • 计算机配置:8 个 vCPU、16 GB RAM、300 GB HDDMachine configuration: 8 vCPUs, 16 GB RAM, 300 GB HDD
  • .NET Framework 4.5.NET Framework 4.5
  • VMware vSphere PowerCLI 6.0 R3VMware vSphere PowerCLI 6.0 R3
  • Visual C++ Redistributable for Visual Studio 2012Visual C++ Redistributable for Visual Studio 2012
  • 从此服务器的 443 端口通过 Internet 访问 Azure (*.blob.core.chinacloudapi.cn)Internet access to Azure (*.blob.core.chinacloudapi.cn) from this server, port 443
    [这是可选的。[This is optional. 你可以选择在手动生成报告期间提供可用带宽。]You can choose to provide the available bandwidth during Report Generation manually.]
  • Azure 存储帐户Azure storage account
  • 服务器上的管理员访问权限Administrator access on the server
  • 至少 100 GB 的可用磁盘空间(假定有 1,000 个 VM,每个平均包含 3 个磁盘,分析时间为 30 天)Minimum 100 GB of free disk space (assuming 1,000 VMs with an average of three disks each, profiled for 30 days)
  • VMware vCenter 统计信息级别设置可以是 1 或更高级别VMware vCenter statistics level settings can be 1 or higher level
  • 允许 vCenter 端口(默认 443):Site Recovery 部署规划器使用此端口连接到 vCenter 服务器/ESXi 主机Allow vCenter port (default 443): Site Recovery Deployment Planner uses this port to connect to the vCenter server/ESXi host
报告生成Report generation 装有 Excel 2013 或更高版本的 Windows 电脑或 Windows Server。A Windows PC or Windows Server with Excel 2013 or later.
  • .NET Framework 4.5.NET Framework 4.5
  • Visual C++ Redistributable for Visual Studio 2012Visual C++ Redistributable for Visual Studio 2012
  • 仅当你在报表生成命令中传递了 -User 选项来获取 VM 的最新 VM 配置信息时才需要 VMware vSphere PowerCLI 6.0 R3VMware vSphere PowerCLI 6.0 R3 is required only when you pass -User option in the report generation command to fetch the latest VM configuration information of the VMs. 部署规划器连接到 vCenter 服务器。The Deployment Planner connects to vCenter server. 允许 vCenter 端口(默认为 443)连接到 vCenter 服务器。Allow vCenter port (default 443) port to connect to vCenter server.
  • 用户权限User permissions 用于在分析期间访问 VMware vCenter 服务器/VMware vSphere ESXi 主机的用户帐户的只读权限Read-only permission for the user account that's used to access the VMware vCenter server/VMware vSphere ESXi host during profiling


    该工具只能分析使用 VMDK 和 RDM 磁盘的 VM,The tool can profile only VMs with VMDK and RDM disks. 无法分析使用 iSCSI 或 NFS 磁盘的 VM。It can't profile VMs with iSCSI or NFS disks. Site Recovery 支持适用于 VMware 服务器的 iSCSI 和 NFS 磁盘。Site Recovery does support iSCSI and NFS disks for VMware servers. 由于部署规划器不在来宾计算机中并且只使用 vCenter 性能计数器进行分析,该工具无法洞察这些磁盘类型。Because the deployment planner isn't inside the guest and it profiles only by using vCenter performance counters, the tool doesn't have visibility into these disk types.

    下载和提取部署规划器工具Download and extract the deployment planner tool

    1. 下载最新版本的 Site Recovery 部署规划器Download the latest version of Site Recovery Deployment Planner. 该工具已打包到 .zip 文件夹中。The tool is packaged in a .zip folder. 该工具的当前版本仅支持 VMware 到 Azure 的方案。The current version of the tool supports only the VMware to Azure scenario.

    2. 将 .zip 文件夹复制到要从中运行该工具的 Windows Server。Copy the .zip folder to the Windows server from which you want to run the tool. 可以从 Windows Server 2012 R2 运行该工具,前提是该服务器具有网络访问权限,可以连接到 vCenter 服务器/vSphere ESXi 主机,其中包含要分析的 VM。You can run the tool from Windows Server 2012 R2 if the server has network access to connect to the vCenter server/vSphere ESXi host that holds the VMs to be profiled. 但是,我们建议在其硬件配置符合配置服务器大小调整指南的服务器上运行该工具。However, we recommend that you run the tool on a server whose hardware configuration meets the configuration server sizing guidelines. 如果已在本地部署 Site Recovery 组件,请从配置服务器运行该工具。If you already deployed Site Recovery components on-premises, run the tool from the configuration server.

      我们建议在运行该工具的服务器上实施与配置服务器(包含内置的进程服务器)一样的硬件配置。We recommend that you have the same hardware configuration as the configuration server (which has an in-built process server) on the server where you run the tool. 此类配置可确保该工具所报告的已实现吞吐量与 Site Recovery 在复制过程中能够达到的实际吞吐量相符。Such a configuration ensures that the achieved throughput that the tool reports matches the actual throughput that Site Recovery can achieve during replication. 吞吐量计算取决于服务器上的可用网络带宽和服务器的硬件配置(例如 CPU 和存储)。The throughput calculation depends on available network bandwidth on the server and hardware configuration (such as CPU and storage) of the server. 如果从任何其他服务器运行该工具,则会计算从该服务器到 Azure 的吞吐量。If you run the tool from any other server, the throughput is calculated from that server to Azure. 另外,由于该服务器的硬件配置可能不同于配置服务器的硬件配置,该工具所报告的已实现吞吐量可能不准确。Also, because the hardware configuration of the server might differ from that of the configuration server, the achieved throughput that the tool reports might be inaccurate.

    3. 解压缩 .zip 文件夹。Extract the .zip folder. 该文件夹包含多个文件和子文件夹。The folder contains multiple files and subfolders. 可执行文件是父文件夹中的 ASRDeploymentPlanner.exe。The executable file is ASRDeploymentPlanner.exe in the parent folder.

      示例:将 .zip 文件复制到 E:\ 驱动器并将它解压缩。Example: Copy the .zip file to E:\ drive and extract it. E:\ASR Deployment Planner_v2.3.zipE:\ASR Deployment Planner_v2.3.zip

      E:\ASR Deployment Planner_v2.3\ASRDeploymentPlanner.exeE:\ASR Deployment Planner_v2.3\ASRDeploymentPlanner.exe

    更新至最新版本的部署规划器Update to the latest version of Deployment Planner

    最新更新汇总在部署规划器版本历史记录中。The latest updates are summarized in the Deployment Planner version history.

    如果部署规划器为旧版,请执行以下操作之一:If you have a previous version of Deployment Planner, do either of the following:

    • 如果最新版不包含分析修补程序且分析已在当前版本的 Planner 上进行,请继续该分析。If the latest version doesn't contain a profiling fix and profiling is already in progress on your current version of the planner, continue the profiling.

    • 如果最新版本不包含分析修补程序,则建议停止在当前版本上进行分析,使用新版本重新开始分析。If the latest version does contain a profiling fix, we recommend that you stop profiling on your current version and restart the profiling with the new version.


      注意开始使用新版本进行分析以后,请传递相同的输出目录路径,以便工具将配置文件数据追加到现有文件。When you start profiling with the new version, pass the same output directory path so that the tool appends profile data on the existing files. 使用完整的分析数据集来生成报告。A complete set of profiled data is used to generate the report. 如果传递不同的输出目录,则会创建新文件,生成报告时不能使用旧的分析数据。If you pass a different output directory, new files are created and old profiled data isn't used to generate the report.

      每个新的部署规划器版本都是 .zip 文件的累积更新。Each new Deployment Planner version is a cumulative update of the .zip file. 不需要将最新文件复制到旧文件夹。You don't need to copy the newest files to the previous folder. 可以创建和使用新文件夹。You can create and use a new folder.

    版本历史记录Version history

    最新的 Site Recovery 部署规划器工具版本为 2.5。The latest Site Recovery Deployment Planner tool version is 2.5. 请参阅 Site Recovery 部署规划器版本历史记录页,了解每个更新中增加的修补程序。See the Site Recovery Deployment Planner version history page for the fixes that are added in each update.

    后续步骤Next steps

    运行 Site Recovery 部署规划器Run Site Recovery Deployment Planner