为 Hyper-V VM 灾难恢复规划容量Plan capacity for Hyper-V VM disaster recovery

适用于 Hyper-V 到 Azure 部署的 Azure Site Recovery 部署规划器提供了以下内容:The Azure Site Recovery Deployment Planner for Hyper-V to Azure deployment provides the following:

  • 根据磁盘数量、磁盘大小、IOPS、变动量和一些 VM 特征评估 VM 的合格性VM eligibility assessment, based on the number of disks, disk size, IOPS, churn, and a few VM characteristics
  • 网络带宽需求与 RPO 评估Network bandwidth need versus RPO assessment
  • Azure 基础结构需求Azure infrastructure requirements
  • 本地基础结构需求On-premises infrastructure requirements
  • 初始复制批处理指导原则Initial replication batching guidance
  • 灾难恢复到 Azure 的总估计成本Estimated total disaster recovery cost to Azure

Azure Site Recovery Capacity Planner 工具可帮助用户确定通过 Azure Site Recovery 复制 Hyper-V VM 时的容量要求。Azure Site Recovery Capacity Planner helps you determine your capacity requirements when you replicate Hyper-V VMs with Azure Site Recovery.

使用 Site Recovery Capacity Planner 可以分析源环境和工作负荷。Use Site Recovery Capacity Planner to analyze your source environment and workloads. 它可以帮助估计带宽需求、源位置所需的服务器资源,以及目标位置所需的资源(VM 和存储等)。It helps you estimate bandwidth needs, the server resources you need for the source location, and the resources (such as VMs and storage) you need in the target location.

可以通过两种模式运行该工具:You can run the tool in two modes:

  • 快速规划:在此模式下运行该工具时,可以根据 VM 平均数、磁盘、存储和更改率来获取网络和服务器投影。Quick planning: Provides network and server projections based on an average number of VMs, disks, storage, and change rate.
  • 详细规划:提供 VM 级别每个工作负荷的详细信息。Detailed planning: Provides details of each workload at the VM level. 分析 VM 兼容性,获取网络和服务器投影。Analyze VM compatibility and get network and server projections.

开始之前Before you start

  • 收集环境信息,包括 VM 数、每个 VM 的磁盘数、每个磁盘的存储。Gather information about your environment, including VMs, disks per VM, storage per disk.
  • 确定已复制数据的每日更改(改动)率。Identify your daily change (churn) rate for replicated data. 下载 Hyper-V 容量计划工具以获取更改率。Download the Hyper-V capacity planning tool to get the change rate. 详细了解此工具。Learn more about this tool. 我们建议运行此工具一周以上的时间以获取平均值。We recommend that you run this tool over a week to capture averages.

运行快速规划器Run the Quick Planner

  1. 下载并打开 Site Recovery Capacity Planner 工具。Download and open Site Recovery Capacity Planner. 需要运行宏。You need to run macros. 在出现提示时,请选择启用编辑内容的选项。When you're prompted, make selections to enable editing and content.

  2. 在“选择规划器类型”列表框中,选择“快速规划器” 。In the Select a planner type list box, select Quick Planner.

    “选择规划器类型”选项的屏幕截图,其中的快速规划器处于选中状态。

  3. 在“Capacity Planner”工作表中输入所需信息。 On the Capacity Planner worksheet, enter the required information. 必须填写以下屏幕快照中标有红圈的所有字段:Fill in all the fields circled in red in the following screenshot:

    a.a. 在“选择你的方案” 中,选择“Hyper-V 到 Azure” 或“VMware/物理设备到 Azure” .In Select your scenario, choose Hyper-V to Azure or VMware/Physical to Azure.

    b.b. 在“平均每日数据更改率(%)”中输入使用 Hyper-V 容量计划工具Site Recovery Deployment Planner 收集的信息。 In Average daily data change rate (%), enter the information you gather by using the Hyper-V capacity planning tool or Site Recovery Deployment Planner.

    c.c. 将 Hyper-V VM 复制到 Azure 时,不使用“压缩”设置。 The Compression setting isn't used when you replicate Hyper-V VMs to Azure. 对于压缩,请使用第三方应用程序(例如 Riverbed)。For compression, use a third-party appliance, such as Riverbed.

    d.d. 在“保留天数”中,指定副本应保留的天数。 In Retention in days, specify in days how long to retain replicas.

    e.e. 在“完成成批虚拟机的初始复制所需的小时数”和“初始复制批处理的虚拟机数”中,可以输入用于计算初始复制要求的设置 。In Number of hours in which initial replication for the batch of virtual machines should complete and Number of virtual machines per initial replication batch, enter settings that are used to compute initial replication requirements. 部署 Site Recovery 时,应上传整个初始数据集。When Site Recovery is deployed, the entire initial data set is uploaded.

    Capacity Planner 工作表的屏幕截图,显示了所需的输入信息。

  4. 输入源环境的值以后,显示的输出将包括:After you enter the values for the source environment, the displayed output includes:

    • 增量复制所需的带宽(MB/秒) :根据每日数据更改率的平均值计算增量复制的网络带宽。Bandwidth required for delta replication (in Megabits/sec): Network bandwidth for delta replication is calculated on the average daily data change rate.
    • 初始复制所需的带宽(MB/秒) :根据你输入的初始复制值计算初始复制的网络带宽。Bandwidth required for initial replication (in Megabits/sec): Network bandwidth for initial replication is calculated on the initial replication values you enter.
    • 所需存储(GB) :所需的总 Azure 存储。Storage required (in GBs): The total Azure storage required.
    • 标准存储的总 IOPS:根据所有标准存储帐户的 8K IOPS 单元大小计算的数字。Total IOPS on Standard Storage: The number is calculated based on the 8K IOPS unit size on the total standard storage accounts. 对于快速规划器,该数字根据所有源 VM 磁盘数以及每日数据更改率来计算。For the Quick Planner, the number is calculated based on all the source VM disks and the daily data change rate. 对于详细规划器,该数字根据映射到标准 Azure VM 的 VM 总数以及这些 VM 的数据更改率来计算。For the Detailed Planner, the number is calculated based on the total number of VMs that are mapped to standard Azure VMs and the data change rate on those VMs.
    • 所需的标准存储帐户数:保护 VM 所需的标准存储帐户总数。Number of Standard storage accounts required: The total number of standard storage accounts needed to protect the VMs. 标准存储帐户最高可以在标准存储的所有 VM 中保持 20000 IOPS。A standard storage account can hold up to 20,000 IOPS across all the VMs in standard storage. 每个磁盘支持的最大 IOPS 为 500A maximum of 500 IOPS is supported per disk.
    • 所需的 Blob 磁盘数:在 Azure 存储中创建的磁盘数。Number of Blob disks required: The number of disks that are created on Azure storage.
    • 所需的高级存储帐户数:保护 VM 所需的高级存储帐户总数。Number of premium accounts required: The total number of premium storage accounts needed to protect the VMs. IOPS 较高(高于 20,000)的源 VM 需要高级存储帐户。A source VM with high IOPS (greater than 20,000) needs a premium storage account. 高级存储帐户最高可支持 80,000 IOPS。A premium storage account can hold up to 80,000 IOPS.
    • 高级存储的总 IOPS:根据所有高级存储帐户的 256K IOPS 单元大小计算的数字。Total IOPS on Premium Storage: The number is calculated based on the 256K IOPS unit size on the total premium storage accounts. 对于快速规划器,该数字根据所有源 VM 磁盘数以及每日数据更改率来计算。For the Quick Planner, the number is calculated based on all the source VM disks and the daily data change rate. 对于详细规划器,该数字根据映射到高级 Azure VM(DS 和 GS 系列)的 VM 总数以及这些 VM 的数据更改率来计算。For the Detailed Planner, the number is calculated based on the total number of VMs that are mapped to premium Azure VMs (DS and GS series) and the data change rate on those VMs.
    • 所需的配置服务器数:显示需要多少个配置服务器才能完成该部署。Number of Configuration Servers required: Shows how many configuration servers are required for the deployment.
    • 所需的其他进程服务器数:显示除了默认在配置服务器上运行的进程服务器外,是否还需要其他进程服务器。Number of additional Process Servers required: Shows whether additional process servers are required, in addition to the process server that's running on the configuration server by default.
    • 源中的 100% 附加存储:显示源位置是否需要其他存储。100% additional storage on the Source: Shows whether additional storage is required in the source location.

    根据提供的输入显示的输出的屏幕截图。

运行详细规划器Run the Detailed Planner

  1. 下载并打开 Site Recovery Capacity Planner 工具。Download and open Site Recovery Capacity Planner. 需要运行宏。You need to run macros. 在出现提示时,请选择启用编辑内容的选项。When you're prompted, make selections to enable editing and content.

  2. 在“选择规划器类型” 中,从列表框中选择“详细规划器” 。In Select a planner type, select Detailed Planner from the list box.

    “选择规划器类型”选项的屏幕截图,其中的详细规划器处于选中状态。

  3. 在“工作负荷限定”工作表中输入所需的信息。 On the Workload Qualification worksheet, enter the required information. 必须填写所有标记的字段。You must fill in all the marked fields.

    a.a. 在“处理器内核数”中指定源服务器上的内核总数。 In Processor Cores, specify the total number of cores on a source server.

    b.b. 在“内存分配(MB)”中指定源服务器的 RAM 大小。 In Memory allocation (in MBs), specify the RAM size of a source server.

    c.c. NIC 数:指定源服务器上的网络适配器数。In Number of NICs, specify the number of network adapters on a source server.

    d.d. 在“总存储空间(GB)”中指定 VM 存储空间的总大小。 In Total Storage (in GB), specify the total size of the VM storage. 例如,如果源服务器有 3 个磁盘,每个磁盘的大小为 500 GB,则总的存储空间大小为 1500 GB。For example, if the source server has three disks with 500 GB each, total storage size is 1,500 GB.

    e.e. 在“附加磁盘数” 中指定源服务器的磁盘总数。In Number of disks attached, specify the total number of disks of a source server.

    f.f. 在“磁盘容量使用率”中指定平均使用率。 In Disk capacity utilization (%), specify the average utilization.

    g.g. 在“每日数据更改率(%)”中指定源服务器的每日数据更改率。 In Daily data change rate (%), specify the daily data change rate of a source server.

    h.如果该值不存在,请单击“添加行”。h. 在“映射 Azure VM 大小”中输入要映射的 Azure VM 大小。 In Mapping Azure VM size, enter the Azure VM size that you want to map. 如果不想手动执行此操作,请选择“计算 IaaS VM”。 If you don't want to do this manually, select Compute IaaS VMs. 如果输入了手动设置,然后单击“计算 IaaS VM”,系统可能会覆盖手动设置。 If you input a manual setting and then select Compute IaaS VMs, the manual setting might be overwritten. 计算过程会自动确定 Azure VM 大小的最佳匹配项。The compute process automatically identifies the best match on Azure VM size.

    工作负荷限定工作表的屏幕截图,显示了所需的输入信息。

  4. 如果选择“计算 IaaS VM”,则会执行以下操作: If you select Compute IaaS VMs, here's what it does:

    • 验证必需的输入。Validates the mandatory inputs.
    • 计算 IOPS,并为每个可以复制到 Azure 的 VM 提供最佳 Azure VM 大小匹配项的建议。Calculates IOPS and suggests the best Azure VM size match for each VM that's eligible for replication to Azure. 如果系统检测不到合适的 Azure VM 大小,则会显示错误消息。If an appropriate size Azure VM can't be detected, an error displays. 例如,如果附加的磁盘数为 65,则会显示错误消息,因为 Azure VM 的最大大小为 64。For example, if the number of disks attached is 65, an error displays because the highest size for an Azure VM is 64.
    • 建议一个适用于 Azure VM 的存储帐户。Suggests a storage account that can be used for an Azure VM.
    • 计算工作负荷所需的标准存储帐户和高级存储帐户的总数。Calculates the total number of standard storage accounts and premium storage accounts required for the workload. 向下滚动,以便查看可用于源服务器的 Azure 存储类型和存储帐户。Scroll down to view the Azure storage type and the storage account that can be used for a source server.
    • 根据为 VM 分配的所需存储类型(标准或高级)以及附加磁盘数完成表的其余部分并对其排序。Completes and sorts the rest of the table based on the required storage type (standard or premium) assigned for a VM and the number of disks attached. 对于所有满足 Azure 要求的 VM,列“VM 是否合格?” 显示“是” 。For all VMs that meet the requirements for Azure, the column Is VM qualified? shows Yes. 如果 VM 无法备份到 Azure,则会显示错误消息。If a VM can't be backed up to Azure, an error displays.

AA 到 AE 列为输出,提供的是每个 VM 的信息。Columns AA to AE are output and provide information for each VM.

屏幕截图,显示输出列 AA 到 AE。

示例Example

例如,如果有 6 个 VM,其值如表中所示,该工具会计算和分配最佳 Azure VM 匹配项以及 Azure 存储需求。As an example, for six VMs with the values shown in the table, the tool calculates and assigns the best Azure VM match and the Azure storage requirements.

屏幕截图,显示工作负荷限定分配。

  • 在示例输出中,请注意以下问题:In the example output, note the following:

    • 第一列是用于 VM、磁盘和改动的验证列。The first column is a validation column for the VMs, disks, and churn.
    • 5 个 VM 需要 2 个标准存储帐户和 1 个高级存储帐户。Two standard storage accounts and one premium storage account are needed for five VMs.
    • VM3 不符合受保护资格,因为一个或多个磁盘大于 1 TB。VM3 doesn't qualify for protection because one or more disks are more than 1 TB.
    • VM1 和 VM2 可以使用第一个标准存储帐户。VM1 and VM2 can use the first standard storage account
    • VM4 可以使用第二个标准存储帐户。VM4 can use the second standard storage account.
    • VM5 和 VM6 需要高级存储帐户,并且都可以使用单个帐户。VM5 and VM6 need a premium storage account, and both can use a single account.

    备注

    标准存储和高级存储的 IOPS 在 VM 级别而非磁盘级别进行计算。IOPS on standard and premium storage are calculated at the VM level and not at disk level. 标准 VM 最多可处理每个磁盘 500 IOPS。A standard VM can handle up to 500 IOPS per disk. 如果磁盘的 IOPS 大于 500,则需要高级存储。If IOPS for a disk are greater than 500, you need premium storage. 如果某个磁盘的 IOPS 超出 500 但所有 VM 磁盘的 IOPS 仍在标准 Azure VM 的支持范围内,则规划器会选取标准 VM 而不是 DS 或 GS 系列。If IOPS for a disk are more than 500 but IOPS for the total VM disks are within the support standard Azure VM limits, the planner picks a standard VM and not the DS or GS series. (Azure VM 限制包括 VM 大小、磁盘数、适配器数、CPU 和内存。)需要使用相应的 DS 或 GS 系列 VM 来手动更新“映射 Azure 大小”单元格。(The Azure VM limits are VM size, number of disks, number of adapters, CPU, and memory.) You need to manually update the mapping Azure size cell with the appropriate DS or GS series VM.

输入所有信息后,选择“将数据提交到规划器工具”打开 Capacity Planner。 After all the information is entered, select Submit data to the planner tool to open Capacity Planner. 工作负荷会突出显示,以表明其是否符合受保护资格。Workloads are highlighted to show whether they're eligible for protection.

在 Capacity Planner 中提交数据Submit data in Capacity Planner

  1. 打开“Capacity Planner”工作表时,该表会根据你所指定的设置进行填充。 When you open the Capacity Planner worksheet, it's populated based on the settings you specified. “工作负荷”一词会出现在“基础输入源”单元格中,用来表示输入是“工作负荷限定”工作表。 The word "Workload" appears in the Infra inputs source cell to show that the input is the Workload Qualification worksheet.

  2. 如果想要进行更改,则需修改“工作负荷限定”工作表。 If you want to make changes, you need to modify the Workload Qualification worksheet. 然后再次选择“将数据提交到规划器工具”。 Then select Submit data to the planner tool again.

    屏幕截图,显示 Capacity Planner 工作表中修改的输入和生成的输出。

后续步骤Next steps

了解如何运行容量计划工具。Learn how to run the capacity planning tool.