分析部署规划器报表以从 VMware 灾难恢复到 AzureAnalyze the Deployment Planner report for VMware disaster recovery to Azure

生成的 Microsoft Excel 报表包含以下工作表:The generated Microsoft Excel report contains the following sheets:

本地摘要On-premises summary

“本地摘要”工作表概述了分析的 VMware 环境。The On-premises summary worksheet provides an overview of the profiled VMware environment.

VMware 环境的本地摘要

开始日期结束日期:生成报告时要考虑的分析数据的开始和结束日期。Start Date and End Date: The start and end dates of the profiling data considered for report generation. 默认情况下,开始日期是开始分析的日期,结束日期是停止分析的日期。By default, the start date is the date when profiling starts, and the end date is the date when profiling stops. 如果结合这些参数生成报告,可以使用“StartDate”和“EndDate”值。This can be the 'StartDate' and 'EndDate' values if the report is generated with these parameters.

分析总天数:要生成报告的开始和结束日期之间的分析总天数。Total number of profiling days: The total number of days of profiling between the start and end dates for which the report is generated.

兼容的虚拟机数:为其计算了所需网络带宽、所需存储帐户数、Microsoft Azure 核心数、配置服务器与附加进程服务器数的兼容 VM 总数。Number of compatible virtual machines: The total number of compatible VMs for which the required network bandwidth, required number of storage accounts, Azure cores, configuration servers and additional process servers are calculated.

所有兼容虚拟机的磁盘总数:此数字用作输入之一,确定要在部署中使用的配置服务器和附加进程服务器的数目。Total number of disks across all compatible virtual machines: The number that's used as one of the inputs to decide the number of configuration servers and additional process servers to be used in the deployment.

每个兼容虚拟机的平均磁盘数:根据所有兼容 VM 计算出的平均磁盘数。Average number of disks per compatible virtual machine: The average number of disks calculated across all compatible VMs.

平均磁盘大小(GB) :根据所有兼容 VM 计算出的平均磁盘大小。Average disk size (GB): The average disk size calculated across all compatible VMs.

所需 RPO (分钟) :默认恢复点目标,或者在生成报告时为了估算所需带宽为“DesiredRPO”参数传递的值。Desired RPO (minutes): Either the default recovery point objective or the value passed for the 'DesiredRPO' parameter at the time of report generation to estimate required bandwidth.

所需带宽(Mbps) :在生成报告时为了估算可实现 RPO 为“Bandwidth”参数传递的值。Desired bandwidth (Mbps): The value that you have passed for the 'Bandwidth' parameter at the time of report generation to estimate achievable RPO.

每日观察到的典型数据变动量(GB) :在所有分析日期观察到的平均数据变动量。Observed typical data churn per day (GB): The average data churn observed across all profiling days. 此数字用作输入之一,确定要在部署中使用的配置服务器和附加进程服务器的数目。This number is used as one of the inputs to decide the number of configuration servers and additional process servers to be used in the deployment.

建议Recommendations

VMware 到 Azure 报表的建议表根据选定的所需 RPO 提供以下详细信息:The recommendations sheet of the VMware to Azure report has the following details as per the selected desired RPO:

适用于 VMware 到 Azure 报表的建议

分析的数据Profiled data

Deployment Planner 中的分析数据视图

数据分析期:在此期间运行了分析。Profiled data period: The period during which the profiling was run. 默认情况下,该工具使用所有分析数据进行计算,除非在生成报告期间使用 StartDate 和 EndDate 选项生成特定时间段的报告。By default, the tool includes all profiled data in the calculation, unless it generates the report for a specific period by using StartDate and EndDate options during report generation.

服务器名称:为其生成了 VM 报告的 VMware vCenter 或 ESXi 主机的名称或 IP 地址。Server Name: The name or IP address of the VMware vCenter or ESXi host whose VMs' report is generated.

所需 RPO:部署的恢复点目标。Desired RPO: The recovery point objective for your deployment. 默认情况下,所需网络带宽是根据 RPO 值为 15、30 和 60 分钟计算的。By default, the required network bandwidth is calculated for RPO values of 15, 30, and 60 minutes. 根据所做的选择,受影响的值会在工作表中更新。Based on the selection, the affected values are updated on the sheet. 如果生成报告时使用了 DesiredRPOinMin 参数,该值会显示在“所需 RPO”结果中。If you have used the DesiredRPOinMin parameter while generating the report, that value is shown in the Desired RPO result.

分析概述Profiling overview

Deployment Planner 中的分析结果

分析的虚拟机总数:提供了其分析数据的 VM 总数。Total Profiled Virtual Machines: The total number of VMs whose profiled data is available. 如果 VMListFile 中包含未分析的任何 VM 的名称,则生成报告时不会考虑这些 VM,会将其从分析的 VM 总数中排除。If the VMListFile has names of any VMs which were not profiled, those VMs are not considered in the report generation and are excluded from the total profiled VMs count.

兼容的虚拟机数:可以使用Site Recovery 在 Azure 中保护的 VM 数。Compatible Virtual Machines: The number of VMs that can be protected to Azure by using Site Recovery. 它是计算了所需网络带宽、存储帐户数、Azure 核心数以及配置服务器与附加进程服务器数的兼容 VM 总数。It is the total number of compatible VMs for which the required network bandwidth, number of storage accounts, number of Azure cores, and number of configuration servers and additional process servers are calculated. “兼容的 VM”部分提供了每个兼容的 VM 的详细信息。The details of every compatible VM are available in the "Compatible VMs" section.

不兼容的虚拟机数:在保护方面与 Site Recovery 不兼容的已分析 VM 数。Incompatible Virtual Machines: The number of profiled VMs that are incompatible for protection with Site Recovery. “不兼容的 VM”部分说明了不兼容的原因。The reasons for incompatibility are noted in the "Incompatible VMs" section. 如果 VMListFile 包含任何未分析 VM 的名称,则这些 VM 不计入不兼容 VM 的数目。If the VMListFile has names of any VMs that were not profiled, those VMs are excluded from the incompatible VMs count. 在“不兼容的 VM”部分的末尾,这些 VM 作为“找不到数据”类型列出。These VMs are listed as "Data not found" at the end of the "Incompatible VMs" section.

所需 RPO:以分钟为单位的所需恢复点目标。Desired RPO: Your desired recovery point objective, in minutes. 针对以下三个 RPO 值生成报告:15 分钟(默认值)、30 分钟和 60 分钟。The report is generated for three RPO values: 15 (default), 30, and 60 minutes. 会根据你在工作表右上方“所需 RPO”下拉列表中所做的选择来更改报告中的带宽建议。The bandwidth recommendation in the report is changed based on your selection in the Desired RPO drop-down list at the top right of the sheet. 如果结合某个自定义值使用“-DesiredRPO”参数生成了报告,此自定义值会在“所需 RPO”下拉列表中显示为默认值。 If you have generated the report by using the -DesiredRPO parameter with a custom value, this custom value will show as the default in the Desired RPO drop-down list.

所需的网络带宽 (Mbps)Required network bandwidth (Mbps)

Deployment Planner 中的所需网络带宽

为了满足 100% 时间 RPO:分配建议的以 Mbps 为单位的带宽,以便满足 100% 时间的所需 RPO。To meet RPO 100 percent of the time: The recommended bandwidth in Mbps to be allocated to meet your desired RPO 100 percent of the time. 这种带宽量必须专用于所有兼容 VM 的稳态增量复制,避免任何 RPO 违规。This amount of bandwidth must be dedicated for steady-state delta replication of all your compatible VMs to avoid any RPO violations.

为了满足 90% 时间的 RPO:如果由于宽带价格或任何其他原因而无法设置所需的带宽来满足 100% 时间的所需 RPO,可以选择规格较低但仍可满足 90% 时间的所需 RPO 的带宽设置。To meet RPO 90 percent of the time: Because of broadband pricing or for any other reason, if you cannot set the bandwidth needed to meet your desired RPO 100 percent of the time, you can choose to go with a lower bandwidth setting that can meet your desired RPO 90 percent of the time. 为了帮助理解设置这种规格较低的带宽所造成的影响,报告中会根据预期发生的 RPO 违规的数目和持续时间提供一项假设 (what-if) 分析。To understand the implications of setting this lower bandwidth, the report provides a what-if analysis on the number and duration of RPO violations to expect.

实现的吞吐量:从运行 GetThroughput 命令的服务器到存储帐户所在的 Azure 区域的吞吐量。Achieved Throughput: The throughput from the server on which you have run the GetThroughput command to the Azure region where the storage account is located. 此吞吐量数字表示在配置服务器或进程服务器的存储和网络特征与运行该工具的服务器保持相同的前提下,使用 Site Recovery 保护兼容的 VM 时可实现的大致吞吐量水平。This throughput number indicates the estimated level that you can achieve when you protect the compatible VMs by using Site Recovery, provided that your configuration server or process server storage and network characteristics remain the same as that of the server from which you have run the tool.

对于复制,应设置建议的带宽以满足 100% 时间的 RPO。For replication, you should set the recommended bandwidth to meet the RPO 100 percent of the time. 在设置带宽后,如果工具所报告的已实现吞吐量没有增长,请执行以下操作:After you set the bandwidth, if you don't see any increase in the achieved throughput, as reported by the tool, do the following:

  1. 查看是否有任何网络服务质量 (QoS) 限制了 Site Recovery 吞吐量。Check to see whether there is any network Quality of Service (QoS) that is limiting Site Recovery throughput.

  2. 查看 Site Recovery 保管库是否位于从物理上来说最近的受支持 Microsoft Azure 区域,以尽量降低网络延迟。Check to see whether your Site Recovery vault is in the nearest physically supported Azure region to minimize network latency.

  3. 检查本地存储特征,确定能否改进硬件(例如,从 HDD 升级到 SSD)。Check your local storage characteristics to determine whether you can improve the hardware (for example, HDD to SSD).

  4. 更改进程服务器中的 Site Recovery 设置,增大用于复制的网络带宽量Change the Site Recovery settings in the process server to increase the amount network bandwidth used for replication.

如果是在其 VM 已经受保护的配置服务器或进程服务器上运行该工具,请运行该工具多次。If you are running the tool on a configuration server or process server that already has protected VMs, run the tool a few times. 已实现的吞吐量数字会更改,具体取决于在该时间点处理的数据更改量。The achieved throughput number changes depending on the amount of churn being processed at that point in time.

对于所有企业型 Site Recovery 部署,建议使用 ExpressRouteFor all enterprise Site Recovery deployments, we recommend that you use ExpressRoute.

所需的存储帐户Required storage accounts

下图显示了保护所有兼容 VM 所需的存储帐户(标准和高级)总数。The following chart shows the total number of storage accounts (standard and premium) that are required to protect all the compatible VMs. 若要了解适用于每个 VM 的存储帐户,请参阅“VM-存储位置”部分。To learn which storage account to use for each VM, see the "VM-storage placement" section. 如果使用的是部署规划器 v2.5,则此建议仅显示复制所需的标准缓存存储帐户数,因为数据会直接写入到托管磁盘。If you are using v2.5 of Deployment Planner, this recommendation only shows the number of standard cache storage accounts which are needed for replication since the data is being directly written to Managed Disks.

Deployment Planner 中的所需存储帐户

所需的 Azure 核心数Required number of Azure cores

此结果是在对所有兼容的 VM 进行故障转移或测试性故障转移之前需要设置的核心总数。This result is the total number of cores to be set up before failover or test failover of all the compatible VMs. 如果订阅中能够使用的核心太少,在执行测试性故障转移或故障转移时,Site Recovery 无法创建 VM。If too few cores are available in the subscription, Site Recovery fails to create VMs at the time of test failover or failover.

Deployment Planner 中的所需 Azure 核心数

所需的本地基础结构Required on-premises infrastructure

下图是要配置的配置服务器和附加进程服务器的总数,该数目足以保护所有兼容 VM。This figure is the total number of configuration servers and additional process servers to be configured that would suffice to protect all the compatible VMs. 根据所支持的配置服务器大小建议,该工具可能会建议使用更多的服务器。Depending on the supported size recommendations for the configuration server, the tool might recommend additional servers. 该建议取决于每日变动量和受保护 VM(假定每个 VM 平均有三个磁盘)的最大数目哪个更大,即在配置服务器或附加进程服务器上哪个最先达到。The recommendation is based on the larger of either the per-day churn or the maximum number of protected VMs (assuming an average of three disks per VM), whichever is hit first on the configuration server or the additional process server. 在“本地摘要”部分可以找到每天总变动量和受保护磁盘总数的详细信息。You'll find the details of total churn per day and total number of protected disks in the "On-premises summary" section.

Deployment Planner 中的所需本地基础结构

假设分析What-if analysis

此项分析概述了如果设置较低的带宽,导致只能在 90% 的时间内满足所需 RPO,则在分析期间可能会发生多少项违规。This analysis outlines how many violations could occur during the profiling period when you set a lower bandwidth for the desired RPO to be met only 90 percent of the time. 在任何给定的日期可能会发生一项或多项 RPO 违规。One or more RPO violations can occur on any given day. 下图显示了一天的峰值 RPO。The graph shows the peak RPO of the day. 基于此分析,可以确定在使用指定的较低带宽的条件下,是否可以接受所有日期的 RPO 违规数以及每天的峰值 RPO。Based on this analysis, you can decide if the number of RPO violations across all days and peak RPO hit per day is acceptable with the specified lower bandwidth. 如果可以接受,则可为复制分配较低的带宽,否则,应根据建议分配更高的带宽来满足 100% 时间的所需 RPO。If it is acceptable, you can allocate the lower bandwidth for replication, else allocate the higher bandwidth as suggested to meet the desired RPO 100 percent of the time.

Deployment Planner 中的模拟分析

在本部分,我们提供了可以进行并行保护的 VM 数的建议,目的是在 72 小时内使用建议的带宽完成初始复制,该带宽满足所设置的 100% 时间的所需 RPO。In this section, we recommend the number of VMs that can be protected in parallel to complete the initial replication within 72 hours with the suggested bandwidth to meet desired RPO 100 percent of the time being set. 此值是可以配置的值。This value is configurable value. 若要在生成报告时对其进行更改,请使用“GoalToCompleteIR” 参数。To change it at report-generation time, use the GoalToCompleteIR parameter.

下图显示了一系列带宽值和计算出的 VM 批大小计数,用于根据所有兼容 VM 上检测到的平均 VM 大小,在 72 小时内完成初始复制。The graph here shows a range of bandwidth values and a calculated VM batch size count to complete initial replication in 72 hours, based on the average detected VM size across all the compatible VMs.

在公共预览版中,报告不会指定应在批中包含的具体 VM。In the public preview, the report does not specify which VMs should be included in a batch. 可以使用“兼容的 VM”部分显示的磁盘大小找出每个 VM 的大小,为批选择 VM,也可以根据已知的工作负荷特征选择 VM。You can use the disk size shown in the "Compatible VMs" section to find each VM's size and select them for a batch, or you can select the VMs based on known workload characteristics. 初始复制的完成时间根据实际 VM 磁盘大小、已用磁盘空间和可用的网络吞吐量按比例变化。The completion time of the initial replication changes proportionally, based on the actual VM disk size, used disk space, and available network throughput.

建议的 VM 批大小

成本估算Cost estimation

下图显示的摘要视图包含灾难恢复 (DR) 到所选目标区域的 Azure 时的总估算成本,以及生成报表时所用的指定货币。The graph shows the summary view of the estimated total disaster recovery (DR) cost to Azure of your chosen target region and the currency that you have specified for report generation.

成本估算摘要

可以通过此摘要了解在使用 Azure Site Recovery 将所有兼容的 VM 转移到 Azure 进行保护时,需要支付的存储、计算、网络和许可证成本。The summary helps you to understand the cost that you need to pay for storage, compute, network, and license when you protect all your compatible VMs to Azure using Azure Site Recovery. 计算成本时,只针对兼容的 VM,不针对所有受分析的 VM。The cost is calculated on for compatible VMs and not on all the profiled VMs.

可以按月或按年查看成本。You can view the cost either monthly or yearly.

按组件成本:总 DR 成本分为四个部分:计算成本、存储成本、网络成本和 Azure Site Recovery 许可证成本。Cost by components The total DR cost is divided into four components: Compute, Storage, Network, and Azure Site Recovery license cost. 成本计算基于在复制时和 DR 演练时上述四个部分(计算、存储(高级和标准)、在本地站点和 Azure 之间配置的 ExpressRoute/VPN,以及 Azure Site Recovery 许可证)所对应的使用量。The cost is calculated based on the consumption that will be incurred during replication and at DR drill time for compute, storage (premium and standard), ExpressRoute/VPN that is configured between the on-premises site and Azure, and Azure Site Recovery license.

按状态成本:总灾难恢复 (DR) 成本按两种不同的状态(“复制”和“DR 演练”)分类。Cost by states The total disaster recovery (DR) cost is categories based on two different states - Replication and DR drill.

复制成本:复制期间产生的成本,Replication cost: The cost that will be incurred during replication. 涵盖存储成本、网络成本、Azure Site Recovery 许可证成本。It covers the cost of storage, network, and Azure Site Recovery license.

DR 演练成本:测试性故障转移期间产生的成本。DR-Drill cost: The cost that will be incurred during test failovers. Azure Site Recovery 会在测试性故障转移期间启动 VM。Azure Site Recovery spins up VMs during test failover. DR 演练成本涵盖了正在运行的 VM 的计算和存储成本。The DR drill cost covers the running VMs' compute and storage cost.

每月/年的 Azure 存储成本:表示针对高级和标准存储进行复制和 DR 演练时产生的总存储成本。Azure storage cost per Month/Year It shows the total storage cost that will be incurred for premium and standard storage for replication and DR drill. 可以在成本估算表中查看每个 VM 的详细成本分析。You can view detailed cost analysis per VM in the Cost Estimation sheet.

增长系数和使用的百分位值Growth factor and percentile values used

工作表底部的此部分显示用于已分析 VM 的所有性能计数器的百分位值(默认为第 95 百分位),以及所有计算中使用的增长系数(默认为 30%)。This section at the bottom of the sheet shows the percentile value used for all the performance counters of the profiled VMs (default is 95th percentile), and the growth factor (default is 30 percent) that's used in all the calculations.

增长系数和使用的百分位值

有关用作输入的可用带宽建议Recommendations with available bandwidth as input

有关用作输入的可用带宽建议

有时,知道无法为 Site Recovery 复制设置 x Mbps 以上的带宽。You might have a situation where you know that you cannot set a bandwidth of more than x Mbps for Site Recovery replication. 在该工具中可以输入可用带宽(生成报告时使用 -Bandwidth 参数),在数分钟内就能获得可实现的 RPO。The tool allows you to input available bandwidth (using the -Bandwidth parameter during report generation) and get the achievable RPO in minutes. 使用这个可实现的 RPO 值,可以确定是需要设置额外的带宽,还是可以使用某个灾难恢复解决方案来实现此 RPO。With this achievable RPO value, you can decide whether you need to set up additional bandwidth or you are OK with having a disaster recovery solution with this RPO.

500 Mbps 带宽的可实现 RPO

VM-存储位置VM-storage placement

备注

部署规划器 v2.5 及更高版本建议将直接复制到托管磁盘的计算机的存储位置。Deployment Planner v2.5 onwards recommends the storage placement for machines which will replicate directly to managed disks.

VM-粗糙年位置

复制存储类型:标准或高级托管磁盘,用于复制“要放置的 VM”列中所述的所有相应 VM。 Replication Storage Type: Either a standard or premium managed disk, which is used to replicate all the corresponding VMs mentioned in the VMs to Place column.

日志存储帐户类型:所有复制日志存储在标准存储帐户中。Log Storage Account Type: All the replication logs are stored in a standard storage account.

建议的存储帐户前缀:建议的三字符前缀,可用于缓存存储帐户的命名。Suggested Prefix for Storage Account: The suggested three-character prefix that can be used for naming the cache storage account. 可以使用自己的前缀,而该工具的建议则遵循存储帐户的分区命名约定You can use your own prefix, but the tool's suggestion follows the partition naming convention for storage accounts.

建议的日志帐户名称:在使用建议的前缀后出现的存储帐户名称。Suggested Log Account Name: The storage-account name after you include the suggested prefix. 将尖括号(< 和 >)中的名称替换为自定义输入。Replace the name within the angle brackets (< and >) with your custom input.

位置摘要:按存储类型列出受保护的 VM 所需的磁盘的摘要。Placement Summary: A summary of the disks needed to protected VMs by storage type. 它包括 VM 总数、所有磁盘上预配的总大小,以及磁盘总数。It includes the total number of VMs, total provisioned size across all disks, and total number of disks.

要放置的虚拟机:列出了为优化性能和使用而应放置在给定存储帐户中的所有 VM。Virtual Machines to Place: A list of all the VMs that should be placed on the given storage account for optimal performance and use.

兼容的 VMCompatible VMs

包含兼容 VM 的 Excel 电子表格

VM 名称:VM 名称或 IP 地址,生成报告时在 VMListFile 中使用。VM Name: The VM name or IP address that's used in the VMListFile when a report is generated. 此列还列出附加到 VM 的磁盘 (VMDK)。This column also lists the disks (VMDKs) that are attached to the VMs. 为了区分使用重复名称或 IP 地址的 vCenter VM,这些名称包含 ESXi 主机名。To distinguish vCenter VMs with duplicate names or IP addresses, the names include the ESXi host name. 列出的 ESXi 主机是在其中放置了 VM 的主机,该 VM 是在分析期间通过工具发现后放置的。The listed ESXi host is the one where the VM was placed when the tool discovered during the profiling period.

VM 兼容性:值为“是”和“是” *** *。“是”****针对 VM 适用于 高级 SSD 的情况。VM Compatibility: Values are Yes and *Yes*. _* Yes*** is for instances in which the VM is a fit for premium SSDs. 在这里,所分析的高变动量或 IOPS 磁盘适合 P20 或 P30 类别,但考虑到磁盘大小,因此将其归入较低的 P10 或 P20 类别。Here, the profiled high-churn or IOPS disk fits in the P20 or P30 category, but the size of the disk causes it to be mapped down to a P10 or P20. 存储帐户决定了根据大小对磁盘分类时,可将磁盘归入哪种高级存储磁盘类型。The storage account decides which premium storage disk type to map a disk to, based on its size. 例如:For example:

  • <128 GB 为 P10。<128 GB is a P10.
  • 128 GB 到 256 GB 为 P15128 GB to 256 GB is a P15
  • 256 GB 到 512 GB 为 P20。256 GB to 512 GB is a P20.
  • 512 GB 到 1024 GB 为 P30。512 GB to 1024 GB is a P30.
  • 1025 GB 到 2048 GB 为 P40。1025 GB to 2048 GB is a P40.
  • 2049 GB 到 4095 GB 为 P50。2049 GB to 4095 GB is a P50.

例如,如果某个磁盘按工作负荷特征应归入 P20 或 P30 类别,但按大小应归入较低的高级存储磁盘类型,则此工具会将该 VM 标记为“是*”。 For example, if the workload characteristics of a disk put it in the P20 or P30 category, but the size maps it down to a lower premium storage disk type, the tool marks that VM as Yes*. 该工具还建议根据建议的高级存储磁盘类型更改源磁盘大小,或者在故障转移后更改目标磁盘类型。The tool also recommends that you either change the source disk size to fit into the recommended premium storage disk type or change the target disk type post-failover.

存储类型:标准或高级。Storage Type: Standard or premium.

为复制创建的 Asrseeddisk(托管磁盘) :启用复制时创建的磁盘的名称。Asrseeddisk (Managed Disk) created for replication: The name of the disk that is created when you enable replication. 它将数据及其快照存储在 Azure 中。It stores the data and its snapshots in Azure.

峰值读/写 IOPS (包括增长系数) :磁盘上的峰值工作负荷读/写 IOPS(默认为第 95 百分位),包括将来的增长系数(默认为 30%)。Peak R/W IOPS (with Growth Factor): The peak workload read/write IOPS on the disk (default is 95th percentile), including the future growth factor (default is 30 percent). 请注意,VM 的读/写 IOPS 总数并非总是该 VM 各个磁盘的读/写 IOPS 之和,因为在分析期间,该 VM 每分钟的读/写 IOPS 峰值是其各个磁盘的读/写 IOPS 之和的峰值。Note that the total read/write IOPS of a VM is not always the sum of the VM's individual disks' read/write IOPS, because the peak read/write IOPS of the VM is the peak of the sum of its individual disks' read/write IOPS during every minute of the profiling period.

以 Mbps 为单位的峰值数据变动量(包括增长系数) :磁盘上的峰值变动率(默认为第 95 百分位),包括将来的增长系数(默认为 30%)。Peak Data Churn in Mbps (with Growth Factor): The peak churn rate on the disk (default is 95th percentile), including the future growth factor (default is 30 percent). 请注意,VM 的总数据变动量并非总是 VM 各个磁盘的数据变动量之和,因为 VM 的峰值数据变动量是该 VM 在分析期间每分钟的各个磁盘变动量之和的峰值。Note that the total data churn of the VM is not always the sum of the VM's individual disks' data churn, because the peak data churn of the VM is the peak of the sum of its individual disks' churn during every minute of the profiling period.

Azure VM 大小:适用于此本地 VM 的映射 Azure 云服务虚拟机大小。Azure VM Size: The ideal mapped Azure Cloud Services virtual-machine size for this on-premises VM. 映射取决于本地 VM 的内存、磁盘/核心/NIC 数以及读/写 IOPS。The mapping is based on the on-premises VM's memory, number of disks/cores/NICs, and read/write IOPS. 建议在符合所有本地 VM 特征的情况下,始终使用最小的 Azure VM 大小。The recommendation is always the lowest Azure VM size that matches all of the on-premises VM characteristics.

磁盘数:VM 上的虚拟机磁盘 (VMDK) 总数。Number of Disks: The total number of virtual machine disks (VMDKs) on the VM.

磁盘大小(GB) :VM 所有磁盘的总安装大小。Disk size (GB): The total setup size of all disks of the VM. 该工具还会显示 VM 中各个磁盘的磁盘大小。The tool also shows the disk size for the individual disks in the VM.

核心数:VM 上的 CPU 核心数。Cores: The number of CPU cores on the VM.

内存(MB):VM 上的 RAM。Memory (MB): The RAM on the VM.

NIC 数:VM 上的 NIC 数。NICs: The number of NICs on the VM.

启动类型:VM 的启动类型。Boot Type: Boot type of the VM. 它可以是 BIOS 或 EFI。It can be either BIOS or EFI. 目前,Azure Site Recovery 支持 Windows Server EFI VM(Windows Server 2012、2012 R2 和 2016),前提是启动盘中的分区数小于 4,引导扇区大小为 512 字节。Currently Azure Site Recovery supports Windows Server EFI VMs (Windows Server 2012, 2012 R2 and 2016) provided the number of partitions in the boot disk is less than 4 and boot sector size is 512 bytes. Azure Site Recovery 移动服务的版本最低必须为 9.13 才能保护 EFI VM。To protect EFI VMs, Azure Site Recovery mobility service version must be 9.13 or above. EFI VM 仅支持故障转移。Only failover is supported for EFI VMs. 不支持故障回复。Failback is not supported.

OS 类型:VM 的 OS 类型。OS Type: It is OS type of the VM. 可以是 Windows、Linux 或其他,具体取决于创建 VM 时从 VMware vSphere 中选择的模板。It can be either Windows or Linux or other based on the chosen template from VMware vSphere while creating the VM.

不兼容的 VMIncompatible VMs

包含不兼容 VM 的 Excel 电子表格

VM 名称:VM 名称或 IP 地址,生成报告时在 VMListFile 中使用。VM Name: The VM name or IP address that's used in the VMListFile when a report is generated. 此列还列出附加到 VM 的 VMDK。This column also lists the VMDKs that are attached to the VMs. 为了区分使用重复名称或 IP 地址的 vCenter VM,这些名称包含 ESXi 主机名。To distinguish vCenter VMs with duplicate names or IP addresses, the names include the ESXi host name. 列出的 ESXi 主机是在其中放置了 VM 的主机,该 VM 是在分析期间通过工具发现后放置的。The listed ESXi host is the one where the VM was placed when the tool discovered during the profiling period.

VM 兼容性:指示给定的 VM 为何无法与 Site Recovery 兼容使用。VM Compatibility: Indicates why the given VM is incompatible for use with Site Recovery. 会针对 VM 的每个不兼容磁盘说明原因,而根据已发布的存储限制,这些原因不外乎:The reasons are described for each incompatible disk of the VM and, based on published storage limits, can be any of the following:

  • 数据磁盘大小错误或 OS 磁盘大小错误。Wrong data disk size or wrong OS disk size. 查看支持限制。Review the support limits.

  • VM 总大小(复制 + TFO)超出系统支持的存储帐户大小限制 (35 TB)。Total VM size (replication + TFO) exceeds the supported storage-account size limit (35 TB). 当 VM 中的单个磁盘的性能特征超出系统支持的适用于标准存储的 Azure 或 Site Recovery 最大限制时,通常会表现出这种不兼容性。This incompatibility usually occurs when a single disk in the VM has a performance characteristic that exceeds the maximum supported Azure or Site Recovery limits for standard storage. 如果出现这种情况,则必须将 VM 置于高级存储区域。Such an instance pushes the VM into the premium storage zone. 但是,高级存储帐户支持的最大大小为 35 TB,并且无法跨多个存储帐户保护单个需要保护的 VM。However, the maximum supported size of a premium storage account is 35 TB, and a single protected VM cannot be protected across multiple storage accounts. 另请注意,在受保护 VM 上执行测试性故障转移时,该故障转移运行时所使用的存储帐户与进行复制时所使用的存储帐户相同。Also note that when a test failover is executed on a protected VM, it runs in the same storage account where replication is progressing. 在这种情况下,可以在设置时将磁盘大小加倍,既可进行复制,又可成功地进行测试性故障转移。In this instance, set up 2x the size of the disk for replication to progress and test failover to succeed in parallel.

  • 源 IOPS 超出了每个磁盘支持的存储 IOPS 限制,即 7500。Source IOPS exceeds supported storage IOPS limit of 7500 per disk.

  • 源 IOPS 超出了每个 VM 支持的存储 IOPS 限制,即 80,000。Source IOPS exceeds supported storage IOPS limit of 80,000 per VM.

  • 平均数据变动量超出了磁盘支持的 Site Recovery 数据变动量限制:平均 I/O 大小不能超过 20 MB/秒。Average data churn exceeds supported Site Recovery data churn limit of 20 MB/s for average I/O size for the disk.

  • VM 中所有磁盘的峰值数据变动量超出了每个 VM 支持的最大 Site Recovery 峰值数据变动量限制,即 54 MB/秒。Peak data churn across all disks on the VM exceeds the maximum supported Site Recovery peak data churn limit of 54 MB/s per VM.

  • 平均有效写入 IOPS 超出了磁盘支持的 Site Recovery IOPS 限制,即 840。Average effective write IOPS exceeds the supported Site Recovery IOPS limit of 840 for disk.

  • 计算出的快照存储超出了支持的快照存储限制,即 10 TB。Calculated snapshot storage exceeds the supported snapshot storage limit of 10 TB.

  • 每日总数据变动量超出了进程服务器支持的每日变动量限制,即 2 TB。Total data churn per day exceeds supported churn per day limit of 2 TB by a Process Server.

峰值读/写 IOPS (包括增长系数) :磁盘上的峰值工作负荷 IOPS(默认为第 95 百分位),包括将来的增长系数(默认为 30%)。Peak R/W IOPS (with Growth Factor): The peak workload IOPS on the disk (default is 95th percentile), including the future growth factor (default is 30 percent). 请注意,VM 的读/写 IOPS 总数并非总是该 VM 各个磁盘的读/写 IOPS 之和,因为在分析期间,该 VM 每分钟的读/写 IOPS 峰值是其各个磁盘的读/写 IOPS 之和的峰值。Note that the total read/write IOPS of the VM is not always the sum of the VM's individual disks' read/write IOPS, because the peak read/write IOPS of the VM is the peak of the sum of its individual disks' read/write IOPS during every minute of the profiling period.

以 Mbps 为单位的峰值数据变动量(包括增长系数) :磁盘上的峰值变动率(默认为第 95 百分位),包括将来的增长系数(默认为 30%)。Peak Data Churn in Mbps (with Growth Factor): The peak churn rate on the disk (default 95th percentile) including the future growth factor (default 30 percent). 请注意,VM 的总数据变动量并非总是 VM 各个磁盘的数据变动量之和,因为 VM 的峰值数据变动量是该 VM 在分析期间每分钟的各个磁盘变动量之和的峰值。Note that the total data churn of the VM is not always the sum of the VM's individual disks' data churn, because the peak data churn of the VM is the peak of the sum of its individual disks' churn during every minute of the profiling period.

磁盘数:VM 上的 VMDK 总数。Number of Disks: The total number of VMDKs on the VM.

磁盘大小(GB) :VM 所有磁盘的总安装大小。Disk size (GB): The total setup size of all disks of the VM. 该工具还会显示 VM 中各个磁盘的磁盘大小。The tool also shows the disk size for the individual disks in the VM.

核心数:VM 上的 CPU 核心数。Cores: The number of CPU cores on the VM.

内存(MB):VM 上的 RAM 量。Memory (MB): The amount of RAM on the VM.

NIC 数:VM 上的 NIC 数。NICs: The number of NICs on the VM.

启动类型:VM 的启动类型。Boot Type: Boot type of the VM. 它可以是 BIOS 或 EFI。It can be either BIOS or EFI. 目前,Azure Site Recovery 支持 Windows Server EFI VM(Windows Server 2012、2012 R2 和 2016),前提是启动盘中的分区数小于 4,引导扇区大小为 512 字节。Currently Azure Site Recovery supports Windows Server EFI VMs (Windows Server 2012, 2012 R2 and 2016) provided the number of partitions in the boot disk is less than 4 and boot sector size is 512 bytes. Azure Site Recovery 移动服务的版本最低必须为 9.13 才能保护 EFI VM。To protect EFI VMs, Azure Site Recovery mobility service version must be 9.13 or above. EFI VM 仅支持故障转移。Only failover is supported for EFI VMs. 不支持故障回复。Failback is not supported.

OS 类型:VM 的 OS 类型。OS Type: It is OS type of the VM. 可以是 Windows、Linux 或其他,具体取决于创建 VM 时从 VMware vSphere 中选择的模板。It can be either Windows or Linux or other based on the chosen template from VMware vSphere while creating the VM.

Azure Site Recovery 限制Azure Site Recovery limits

下表提供了 Azure Site Recovery 限制。The following table provides the Azure Site Recovery limits. 这些限制基于我们的测试,但无法涵盖所有可能的应用程序 I/O 组合。These limits are based on our tests, but they cannot cover all possible application I/O combinations. 实际结果可能因应用程序 I/O 组合而异。Actual results can vary based on your application I/O mix. 为获得最佳结果,我们始终建议通过测试性故障转移执行广泛的应用程序测试,获取应用程序的真实性能视图,即使在规划部署后,也应如此。For best results, even after deployment planning, we always recommend that you perform extensive application testing by issuing a test failover to get the true performance picture of the application.

复限制复制存储目标Replication storage 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 分钟的积压工作。The preceding 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.

成本估算Cost estimation

详细了解成本估算Learn more about cost estimation.

后续步骤Next steps

详细了解成本估算Learn more about cost estimation.