您现在访问的是微软AZURE全球版技术文档网站,若需要访问由世纪互联运营的MICROSOFT AZURE中国区技术文档网站,请访问 https://docs.azure.cn.

为 VMware 灾难恢复运行部署规划器Run the Deployment Planner for VMware disaster recovery

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

运行部署规划器的模式Modes of running deployment planner

可使用以下三种模式之一运行该命令行工具 (ASRDeploymentPlanner.exe):You can run the command-line tool (ASRDeploymentPlanner.exe) in any of the following three modes:

  1. 分析Profiling
  2. 报表生成Report generation
  3. 获取吞吐量Get throughput

首先,请以分析模式运行该工具,收集 VM 数据变动量和 IOPS。First, run the tool in profiling mode to gather VM data churn and IOPS. 接下来,运行该工具以生成报表,确定网络带宽、存储要求和 DR 成本。Next, run the tool to generate the report to find the network bandwidth, storage requirements and DR cost.

分析 VMware VMProfile VMware VMs

在分析模式下,Deployment Planner 工具将连接到 vCenter 服务器/vSphere ESXi 主机,以便收集有关 VM 的性能数据。In profiling mode, the deployment planner tool connects to the vCenter server/vSphere ESXi host to collect performance data about the VM.

  • 分析不会影响生产 VM 的性能,因为不会与其进行直接连接。Profiling does not affect the performance of the production VMs, because no direct connection is made to them. 所有性能数据是从 vCenter 服务器/vSphere ESXi 主机收集的。All performance data is collected from the vCenter server/vSphere ESXi host.
  • 为了确保分析对服务器造成的影响可忽略不计,该工具每隔 15 分钟对 vCenter 服务器/vSphere ESXi 主机查询一次。To ensure that there is a negligible impact on the server because of profiling, the tool queries the vCenter server/vSphere ESXi host once every 15 minutes. 该查询时间间隔不会降低分析的准确性,因为该工具会存储每一分钟的性能计数器数据。This query interval does not compromise profiling accuracy, because the tool stores every minute’s performance counter data.

创建要分析的 VM 的列表Create a list of VMs to profile

首先,需要一个要分析的 VM 的列表。First, you need a list of the VMs to be profiled. 可以使用以下过程中的 VMware vSphere PowerCLI 命令获取 vCenter 服务器/vSphere ESXi 主机上的 VM 的所有名称。You can get all the names of VMs on a vCenter server/vSphere ESXi host by using the VMware vSphere PowerCLI commands in the following procedure. 也可以在文件中列出要手动分析的 VM 的友好名称或 IP 地址。Alternatively, you can list in a file the friendly names or IP addresses of the VMs that you want to profile manually.

  1. 登录到在其中安装了 VMware vSphere PowerCLI 的 VM。Sign in to the VM that VMware vSphere PowerCLI is installed in.

  2. 打开 VMware vSphere PowerCLI 控制台。Open the VMware vSphere PowerCLI console.

  3. 确保启用脚本的执行策略。Ensure that the execution policy is enabled for the script. 如果已禁用,请以管理员模式启动 VMware vSphere PowerCLI 控制台,并运行以下命令将它启用:If it is disabled, launch the VMware vSphere PowerCLI console in administrator mode, and then enable it by running the following command:

         Set-ExecutionPolicy –ExecutionPolicy AllSigned
    
  4. 如果系统不将 Connect-VIServer 视为 cmdlet 的名称,则可能需要运行以下命令。You may optionally need to run the following command if Connect-VIServer is not recognized as the name of cmdlet.

         Add-PSSnapin VMware.VimAutomation.Core
    
  5. 要获取在 vCenter 服务器/vSphere ESXi 主机上的 VM 的所有名称并将列表存储在 .txt 文件中,请运行下面列出的两个命令。To get all the names of VMs on a vCenter server/vSphere ESXi host and store the list in a .txt file, run the two commands listed here. 将 ‹server name›、‹user name›、‹password› 和 ‹outputfile.txt› 替换为输入。Replace ‹server name›, ‹user name›, ‹password›, ‹outputfile.txt›; with your inputs.

         Connect-VIServer -Server <server name> -User <user name> -Password <password>
    
         Get-VM |  Select Name | Sort-Object -Property Name >  <outputfile.txt>
    
  6. 在记事本中打开输出文件,然后将要分析的所有 VM 的名称复制到另一文件(例如 ProfileVMList.txt)中,每行一个 VM 名称。Open the output file in Notepad, and then copy the names of all VMs that you want to profile to another file (for example, ProfileVMList.txt), one VM name per line. 此文件将用作命令行工具的 -VMListFile 参数的输入。This file is used as input to the -VMListFile parameter of the command-line tool.

    Deployment Planner 中的 VM 名称列表VM name list in the deployment planner

开始分析Start profiling

创建要分析的 VM 的列表后,可在分析模式下运行该工具。After you have the list of VMs to be profiled, you can run the tool in profiling mode. 下面是在分析模式下运行该工具所要提供的必需和可选参数列表。Here is the list of mandatory and optional parameters of the tool to run in profiling mode.

ASRDeploymentPlanner.exe -Operation StartProfiling /?
参数名称Parameter name 说明Description
-Operation-Operation StartProfilingStartProfiling
-Server-Server 要分析其 VM 的 vCenter 服务器/vSphere ESXi 主机的完全限定域名或 IP 地址。The fully qualified domain name or IP address of the vCenter server/vSphere ESXi host whose VMs are to be profiled.
-User-User 用于连接到 vCenter 服务器/vSphere ESXi 主机的用户名。The user name to connect to the vCenter server/vSphere ESXi host. 该用户至少需要拥有只读访问权限。The user needs to have read-only access, at minimum.
-VMListFile-VMListFile 一个文件,其中包含要分析的 VM 的列表。The file that contains the list of VMs to be profiled. 文件路径可以是绝对或相对路径。The file path can be absolute or relative. 此文件应该每行包含一个 VM 名称/IP 地址。The file should contain one VM name/IP address per line. 此文件中指定的虚拟机名称应与 vCenter 服务器/vSphere ESXi 主机上的 VM 名称相同。Virtual machine name specified in the file should be the same as the VM name on the vCenter server/vSphere ESXi host.
例如,VMList.txt 文件包含以下 VM:For example, the file VMList.txt contains the following VMs:
  • virtual_machine_Avirtual_machine_A
  • 10.150.29.11010.150.29.110
  • virtual_machine_Bvirtual_machine_B
    -NoOfMinutesToProfile-NoOfMinutesToProfile 运行分析的分钟数。The number of minutes for which profiling is to be run. 最小值为 30 分钟。Minimum is 30 minutes.
    -NoOfHoursToProfile-NoOfHoursToProfile 运行分析的小时数。The number of hours for which profiling is to be run.
    -NoOfDaysToProfile-NoOfDaysToProfile 运行分析的天数。The number of days for which profiling is to be run. 建议运行分析 7 天以上,确保在指定时间段内观察环境中的工作负荷模式,并根据该模式提供准确的建议。We recommend that you run profiling for more than 7 days to ensure that the workload pattern in your environment over the specified period is observed and used to provide an accurate recommendation.
    -Virtualization-Virtualization 指定虚拟化类型(VMware 或 Hyper-V)。Specify the virtualization type (VMware or Hyper-V).
    -Directory-Directory (可选)通用命名约定 (UNC) 或本地目录路径,用于存储在分析期间生成的分析数据。(Optional) The universal naming convention (UNC) or local directory path to store profiling data generated during profiling. 如果未指定目录名称,则使用当前路径下名为“ProfiledData”的目录作为默认目录。If a directory name is not given, the directory named ‘ProfiledData’ under the current path will be used as the default directory.
    -Password-Password (可选)用于连接到 vCenter 服务器/vSphere ESXi 主机的密码。(Optional) The password to use to connect to the vCenter server/vSphere ESXi host. 如果现在不指定密码,则在执行命令时,系统会提示指定密码。If you do not specify one now, you will be prompted for it when the command is executed.
    -Port-Port (可选)用于连接到 vCenter/ESXi 主机的端口号。(Optional) Port number to connect to vCenter/ESXi host. 默认端口为 443。Default port is 443.
    -Protocol-Protocol (可选)用于连接到 vCenter 的指定协议,即“http”或“https”。(Optional) Specified the protocol either ‘http’ or ‘https’ to connect to vCenter. 默认协议为 https。Default protocol is https.
    -StorageAccountName-StorageAccountName (可选)存储帐户名称,用于确定在将数据从本地复制到 Azure 时可实现的吞吐量。(Optional) The storage-account name that's used to find the throughput achievable for replication of data from on-premises to Azure. 该工具会将测试数据上传到此存储帐户来计算吞吐量。The tool uploads test data to this storage account to calculate throughput. 存储帐户必须是常规用途 v1 (GPv1) 类型。The storage account must be General-purpose v1 (GPv1) type.
    -StorageAccountKey-StorageAccountKey (可选)用于访问存储帐户的存储帐户密钥。(Optional) The storage-account key that's used to access the storage account. 转到 Azure 门户 >“存储帐户”> <存储帐户名称> >“设置”>“访问密钥”> 密钥 1。Go to the Azure portal > Storage accounts > <Storage account name> > Settings > Access Keys > Key1.
    -Environment-Environment (可选)这是目标 Azure 存储帐户环境。(optional) This is your target Azure Storage account environment. 此项可能采用下述三个值之一:AzureCloud、AzureUSGovernment、AzureChinaCloud。This can be one of three values - AzureCloud,AzureUSGovernment, AzureChinaCloud. 默认值为 AzureCloud。Default is AzureCloud. 当目标 Azure 区域为 Azure 美国政府或 Azure 中国世纪互联时,请使用此参数。Use the parameter when your target Azure region is either Azure US Government or Azure China 21Vianet.

    建议在分析 VM 时,分析 7 天以上。We recommend that you profile your VMs for more than 7 days. 如果变动量模式在某个月发生变化,建议在看到最大变动量的一周内进行分析。If churn pattern varies in a month, we recommend to profile during the week when you see the maximum churn. 最好的方式是分析 31 天,以便获取更好的建议。The best way is to profile for 31 days to get better recommendation. 在分析过程中,ASRDeploymentPlanner.exe 将保持运行。During the profiling period, ASRDeploymentPlanner.exe keeps running. 该工具将取以天为单位的分析时间输入。The tool takes profiling time input in days. 若要快速测试此工具或获取概念证明,可以分析数小时或数分钟。For a quick test of the tool or for proof of concept you can profile for few hours or minutes. 允许的最短分析时间为 30 分钟。The minimum allowed profiling time is 30 minutes.

    在分析期间,可以选择性地传递存储帐户名称和密钥,确定在从配置服务器或进程服务器复制到 Azure 时,Site Recovery 可实现的吞吐量。During profiling, you can optionally pass a storage-account name and key to find the throughput that Site Recovery can achieve at the time of replication from the configuration server or process server to Azure. 如果在分析期间不传递存储帐户名称和密钥,该工具不会计算可实现的吞吐量。If the storage-account name and key are not passed during profiling, the tool does not calculate achievable throughput.

    可以针对各个 VM 集运行该工具的多个实例。You can run multiple instances of the tool for various sets of VMs. 确保不要在任何分析集中重复使用 VM 名称。Ensure that the VM names are not repeated in any of the profiling sets. 例如,如果已分析 10 个 VM(VM1 到 VM10),过几天后又想要分析另外 5 个 VM(VM11 到 VM15),则可通过另一个命令行控制台针对第二组 VM(VM11 到 VM15)运行该工具。For example, if you have profiled ten VMs (VM1 through VM10) and after few days you want to profile another five VMs (VM11 through VM15), you can run the tool from another command-line console for the second set of VMs (VM11 through VM15). 请确保第二组 VM 不包含第一个分析实例中的任何 VM 名称,或请确保为第二次运行使用不同的输出目录。Ensure that the second set of VMs do not have any VM names from the first profiling instance or you use a different output directory for the second run. 如果使用该工具的两个实例分析相同的 VM 并使用相同的输出目录,生成的报告不准确。If two instances of the tool are used for profiling the same VMs and use the same output directory, the generated report will be incorrect.

    默认情况下,此工具配置为在分析后为最多 1000 个 VM 生成报告。By default, the tool is configured to profile and generate report up to 1000 VMs. 若要更改限制,可以更改 ASRDeploymentPlanner.exe.config 文件中的 MaxVMsSupported 项值。You can change limit by changing MaxVMsSupported key value in ASRDeploymentPlanner.exe.config file.

    <!-- Maximum number of vms supported-->
    <add key="MaxVmsSupported" value="1000"/>
    

    使用默认设置时,若要分析特定数量的 VM(例如 1500 个 VM),请创建两个 VMList.txt 文件。With the default settings, to profile say 1500 VMs, create two VMList.txt files. 一个包含 1000 个 VM,另一个是 500 个 VM 的列表。One with 1000 VMs and other with 500 VM list. 运行 Azure Site Recovery 部署规划器的这两个实例:一个使用 VMList1.txt,另一个使用 VMList2.txt。Run the two instances of Azure Site Recovery Deployment Planner, one with VMList1.txt and other with VMList2.txt. 可以使用同一目录路径来存储两个 VMList VM 的已分析数据。You can use the same directory path to store the profiled data of both the VMList VMs.

    我们已经看到,根据硬件配置(尤其是在其中运行报表生成工具的服务器的 RAM 大小),在内存不足的情况下,操作可能会失败。We have seen that based on the hardware configuration especially RAM size of the server from where the tool is run to generate the report, the operation may fail with insufficient memory. 如果硬件良好,可将 MaxVMsSupported 更改为更高的值。If you have good hardware, you can change the MaxVMsSupported any higher value.

    如果有多个 vCenter 服务器,需为每个 vCenter 服务器运行一个 ASRDeploymentPlanner 实例,以便进行分析。If you have multiple vCenter servers, you need to run one instance of ASRDeploymentPlanner for each vCenter server for profiling.

    VM 配置会在分析操作开始时捕获一次,存储在名为 VMDetailList.xml 的文件中。VM configurations are captured once at the beginning of the profiling operation and stored in a file called VMDetailList.xml. 生成报告时会使用此信息。This information is used when the report is generated. 从分析开始到结束都不捕获 VM 配置中发生的任何更改(例如,核心、磁盘或 NIC 数增加)。Any change in VM configuration (for example, an increased number of cores, disks, or NICs) from the beginning to the end of profiling is not captured. 如果分析的 VM 配置在分析过程中发生了更改,则可在公共预览版中通过下述解决方法在生成报告时获取最新的 VM 详细信息:If a profiled VM configuration has changed during the course of profiling, in the public preview, here is the workaround to get latest VM details when generating the report:

    • 备份 VMdetailList.xml 文件,并将其从当前位置删除。Back up VMdetailList.xml, and delete the file from its current location.
    • 生成报告时传递 -User 和 -Password 参数。Pass -User and -Password arguments at the time of report generation.

    该分析命令在分析目录中生成多个文件。The profiling command generates several files in the profiling directory. 请勿删除任何文件,因为这样做会影响报告生成。Do not delete any of the files, because doing so affects report generation.

    示例 1:分析 VM 30 天,确定从本地到 Azure 的吞吐量Example 1: Profile VMs for 30 days, and find the throughput from on-premises to Azure

    ASRDeploymentPlanner.exe -Operation StartProfiling -Virtualization VMware -Directory “E:\vCenter1_ProfiledData” -Server vCenter1.contoso.com -VMListFile “E:\vCenter1_ProfiledData\ProfileVMList1.txt”  -NoOfDaysToProfile  30  -User vCenterUser1 -StorageAccountName  asrspfarm1 -StorageAccountKey Eby8vdM02xNOcqFlqUwJPLlmEtlCDXJ1OUzFT50uSRZ6IFsuFq2UVErCz4I6tq/K1SZFPTOtr/KBHBeksoGMGw==
    

    示例 2:分析 VM 15 天Example 2: Profile VMs for 15 days

    ASRDeploymentPlanner.exe -Operation StartProfiling -Virtualization VMware -Directory “E:\vCenter1_ProfiledData” -Server vCenter1.contoso.com -VMListFile “E:\vCenter1_ProfiledData\ProfileVMList1.txt” -NoOfDaysToProfile  15  -User vCenterUser1
    

    示例 3:分析 VM 60 分钟以快速测试工具Example 3: Profile VMs for 60 minutes for a quick test of the tool

    ASRDeploymentPlanner.exe -Operation StartProfiling -Virtualization VMware -Directory “E:\vCenter1_ProfiledData” -Server vCenter1.contoso.com -VMListFile “E:\vCenter1_ProfiledData\ProfileVMList1.txt”  -NoOfMinutesToProfile 60  -User vCenterUser1
    

    示例 4:分析 VM 2 小时以获取概念证明Example 4: Profile VMs for 2 hours for a proof of concept

    ASRDeploymentPlanner.exe -Operation StartProfiling -Virtualization VMware -Directory “E:\vCenter1_ProfiledData” -Server vCenter1.contoso.com -VMListFile “E:\vCenter1_ProfiledData\ProfileVMList1.txt” -NoOfHoursToProfile 2 -User vCenterUser1
    

    备注

    • 如果运行该工具的服务器重启或崩溃,或者使用 Ctrl + C 关闭该工具,系统会保存分析数据。If the server that the tool is running on is rebooted or has crashed, or if you close the tool by using Ctrl + C, the profiled data is preserved. 但是,过去 15 分钟的分析数据可能会丢失。However, there is a chance of missing the last 15 minutes of profiled data. 在这种情况下,请在服务器重新启动后以分析模式重新运行该工具。In such an instance, rerun the tool in profiling mode after the server restarts.
    • 如果传递了存储帐户名称和密钥,该工具会在执行最后一个分析步骤时测量吞吐量。When the storage-account name and key are passed, the tool measures the throughput at the last step of profiling. 如果在分析完成之前关闭该工具,则不会计算吞吐量。If the tool is closed before profiling is completed, the throughput is not calculated. 若要在生成报告之前确定吞吐量,可通过命令行控制台运行 GetThroughput 操作。To find the throughput before generating the report, you can run the GetThroughput operation from the command-line console. 否则,生成的报告将不包含吞吐量信息。Otherwise, the generated report will not contain the throughput information.

    生成报告Generate report

    该工具生成一个启用了宏的 Microsoft Excel 文件(XLSM 文件)作为报告输出,对所有部署建议进行了汇总。The tool generates a macro-enabled Microsoft Excel file (XLSM file) as the report output, which summarizes all the deployment recommendations. 该报告名为 DeploymentPlannerReport_<unique numeric identifier>.xlsm,置于指定目录中。The report is named DeploymentPlannerReport_<unique numeric identifier>.xlsm and placed in the specified directory.

    备注

    生成报告需要安装了 Excel 2013 或更高版本的 Windows 电脑或 Windows Server。The report generation requires a Windows PC or Windows Server with Excel 2013 or later. 此计算机上的小数点符号应配置为“.”以生成成本估算。The decimal symbol on this machine should be configured as "." to produce the cost estimates. 如果已设置了“,”作为小数点符号,请转到“控制面板”中的“更改日期、时间或数字格式”,然后转到“其他设置”将小数点符号更改为“.”。In case you have setup "," as decimal symbol, please go to "Change date, time or number formats" in Control Panel and go to "Additional Settings" to change the decimal symbol to ".".

    完成分析后,可在报告生成模式下运行该工具。After profiling is complete, you can run the tool in report-generation mode. 下表包含一系列必需的和可选的工具参数,适用于在报告生成模式下 运行。The following table contains a list of mandatory and optional tool parameters to run in report-generation mode.

    ASRDeploymentPlanner.exe -Operation GenerateReport /?

    参数名称Parameter name 说明Description
    -Operation-Operation GenerateReportGenerateReport
    -Server-Server vCenter/vSphere 服务器完全限定域名或 IP 地址(使用的名称或 IP 地址与分析时使用的相同),其中包含需要生成其报告的已分析 VM。The vCenter/vSphere server fully qualified domain name or IP address (use the same name or IP address that you used at the time of profiling) where the profiled VMs whose report is to be generated are located. 请注意,如果在分析时使用了 vCenter 服务器,则不能使用 vSphere 服务器来生成报告,反之亦然。Note that if you used a vCenter server at the time of profiling, you cannot use a vSphere server for report generation, and vice-versa.
    -VMListFile-VMListFile 一个文件,其中包含一系列需为其生成报告的已分析 VM。The file that contains the list of profiled VMs that the report is to be generated for. 文件路径可以是绝对或相对路径。The file path can be absolute or relative. 此文件应该每行包含一个 VM 名称或 IP 地址。The file should contain one VM name or IP address per line. 此文件中指定的 VM 名称应与 vCenter 服务器/vSphere ESXi 主机上的 VM 名称相同,并与分析时使用的名称匹配。The VM names that are specified in the file should be the same as the VM names on the vCenter server/vSphere ESXi host, and match what was used during profiling.
    -Virtualization-Virtualization 指定虚拟化类型(VMware 或 Hyper-V)。Specify the virtualization type (VMware or Hyper-V).
    -Directory-Directory (可选)UNC 或本地目录路径,其中存储了分析数据(在分析期间生成的文件)。(Optional) The UNC or local directory path where the profiled data (files generated during profiling) is stored. 需要使用此数据来生成报告。This data is required for generating the report. 如果未指定名称,将使用“ProfiledData”目录。If a name isn't specified, ‘ProfiledData’ directory will be used.
    -GoalToCompleteIR-GoalToCompleteIR (可选)小时数,需在此时间段内完成已分析 VM 的初始复制。(Optional) The number of hours in which the initial replication of the profiled VMs needs to be completed. 生成的报告将提供可在指定时间内完成初始复制的 VM 数。The generated report provides the number of VMs for which initial replication can be completed in the specified time. 默认值为 72 小时。The default is 72 hours.
    -User-User (可选)用于连接到 vCenter/vSphere 服务器的用户名。(Optional) The user name to use to connect to the vCenter/vSphere server. 此名称用于获取要在报告中使用的最新 VM 配置信息,例如磁盘数、核心数、NIC 数。The name is used to fetch the latest configuration information of the VMs, such as the number of disks, number of cores, and number of NICs, to use in the report. 如果未提供此名称,将使用开始分析时收集的配置信息。If the name isn't provided, the configuration information collected at the beginning of the profiling kickoff is used.
    -Password-Password (可选)用于连接到 vCenter 服务器/vSphere ESXi 主机的密码。(Optional) The password to use to connect to the vCenter server/vSphere ESXi host. 如果密码未作为参数指定,则稍后在执行命令时,系统会提示指定。If the password isn't specified as a parameter, you will be prompted for it later when the command is executed.
    -Port-Port (可选)用于连接到 vCenter/ESXi 主机的端口号。(Optional) Port number to connect to vCenter/ESXi host. 默认端口为 443。Default port is 443.
    -Protocol-Protocol (可选)用于连接到 vCenter 的指定协议,即“http”或“https”。(Optional) Specified the protocol either ‘http’ or ‘https’ to connect to vCenter. 默认协议为 https。Default protocol is https.
    -DesiredRPO-DesiredRPO (可选)以分钟为单位的所需恢复点目标。(Optional) The desired recovery point objective, in minutes. 默认值为 15 分钟。The default is 15 minutes.
    -Bandwidth-Bandwidth 以 Mbps 为单位的带宽。Bandwidth in Mbps. 一个参数,用于计算指定的带宽可实现的 RPO。The parameter to use to calculate the RPO that can be achieved for the specified bandwidth.
    -StartDate-StartDate (可选)采用 MM-DD-YYYY:HH:MM 格式(24 小时制)的开始日期和时间。(Optional) The start date and time in MM-DD-YYYY:HH:MM (24-hour format). “StartDate”必须与“EndDate”一起指定。StartDate must be specified along with EndDate. 如果指定 StartDate,会根据从 StartDate 到 EndDate 收集的分析数据生成报告。When StartDate is specified, the report is generated for the profiled data that's collected between StartDate and EndDate.
    -EndDate-EndDate (可选)采用 MM-DD-YYYY:HH:MM 格式(24 小时制)的结束日期和时间。(Optional) The end date and time in MM-DD-YYYY:HH:MM (24-hour format). “EndDate”必须与“StartDate”一起指定。EndDate must be specified along with StartDate. 如果指定 EndDate,会根据从 StartDate 到 EndDate 收集的分析数据生成报告。When EndDate is specified, the report is generated for the profiled data that's collected between StartDate and EndDate.
    -GrowthFactor-GrowthFactor (可选)增长系数,以百分比表示。(Optional) The growth factor, expressed as a percentage. 默认值为 30%。The default is 30 percent.
    -UseManagedDisks-UseManagedDisks (可选)UseManagedDisks - 是/否。(Optional) UseManagedDisks - Yes/No. 默认值为“是”。Default is Yes. 计算可放置到单个存储帐户中的虚拟机数量时要考虑到:对虚拟机进行的故障转移/测试性故障转移是在托管磁盘而不是非托管磁盘上完成的。The number of virtual machines that can be placed into a single storage account is calculated considering whether Failover/Test failover of virtual machines is done on managed disk instead of unmanaged disk.
    -SubscriptionId-SubscriptionId (可选)订阅 GUID。(Optional) The subscription GUID. 请注意,当你需要根据订阅、与订阅相关联的套餐使用“指定的货币”中的特定目标 Azure 区域的最新价格生成成本估算报告时,此参数是必需的。Note that this parameter is required when you need to generate the cost estimation report with the latest price based on your subscription, the offer that is associated with your subscription and for your specific target Azure region in the specified currency.
    -TargetRegion-TargetRegion (可选)充当复制目标的 Azure 区域。(Optional) The Azure region where replication is targeted. 由于 Azure 的成本因区域而异,因此可使用此参数来生成特定目标 Azure 区域的报表。Since Azure has different costs per region, to generate report with specific target Azure region use this parameter.
    默认值为 WestUS2 或上次使用的目标区域。Default is WestUS2 or the last used target region.
    请参阅支持的目标区域的列表。Refer to the list of supported target regions.
    -OfferId-OfferId (可选)与给定订阅关联的套餐。(Optional) The offer associated with the give subscription. 默认值为 MS-AZR-0003P(即用即付)。Default is MS-AZR-0003P (Pay-As-You-Go).
    -Currency-Currency (可选)在生成的报表中显示的成本所采用的货币。(Optional) The currency in which cost is shown in the generated report. 默认为美元 ($) 或上次使用的货币。Default is US Dollar ($) or the last used currency.
    请参阅支持的货币的列表。Refer to the list of supported currencies.

    默认情况下,此工具配置为在分析后为最多 1000 个 VM 生成报告。By default, the tool is configured to profile and generate report up to 1000 VMs. 若要更改限制,可以更改 ASRDeploymentPlanner.exe.config 文件中的 MaxVMsSupported 项值。You can change limit by changing MaxVMsSupported key value in ASRDeploymentPlanner.exe.config file.

    <!-- Maximum number of vms supported-->
    <add key="MaxVmsSupported" value="1000"/>
    

    示例 1:当分析数据位于本地驱动器上时,使用默认值生成报告Example 1: Generate a report with default values when the profiled data is on the local drive

    ASRDeploymentPlanner.exe -Operation GenerateReport -Virtualization VMware -Server vCenter1.contoso.com -Directory “E:\vCenter1_ProfiledData” -VMListFile “E:\vCenter1_ProfiledData\ProfileVMList1.txt”
    

    示例 2:当分析数据位于远程服务器上时生成报告Example 2: Generate a report when the profiled data is on a remote server

    应该对远程目录拥有读/写访问权限。You should have read/write access on the remote directory.

    ASRDeploymentPlanner.exe -Operation GenerateReport -Virtualization VMware -Server vCenter1.contoso.com -Directory “\\PS1-W2K12R2\vCenter1_ProfiledData” -VMListFile “\\PS1-W2K12R2\vCenter1_ProfiledData\ProfileVMList1.txt”
    

    示例 3:生成一个报告,列出指定的带宽,以及在指定时间内完成 IR 的目标Example 3: Generate a report with a specific bandwidth and goal to complete IR within specified time

    ASRDeploymentPlanner.exe -Operation GenerateReport -Virtualization VMware -Server vCenter1.contoso.com -Directory “E:\vCenter1_ProfiledData” -VMListFile “E:\vCenter1_ProfiledData\ProfileVMList1.txt” -Bandwidth 100 -GoalToCompleteIR 24
    

    示例 4:使用 5% 的增长系数而不是默认值 30% 来生成报告Example 4: Generate a report with a 5 percent growth factor instead of the default 30 percent

    ASRDeploymentPlanner.exe -Operation GenerateReport -Virtualization VMware -Server vCenter1.contoso.com -Directory “E:\vCenter1_ProfiledData” -VMListFile “E:\vCenter1_ProfiledData\ProfileVMList1.txt” -GrowthFactor 5
    

    示例 5:使用分析数据的子集生成报告Example 5: Generate a report with a subset of profiled data

    例如,有 30 天的分析数据,但只想生成 20 天的报告。For example, you have 30 days of profiled data and want to generate a report for only 20 days.

    ASRDeploymentPlanner.exe -Operation GenerateReport -Virtualization VMware -Server vCenter1.contoso.com -Directory “E:\vCenter1_ProfiledData” -VMListFile “E:\vCenter1_ProfiledData\ProfileVMList1.txt” -StartDate  01-10-2017:12:30 -EndDate 01-19-2017:12:30
    

    示例 6:生成 5 分钟 RPO 报告Example 6: Generate a report for 5-minute RPO

    ASRDeploymentPlanner.exe -Operation GenerateReport -Virtualization VMware -Server vCenter1.contoso.com -Directory “E:\vCenter1_ProfiledData” -VMListFile “E:\vCenter1_ProfiledData\ProfileVMList1.txt”  -DesiredRPO 5
    

    示例 7:使用印度卢比和特定的产品/服务 ID,生成一个针对“印度南部”Azure区域的报表Example 7: Generate a report for South India Azure region with Indian Rupee and specific offer ID

    请注意,订阅 ID 是生成特定货币的成本报告所必需的。Note that the subscription ID is required to generate cost report in a specific currency.

    ASRDeploymentPlanner.exe -Operation GenerateReport -Virtualization VMware  -Directory “E:\vCenter1_ProfiledData” -VMListFile “E:\vCenter1_ProfiledData\ProfileVMList1.txt”  -SubscriptionID 4d19f16b-3e00-4b89-a2ba-8645edf42fe5 -OfferID MS-AZR-0148P -TargetRegion southindia -Currency INR
    

    用于计算的百分位值Percentile value used for the calculation

    在生成报告时,该工具使用分析期间收集的性能指标的哪个默认百分位值?What default percentile value of the performance metrics collected during profiling does the tool use when it generates a report?

    该工具默认使用分析所有 VM 期间收集的读/写 IOPS、写入 IOPS 和数据变动量的第 95 百分位值。The tool defaults to the 95th percentile values of read/write IOPS, write IOPS, and data churn that are collected during profiling of all the VMs. 此指标可确保系统不使用第 100 百分位峰值(在发生临时事件时,可能会出现在 VM 中)来确定目标存储帐户和源带宽需求。This metric ensures that the 100th percentile spike your VMs might see because of temporary events is not used to determine your target storage-account and source-bandwidth requirements. 例如,临时事件可能是一天运行一次的备份作业、定期发生的数据库索引编制或分析报告生成活动,或者其他类似的短期时间点事件。For example, a temporary event might be a backup job running once a day, a periodic database indexing or analytics report-generation activity, or other similar short-lived, point-in-time events.

    使用第 95 百分位值可以反映真实的工作负荷特征,使这些工作负荷在 Azure 中运行时提供最佳性能。Using 95th percentile values gives a true picture of real workload characteristics, and it gives you the best performance when the workloads are running on Azure. 我们预计不需要更改此数字。We do not anticipate that you would need to change this number. 如果更改此值(例如更改为第 90 百分位),则可在默认文件夹中更新并保存配置文件“ASRDeploymentPlanner.exe.config”,针对现有的分析数据生成新报告。If you do change the value (to the 90th percentile, for example), you can update the configuration file ASRDeploymentPlanner.exe.config in the default folder and save it to generate a new report on the existing profiled data.

    <add key="WriteIOPSPercentile" value="95" />      
    <add key="ReadWriteIOPSPercentile" value="95" />      
    <add key="DataChurnPercentile" value="95" />
    

    增长系数考虑因素Growth-factor considerations

    为何在对部署进行计划时应考虑增长系数?Why should I consider growth factor when I plan deployments?

    假设使用量在一段时间内可能会增多,则考虑工作负荷特征的增长就至关重要。It is critical to account for growth in your workload characteristics, assuming a potential increase in usage over time. 在保护就位以后,如果工作负荷特征发生更改,则除非先禁用保护,再重新启用保护,否则在切换到其他存储帐户后将无法获得保护。After protection is in place, if your workload characteristics change, you cannot switch to a different storage account for protection without disabling and re-enabling the protection.

    例如,假设你目前的 VM 适合标准存储复制帐户。For example, let's say that today your VM fits in a standard storage replication account. 在随后的三个月中,可能会发生多项变化:Over the next three months, several changes are likely to occur:

    • 在 VM 上运行的应用程序的用户数会增加。The number of users of the application that runs on the VM will increase.
    • 该 VM 上的变动量随之会增加,因此需使用高级存储,使 Site Recovery 复制能够跟上节奏。The resulting increased churn on the VM will require the VM to go to premium storage so that Site Recovery replication can keep pace.
    • 结果就是,需要先禁用对高级存储帐户的保护,再重新启用该保护。Consequently, you will have to disable and re-enable protection to a premium storage account.

    强烈建议在部署计划期间以及在默认值为 30% 的时候对增长进行计划。We strongly recommend that you plan for growth during deployment planning and while the default value is 30 percent. 对自己的应用程序使用模式和增长预测了解得最充分,生成报告时可以相应地更改此数字。You are the expert on your application usage pattern and growth projections, and you can change this number accordingly while generating a report. 另外,可以使用相同的分析数据根据各种增长系数生成多份报告,确定哪些目标存储和源带宽建议最适合自己。Moreover, you can generate multiple reports with various growth factors with the same profiled data and determine what target storage and source bandwidth recommendations work best for you.

    生成的 Microsoft Excel 报告包含以下信息:The generated Microsoft Excel report contains the following information:

    Deployment Planner

    获取吞吐量Get throughput

    若要估算从本地复制到 Azure 期间 Site Recovery 可实现的吞吐量,请在 GetThroughput 模式下运行该工具。To estimate the throughput that Site Recovery can achieve from on-premises to Azure during replication, run the tool in GetThroughput mode. 该工具计算的吞吐量源自运行该工具的服务器。The tool calculates the throughput from the server that the tool is running on. 理想情况下,该服务器的配置遵循配置服务器大小调整指南。Ideally, this server is based on the configuration server sizing guide. 如果已在本地部署 Site Recovery 基础结构组件,请在配置服务器上运行该工具。If you have already deployed Site Recovery infrastructure components on-premises, run the tool on the configuration server.

    打开命令行控制台,转到 Site Recovery 部署规划工具文件夹。Open a command-line console, and go to the Site Recovery deployment planning tool folder. 结合以下参数运行 ASRDeploymentPlanner.exe。Run ASRDeploymentPlanner.exe with following parameters.

    ASRDeploymentPlanner.exe -Operation GetThroughput /?

    参数名称Parameter name 说明Description
    -Operation-Operation GetThroughputGetThroughput
    -Virtualization-Virtualization 指定虚拟化类型(VMware 或 Hyper-V)。Specify the virtualization type (VMware or Hyper-V).
    -Directory-Directory (可选)UNC 或本地目录路径,其中存储了分析数据(在分析期间生成的文件)。(Optional) The UNC or local directory path where the profiled data (files generated during profiling) is stored. 需要使用此数据来生成报告。This data is required for generating the report. 如果未指定目录名称,请使用“ProfiledData”目录。If a directory name is not specified, ‘ProfiledData’ directory is used.
    -StorageAccountName-StorageAccountName 存储帐户名称,用于确定在将数据从本地复制到 Azure 时消耗的带宽。The storage-account name that's used to find the bandwidth consumed for replication of data from on-premises to Azure. 该工具会将测试数据上传到此存储帐户来确定消耗的带宽。The tool uploads test data to this storage account to find the bandwidth consumed. 存储帐户必须是常规用途 v1 (GPv1) 类型。The storage account must be either General-purpose v1 (GPv1) type.
    -StorageAccountKey-StorageAccountKey 用于访问存储帐户的存储帐户密钥。The storage-account key that's used to access the storage account. 转到 Azure 门户 >“存储帐户”> <存储帐户名称> >“设置”>“访问密钥”> 密钥 1(或经典存储帐户的主访问密钥)。Go to the Azure portal > Storage accounts > <Storage account name> > Settings > Access Keys > Key1 (or a primary access key for a classic storage account).
    -VMListFile-VMListFile 一个文件,其中包含一系列可以通过分析来计算所消耗带宽的 VM。The file that contains the list of VMs to be profiled for calculating the bandwidth consumed. 文件路径可以是绝对或相对路径。The file path can be absolute or relative. 此文件应该每行包含一个 VM 名称/IP 地址。The file should contain one VM name/IP address per line. 此文件中指定的 VM 名称应与 vCenter 服务器/vSphere ESXi 主机上的 VM 名称相同。The VM names specified in the file should be the same as the VM names on the vCenter server/vSphere ESXi host.
    例如,VMList.txt 文件包含以下 VM:For example, the file VMList.txt contains the following VMs:
    • VM_AVM_A
    • 10.150.29.11010.150.29.110
    • VM_BVM_B
    -Environment-Environment (可选)这是目标 Azure 存储帐户环境。(optional) This is your target Azure Storage account environment. 此项可能采用下述三个值之一:AzureCloud、AzureUSGovernment、AzureChinaCloud。This can be one of three values - AzureCloud,AzureUSGovernment, AzureChinaCloud. 默认值为 AzureCloud。Default is AzureCloud. 当目标 Azure 区域为 Azure 美国政府或 Azure 中国世纪互联时,请使用此参数。Use the parameter when your target Azure region is either Azure US Government or Azure China 21Vianet.

    该工具会在指定的目录中创建多个 64 MB 的 asrvhdfile<#>.vhd 文件(其中“#”是文件编号)。The tool creates several 64-MB asrvhdfile<#>.vhd files (where "#" is the number of files) on the specified directory. 该工具会将这些文件上传到存储帐户来确定吞吐量。The tool uploads the files to the storage account to find the throughput. 测出吞吐量后,该工具会从存储帐户和本地服务器中删除所有这些文件。After the throughput is measured, the tool deletes all the files from the storage account and from the local server. 如果该工具在计算吞吐量时因故被终止,它不会从存储或本地服务器中删除这些文件。If the tool is terminated for any reason while it is calculating throughput, it doesn't delete the files from the storage or from the local server. 需要手动删除这些文件。You will have to delete them manually.

    吞吐量是根据指定时间点测量的,也是在其他所有系数保持相同的前提下,Site Recovery 可实现的最大吞吐量。The throughput is measured at a specified point in time, and it is the maximum throughput that Site Recovery can achieve during replication, provided that all other factors remain the same. 例如,如果任何应用程序在相同的网络中开始消耗更多的带宽,则在复制期间实际吞吐量会有所变化。For example, if any application starts consuming more bandwidth on the same network, the actual throughput varies during replication. 如果从配置服务器运行 GetThroughput 命令,该工具无法识别任何受保护的 VM 和正在进行的复制。If you are running the GetThroughput command from a configuration server, the tool is unaware of any protected VMs and ongoing replication. 如果是在受保护 VM 的数据变动量高时运行 GetThroughput 操作,则所测吞吐量的结果会有所不同。The result of the measured throughput is different if the GetThroughput operation is run when the protected VMs have high data churn. 建议在分析期间的不同时间点运行该工具,了解在不同时间能够达到的吞吐量水平。We recommend that you run the tool at various points in time during profiling to understand what throughput levels can be achieved at various times. 在报告中,该工具会显示最后一个测得的吞吐量。In the report, the tool shows the last measured throughput.

    示例Example

    ASRDeploymentPlanner.exe -Operation GetThroughput -Directory  E:\vCenter1_ProfiledData -Virtualization VMware -VMListFile E:\vCenter1_ProfiledData\ProfileVMList1.txt  -StorageAccountName  asrspfarm1 -StorageAccountKey by8vdM02xNOcqFlqUwJPLlmEtlCDXJ1OUzFT50uSRZ6IFsuFq2UVErCz4I6tq/K1SZFPTOtr/KBHBeksoGMGw==
    

    备注

    在与配置服务器具有相同存储和 CPU 特征的服务器上运行该工具。Run the tool on a server that has the same storage and CPU characteristics as the configuration server.

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

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

    2. 通过检查来确定 Site Recovery 保管库是否位于从物理上来说最近的受支持 Microsoft Azure 区域,以尽量降低网络延迟。Check to determine whether your Site Recovery vault is in the nearest physically supported Microsoft 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 of network bandwidth used for replication.

    后续步骤Next steps