关于用于将 Hyper-V 灾难恢复到 Azure 的 Azure Site Recovery 部署规划器About the Azure Site Recovery Deployment Planner for Hyper-V disaster recovery to Azure

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

在开始使用 Site Recovery 保护任何 Hyper-V 虚拟机 (VM) 之前,请根据每日数据更改率分配足够的带宽以满足所需的恢复点目标 (RPO),并在本地 Hyper-V 存储的每个卷上分配足够的可用存储空间。Before you begin protecting any Hyper-V virtual machines (VMs) using Site Recovery, allocate sufficient bandwidth based on your daily data-change rate to meet your desired Recovery Point Objective (RPO), and allocate sufficient free storage space on each volume of Hyper-V storage 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) 或数据变动量,以及 Azure 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 Azure Site Recovery limits.

Azure Site Recovery 部署规划器是一个命令行工具,适用于 Hyper-V 到 Azure 和 VMware 到 Azure 灾难恢复方案。The Azure Site Recovery deployment planner is a command-line tool for both Hyper-V to Azure and VMware to Azure disaster recovery scenarios. 可以使用此工具远程分析多个 Hyper-V 主机上存在的 Hyper-V VM(不会给生产造成任何影响),了解成功进行复制和测试性故障转移/故障转移所需满足的带宽和 Azure 存储要求。You can remotely profile your Hyper-V VMs present on multiple Hyper-V hosts using this tool (with no production impact whatsoever) to understand the bandwidth and Azure storage requirements for successful replication and test failover / failover. 不需在本地安装任何 Azure Site Recovery 组件即可运行此工具。You can run the tool without installing any Azure Site Recovery components on-premises. 但是,为了获取准确的已实现吞吐量结果,建议在 Windows Server 上运行此规划器,该 Server 的硬件配置应与用来启用灾难恢复保护(通过恢复到 Azure 的方式进行保护)的某个 Hyper-V 服务器相同。However, to get accurate achieved throughput results, we recommend that you run the planner on a Windows Server that has the same hardware configuration as that of one of the Hyper-V servers that you will use to enable disaster recovery protection to Azure.

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

兼容性评估Compatibility assessment

  • 根据磁盘数量、磁盘大小、IOPS、变动量和一些 VM 特征评估 VM 的合格性。VM eligibility assessment, based on number of disks, disk size, IOPS, churn, and few VM characteristics.

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

  • 增量复制所需的估计网络带宽The estimated network bandwidth that's required for delta replication
  • Azure Site Recovery 可以获得的从本地到 Azure 的吞吐量The throughput that Azure Site Recovery can get from on-premises to Azure
  • 给定带宽可以实现的 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 的存储类型(标准或高级存储帐户)要求The storage type (standard or premium storage account) requirement for each VM
  • 要为复制设置的标准和高级存储帐户总数The total number of standard and premium storage accounts to be set up for replication
  • 基于 Azure 存储指南的存储帐户命名建议Storage-account naming suggestions, based on Azure Storage guidance
  • 适用于所有 VM 的存储帐户归置The storage-account placement for all VMs
  • 针对订阅执行测试性故障转移或故障转移之前要设置的 Azure 核心数The number of Azure cores to be set up before test failover or failover on the subscription
  • 适用于每个本地 VM 的 Azure VM 建议大小The Azure VM-recommended size for each on-premises VM

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

  • 在 Hyper-V 存储的每个卷上成功地进行初始复制和增量复制所需的可用存储空间,可确保 VM 复制不会导致任何会对生产应用程序造成负面影响的停机The required free storage space on each volume of Hyper-V storage for successful initial replication and delta replication to ensure that VM replication will not cause any undesirable downtime for your production applications
  • 需要为 Hyper-V 复制设置的最大复制频率Maximum copy frequency to be set for Hyper-V replication

初始复制批处理指南Initial replication batching guidance

  • 要用于保护的 VM 批数Number of VM batches to be used for protection
  • 每个批次中的 VM 的列表List of VMs in each batch
  • 对每个批次进行保护的顺序Order in which each batch is to be protected
  • 完成每个批次的初始复制所需的估计时间Estimated time to complete initial replication of each batch

DR 到 Azure 的估算成本Estimated DR cost to Azure

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

重要

由于使用量可能会随着时间的推移而增加,所有上述工具计算在执行时都会假定在工作负荷特征中存在一个 30% 的增长系数,而且所有分析指标(读/写 IOPS、变动量等)的值都会使用 95%。Because usage is likely to increase over time, all the preceding tool calculations are performed assuming a 30% growth factor in workload characteristics, and using a 95th percentile value of all the profiling metrics (read/write IOPS, churn, and so forth). 这两个元素(增长系数和百分位数计算)均可配置。Both of these elements (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

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
可以按 Azure Site Recovery 部署规划器的运行实例进行分析的服务器数Number of servers that can be profiled per running instance of the Azure 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 profile at a time) 不可用NA 多个(一次可以分析多个主机或主机群集的 VM)Multiple (VMs across multiple hosts or host clusters can be profile 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.

先决条件Prerequisites

此工具有三个针对 Hyper-V 的主要阶段:获取 VM 列表、分析,以及生成报表。The tool has three main phases for Hyper-V: get VM list, profiling, and report generation. 此外还有第四个选项,即仅计算吞吐量。There is also a fourth option to calculate throughput only. 下表中显示了需要在其上执行不同阶段的服务器的要求:The requirements for the server on which the different phases need to be executed are presented in the following table:

服务器要求Server requirement 说明Description
获取 VM 列表、分析和吞吐量测量Get VM list, profiling, and throughput measurement
  • 操作系统:Microsoft Windows Server 2016 或 Microsoft Windows Server 2012 R2Operating system: Microsoft Windows Server 2016 or Microsoft Windows Server 2012 R2
  • 计算机配置:8 个 vCPU、16 GB RAM、300 GB HDDMachine configuration: 8 vCPUs, 16 GB RAM, 300 GB HDD
  • Microsoft .NET Framework 4.5Microsoft .NET Framework 4.5
  • Microsoft Visual C++ Redistributable for Visual Studio 2012Microsoft Visual C++ Redistributable for Visual Studio 2012
  • 可在此服务器中通过 Internet 访问 AzureInternet access to Azure from this server
  • Azure 存储帐户Azure storage account
  • 服务器上的管理员访问权限Administrator access on the server
  • 至少 100 GB 的可用磁盘空间(假定有 1000 个 VM,每个平均包含 3 个磁盘,分析时间为 30 天)Minimum 100 GB of free disk space (assuming 1000 VMs with an average of three disks each, profiled for 30 days)
  • 必须将从其运行 Azure Site Recovery 部署规划器工具的 VM 添加到包含所有 Hyper-V 服务器的 TrustedHosts 列表。The VM from where you are running the Azure Site Recovery deployment planner tool must be added to TrustedHosts list of all the Hyper-V servers.
  • 必须将要分析的所有 Hyper-V 服务器都添加到要运行该工具的客户端 VM 的 TrustedHosts 列表中。All Hyper-V servers to be profiled must be added to TrustedHosts list of the client VM from where the tool is being run. 详细了解如何将服务器添加到 TrustedHosts 列表中Learn more to add servers into TrustedHosts list.
  • 应从客户端上的 PowerShell 或命令行控制台使用管理特权运行此工具The tool should be run from Administrative privileges from PowerShell or command-line console on the client
报告生成Report generation 装有 Microsoft Excel 2013 或更高版本的 Windows 电脑或 Windows ServerA Windows PC or Windows Server with Microsoft Excel 2013 or later
用户权限User permissions 在“获取 VM 列表”和“分析”操作过程中用于访问 Hyper-V 群集/Hyper-V 主机的管理员帐户。Administrator account to access Hyper-V cluster/Hyper-V host during get VM list and profiling operations.
所有需要进行分析的主机都应有一个使用相同凭据(即用户名和密码)的域管理员帐户All the hosts that need to be profiled should have a domain administrator account with the same credentials i.e. user name and password

将服务器添加到 TrustedHosts 列表中的步骤Steps to add servers into TrustedHosts List

  1. 要从其部署此工具的 VM 应该让需要分析的所有主机都位于其 TrustedHosts 列表中。The VM from where the tool is to be deployed should have all the hosts to be profiled in its TrustedHosts list. 若要将客户端添加到 Trustedhosts 列表中,请在 VM 上通过提升的 PowerShell 运行以下命令。To add the client into Trustedhosts list run the following command from an elevated PowerShell on the VM. VM 可以是 Windows Server 2012 R2 或 Windows Server 2016。The VM can be a Windows Server 2012 R2 or Windows Server 2016.

     set-item wsman:\localhost\Client\TrustedHosts -value '<ComputerName>[,<ComputerName>]' -Concatenate
    
  2. 每个需要分析的 Hyper-V 主机都应:Each Hyper-V Host that needs to be profiled should have:

    a.a. 有一个 VM,以便其上的此工具能够在其 TrustedHosts 列表中运行。The VM on which the tool is going to be run in its TrustedHosts list. 从 Hyper-V 主机上权限提升的 PowerShell 运行以下命令。Run the following command from an elevated PowerShell on the Hyper-V host.

         set-item wsman:\localhost\Client\TrustedHosts -value '<ComputerName>[,<ComputerName>]' -Concatenate
    

    b.b. 已启用 PowerShell 远程功能。PowerShell remoting enabled.

         Enable-PSRemoting -Force
    

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

  1. 下载最新版本的 Azure Site Recovery Deployment PlannerDownload the latest version of the Azure Site Recovery deployment planner. 该工具已打包到 .zip 文件夹中。The tool is packaged in a .zip folder. 同一工具支持 VMware 到 Azure 与 Hyper-V 到 Azure 灾难恢复方案。The same tool supports both VMware to Azure and Hyper-V to Azure disaster recovery scenarios. 也可将此工具用于 Hyper-V 到辅助站点灾难恢复方案,但请忽略报表中的 Azure 基础结构建议。You can use this tool for Hyper-V-to secondary site disaster recovery scenario as well but ignore the Azure infrastructure recommendation from the report.

  2. 将 .zip 文件夹复制到要在其上运行该工具的 Windows Server。Copy the .zip folder to the Windows Server on which you want to run the tool. 可以在 Windows Server 2012 R2 或 Windows Server 2016 上运行此工具。You can run the tool on a Windows Server 2012 R2 or Windows Server 2016. 服务器必须具有相应的网络访问权限,能够连接到 Hyper-V 群集或 Hyper-V 主机,其中有需要分析的 VM。The server must have network access to connect to the Hyper-V cluster or Hyper-V host that holds the VMs to be profiled. 建议将要运行此工具的 VM 的硬件配置设置为与需要保护的 Hyper-V 服务器的硬件配置相同。We recommend that you have the same hardware configuration of the VM, where the tool is going to run, as that of the Hyper-V server, which you want to protect. 此类配置可确保该工具所报告的已实现吞吐量与 Azure Site Recovery 在复制过程中能够达到的实际吞吐量相符。Such a configuration ensures that the achieved throughput that the tool reports matches the actual throughput that Azure Site Recovery can achieve during replication. 吞吐量计算取决于服务器上的可用网络带宽和服务器的硬件配置(CPU、存储等)。The throughput calculation depends on available network bandwidth on the server and hardware configuration (CPU, storage, and so forth) of the server. 计算的是从运行此工具的服务器到 Azure 的吞吐量。The throughput is calculated from the server where the tool is running to Azure. 如果该服务器的硬件配置不同于 Hyper-V 服务器的硬件配置,该工具所报告的已实现吞吐量将不准确。If the hardware configuration of the server differs from the Hyper-V server, the achieved throughput that the tool reports will be inaccurate. 建议的 VM 配置:8 个 vCPU、16 GB RAM、300 GB HDD。The recommended configuration of the VM: 8 vCPUs, 16 GB RAM, 300 GB HDD.

  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

更新至最新版本的部署规划器Updating to the latest version of deployment planner

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

如果部署规划器为旧版,请执行以下操作之一:If you have previous version of the 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 recommended 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 will be used to generate the report. 如果传递不同的输出目录,则会创建新文件,生成报告时不能使用旧的分析数据。If you pass a different output directory, new files are created, and old profiled data is not used to generate the report.

    每个新的 Deployment Planner 都是 .zip 文件的累积更新。Each new deployment planner 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

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

后续步骤Next steps