Create an Azure VMware Solution assessment

This article describes how to create an Azure VMware Solution assessment for on-premises VMs in a VMware vSphere environment with Azure Migrate: Discovery and assessment.

Azure Migrate helps you to migrate to Azure. Azure Migrate provides a centralized hub to track discovery, assessment, and migration of on-premises infrastructure, applications, and data to Azure. The hub provides Azure tools for assessment and migration, as well as third-party independent software vendor (ISV) offerings.

Before you start

• Make sure you've created an Azure Migrate project.
• If you've already created a project, make sure you've added the Azure Migrate: Discovery and assessment tool.
• To create an assessment, you need to set up an Azure Migrate appliance for VMware vSphere, which discovers the on-premises servers, and sends metadata and performance data to Azure Migrate: Discovery and assessment. Learn more.
• You could also import the server metadata in comma-separated values (CSV) format or import your RVTools XLSX file.

Azure VMware Solution (AVS) Assessment overview

There are four types of assessments you can create using Azure Migrate: Discovery and assessment.

There are two types of sizing criteria that you can use to create Azure VMware Solution (AVS) assessments:

Run an Azure VMware Solution (AVS) assessment

1. On the Overview page > Servers, databases and web apps, click Assess and migrate servers.

2. In Azure Migrate: Discovery and assessment, click Assess.

3. In Assess servers > Assessment type, select Azure VMware Solution (AVS).

4. In Discovery source:

   • If you discovered servers using the appliance, select Servers discovered from Azure Migrate appliance.
   • If you discovered servers using an imported CSV or RVTools file, select Imported servers.

5. Click Edit to review the assessment properties.

   

6. In Assessment properties > Target Properties:

   • In Target location, specify the Azure region to which you want to migrate.
     • Size and cost recommendations are based on the location that you specify.
   • The Storage type is defaulted to vSAN. This is the default storage type for an Azure VMware Solution private cloud.
   • In Reserved Instances, specify whether you want to use reserve instances for Azure VMware Solution nodes when you migrate your VMs.
   • If you select to use a reserved instance, you can't specify 'Discount (%)
   • Learn more

7. In VM Size:

   • The Node type is defaulted to AV36. Azure Migrate recommends the number of nodes needed to migrate the servers to Azure VMware Solution.
   • In FTT setting, RAID level, select the Failure to Tolerate and RAID combination. The selected FTT option, combined with the on-premises server disk requirement, determines the total vSAN storage required in AVS.
   • In CPU Oversubscription, specify the ratio of virtual cores associated with one physical core in the AVS node. Oversubscription of greater than 4:1 might cause performance degradation, but can be used for web server type workloads.
   • In Memory overcommit factor, specify the ratio of memory over commit on the cluster. A value of 1 represents 100% memory use, 0.5 for example is 50%, and 2 would be using 200% of available memory. You can only add values from 0.5 to 10 up to one decimal place.
   • In Dedupe and compression factor, specify the anticipated deduplication and compression factor for your workloads. Actual value can be obtained from on-premises vSAN or storage config and this may vary by workload. A value of 3 would mean 3x so for 300GB disk only 100GB storage would be used. A value of 1 would mean no dedupe or compression. You can only add values from 1 to 10 up to one decimal place.

8. In Node Size:

   • In Sizing criterion, select if you want to base the assessment on static metadata, or on performance-based data. If you use performance data:

     • In Performance history, indicate the data duration on which you want to base the assessment
     • In Percentile utilization, specify the percentile value you want to use for the performance sample.

   • In Comfort factor, indicate the buffer you want to use during assessment. This accounts for issues like seasonal usage, short performance history, and likely increases in future usage. For example, if you use a comfort factor of two:

     Component	Effective utilization	Add comfort factor (2.0)
     Cores	2	4
     Memory	8 GB	16 GB

9. In Pricing:

   • In Offer, Azure offer you're enrolled in is displayed. The Assessment estimates the cost for that offer.
   • In Currency, select the billing currency for your account.
   • In Discount (%), add any subscription-specific discounts you receive on top of the Azure offer. The default setting is 0%.

10. Click Save if you make changes.

    

11. In Assess Servers, click Next.

12. In Select servers to assess > Assessment name > specify a name for the assessment.

13. In Select or create a group > select Create New and specify a group name.

    

14. Select the appliance, and select the servers you want to add to the group. Then click Next.

15. In Review + create assessment, review the assessment details, and click Create Assessment to create the group and run the assessment.

    Note

    For performance-based assessments, we recommend that you wait at least a day after starting discovery before you create an assessment. This provides time to collect performance data with higher confidence. Ideally, after you start discovery, wait for the performance duration you specify (day/week/month) for a high-confidence rating.

Review an Azure VMware Solution (AVS) assessment

An Azure VMware Solution (AVS) assessment describes:

• Azure VMware Solution (AVS) readiness: Whether the on-premises VMs are suitable for migration to Azure VMware Solution (AVS).
• Number of Azure VMware Solution nodes: Estimated number of Azure VMware Solution nodes required to run the servers.
• Utilization across AVS nodes: Projected CPU, memory, and storage utilization across all nodes.
  • Utilization includes up front factoring in the following cluster management overheads such as the vCenter Server, NSX Manager (large), NSX Edge, if HCX is deployed also the HCX Manager and IX appliance consuming ~ 44vCPU (11 CPU), 75GB of RAM and 722GB of storage before compression and deduplication.
  • Limiting factor determines the number of hosts/nodes required to accommodate the resources.
• Monthly cost estimation: The estimated monthly costs for all Azure VMware Solution (AVS) nodes running the on-premises VMs.

You can click on Sizing assumptions to understand the assumptions that went in node sizing and resource utilization calculations. You can also edit the assessment properties, or recalculate the assessment.

View an assessment

1. In Windows, Linux and SQL Server > Azure Migrate: Discovery and assessment, click the number next to Azure VMware Solution.

2. In Assessments, select an assessment to open it. As an example (estimations and costs for example only):

   

3. Review the assessment summary. You can click on Sizing assumptions to understand the assumptions that went in node sizing and resource utilization calculations. You can also edit the assessment properties, or recalculate the assessment.

Review Azure VMware Solution (AVS) readiness

1. In Azure readiness, verify whether servers are ready for migration to AVS.

2. Review the server status:

   • Ready for AVS: The server can be migrated as-is to Azure (AVS) without any changes. It will start in AVS with full AVS support.
   • Ready with conditions: There might be some compatibility issues example internet protocol or deprecated OS in VMware and need to be remediated before migrating to Azure VMware Solution. To fix any readiness problems, follow the remediation guidance the assessment suggests.
   • Not ready for AVS: The VM will not start in AVS. For example, if the on-premises VMware VM has an external device attached such as a cd-rom the VMware vMotion operation will fail (if using VMware vMotion).
   • Readiness unknown: Azure Migrate couldn't determine the readiness of the server because of insufficient metadata collected from the on-premises environment.

3. Review the Suggested tool:

   • VMware HCX Advanced or Enterprise: For VMware vSphere VMs, VMware Hybrid Cloud Extension (HCX) solution is the suggested migration tool to migrate your on-premises workload to your Azure VMware Solution (AVS) private cloud. Learn More.
   • Unknown: For servers imported via a CSV or RVTools file, the default migration tool is unknown. Though for VMware vSphere VMs, it is suggested to use the VMware Hybrid Cloud Extension (HCX) solution.

4. Click on an AVS readiness status. You can view VM readiness details, and drill down to see VM details, including compute, storage, and network settings.

Review cost details

This view shows the estimated cost of running servers in Azure VMware Solution.

1. Review the monthly total costs. Costs are aggregated for all servers in the assessed group.

   • Cost estimates are based on the number of AVS nodes required considering the resource requirements of all the servers in total.
   • As the pricing for Azure VMware Solution is per node, the total cost does not have compute cost and storage cost distribution.
   • The cost estimation is for running the on-premises servers in AVS. AVS assessment doesn't consider PaaS or SaaS costs.

2. You can review monthly storage cost estimates. This view shows aggregated storage costs for the assessed group, split over different types of storage disks.

3. You can drill down to see details for specific servers.

Review confidence rating

When you run performance-based assessments, a confidence rating is assigned to the assessment.

• A rating from 1-star (lowest) to 5-star (highest) is awarded.
• The confidence rating helps you estimate the reliability of the size recommendations provided by the assessment.
• The confidence rating is based on the availability of data points needed to compute the assessment.
• For performance-based sizing, AVS assessments need the utilization data for CPU and server memory. The following performance data is collected but not used in sizing recommendations for AVS assessments:
  • The disk IOPS and throughput data for every disk attached to the server.
  • The network I/O to handle performance-based sizing for each network adapter attached to a server.

Confidence ratings for an assessment are as follows.

Learn more about performance data

Next steps

• Learn how to use dependency mapping to create high confidence groups.
• Learn more about how Azure VMware Solution assessments are calculated.