Support for Hyper-V is on the roadmap and will be enabled soon.
Azure Migrate needs access to VMware servers to automatically discover VMs for assessment. Create a VMware account with the following properties. You specify this account during Azure Migrate setup.
Log in to the Azure portal.
Specify the location in which to create the project, then click Create. You can only create an Azure Migrate project in the West Central US or East US region. However, you can still plan your migration for any target Azure location. The location specified for the project is only used to store the metadata gathered from on-premises VMs.
Azure Migrate creates an on-premises VM known as the collector appliance. This VM discovers on-premises VMware VMs, and sends metadata about them to the Azure Migrate service. To set up the collector appliance, you download an .OVA file, and import it to the on-premises vCenter server to create the VM.
In Copy project credentials, copy the project ID and key. You need these when you configure the collector.
Check that the .OVA file is secure, before you deploy it.
C:\>CertUtil -HashFile <file_location> [Hashing Algorithm]
C:\>CertUtil -HashFile C:\AzureMigrate\AzureMigrate.ova SHA256
The generated hash should match these settings.
For OVA version 126.96.36.199
For OVA version 188.8.131.52
For OVA version 184.108.40.206
For OVA version 220.127.116.11
Import the downloaded file to the vCenter Server.
In the vSphere Client console, click File > Deploy OVF Template.
In the Deploy OVF Template Wizard > Source, specify the location of the .ova file.
In the Azure Migrate Collector, open Set up prerequisites.
If the VM accesses the internet via a proxy, click Proxy settings, and specify the proxy address and listening port. Specify credentials if the proxy needs authentication. Learn more about the internet connectivity requirements and the list of URLs that the collector accesses.
The proxy address needs to be entered in the form http://ProxyIPAddressor http://ProxyFQDN. Only HTTP proxy is supported.
The collector checks that the collector service is running. The service is installed by default on the collector VM.
In Specify vCenter Server details, do the following:
In Specify migration project, specify the Azure Migrate project ID and key that you copied from the portal. If didn't copy them, open the Azure portal from the collector VM. In the project Overview page, click Discover Machines, and copy the values.
The collector only supports "English (United States)" as the operating system language and the collector interface language. Support for more languages is coming soon.
Discovery time depends on how many VMs you are discovering. Typically, for 100 VMs, after the collector finishes running it takes around an hour for discovery to finish.
After VMs are discovered, you group them and create an assessment.
An assessment includes information about whether the on-premises VMs are compatible for Azure, what would be the right VM size for running the VM in Azure and the estimated monthly Azure costs.
The Azure readiness view in the assessment shows the readiness status of each VM. Depending on the properties of the VM, each VM can be marked as:
For VMs that are ready, Azure Migrate recommends a VM size in Azure. The size recommendation done by Azure Migrate depends on the sizing criterion specified in the assessment properties. If the sizing criterion is performance-based sizing, the size recommendation is done by considering the performance history of the VMs (CPU and memory) and disks (IOPS and throughput). If the sizing criterion is 'as on-premises', Azure Migrate does not consider the performance data for the VM and disks. The recommendation for the VM size in Azure is done by looking at the size of the VM on-premises and the disk sizing is done based on the Storage type specified in the assessment properties (default is premium disks). Learn more about how sizing is done in Azure Migrate.
For VMs that aren't ready or conditionally ready for Azure, Azure Migrate explains the readiness issues, and provides remediation steps.
The VMs for which Azure Migrate cannot identify Azure readiness (due to data unavailability) are marked as readiness unknown.
In addition to Azure readiness and sizing, Azure Migrate also suggests tools that you can use for the migrating the VM. This requires a deeper discovery of on the on-premises environment. Learn more about how you can do a deeper discovery by installing agents on the on-premises machines. If the agents are not installed on the on-premises machines, lift and shift migration is suggested using Azure Site Recovery. If the agents are installed on the on-premises machine, Azure Migrate looks at the processes running inside the machine and identifies whether the machine is a database machine or not. If the machine is a database machine, Azure Database Migration Service is suggested, else Azure Site Recovery is suggested as the migration tool.
This view shows the total compute and storage cost of running the VMs in Azure along with the details for each machine. Cost estimates are calculated considering the size recommendations done by Azure Migrate for a machine, its disks, and the assessment properties.
The cost estimation provided by Azure Migrate is for running the on-premises VMs as Azure Infrastructure as a service (IaaS) VMs. Azure Migrate does not consider any Platform as a service (PaaS) or Software as a service (SaaS) costs.
Estimated monthly costs for compute and storage are aggregated for all VMs in the group.
Each assessment in Azure Migrate is associated with a confidence rating that ranges from 1 star to 5 star (1 star being the lowest and 5 star being the highest). The confidence rating is assigned to an assessment based on the availability of data points needed to compute the assessment. The confidence rating of an assessment helps you estimate the reliability of the size recommendations provided by Azure Migrate.
The confidence-rating of an assessment is more useful for assessments with sizing criterion as 'performance-based sizing. For performance-based sizing, Azure Migrate needs the utilization data for CPU, memory of the VM. Additionally, for every disk attached to the VM, it needs the disk IOPS and throughput data. Similarly for each network adapter attached to a VM, Azure Migrate needs the network in/out to do performance-based sizing. If any of the above utilization numbers are not available in vCenter Server, the size recommendation done by Azure Migrate may not be reliable. Depending on the percentage of data points available, the confidence rating for the assessment is provided as below:
An assessment may not have all the data points available due to one of the following reasons:
If the confidence rating of any assessment is below 4 Stars, we recommend you to change the vCenter Server statistics settings level to 3, wait for the duration that you want to consider for assessment (1 day/1 week/1 month) and then do discovery and assessment. If the preceding cannot be done, performance-based sizing may not be reliable and it is recommended to switch to as on-premises sizing by changing the assessment properties.
Zendesk Theme Designed by Diziana
Copyright © Diziana. All Rights Reserved