Migrate Hyper-V VMs to Azure

This article shows you how to migrate on-premises Hyper-V VMs to Azure with the Azure Migrate:Server Migration tool.

This tutorial is the third in a series that demonstrates how to assess and migrate machines to Azure.

Note

Tutorials show you the simplest deployment path for a scenario so that you can quickly set up a proof-of-concept. Tutorials use default options where possible, and don't show all possible settings and paths.

In this tutorial, you learn how to:

  • Add the Azure Migrate:Server Migration tool.
  • Discover VMs you want to migrate.
  • Start replicating VMs.
  • Run a test migration to make sure everything's working as expected.
  • Run a full VM migration.

If you don't have an Azure subscription, create a free account before you begin.

Prerequisites

Before you begin this tutorial, you should:

  1. Review the Hyper-V migration architecture.
  2. Review Hyper-V host requirements for migration, and the Azure URLs to which Hyper-V hosts and clusters need access for VM migration.
  3. Review the requirements for Hyper-V VMs that you want to migrate to Azure.
  4. We recommend that you assess Hyper-V VMs before migrating them to Azure, but you don't have to.
  5. Go to the already created project or create a new project.
  6. Verify permissions for your Azure account - Your Azure account needs permissions to create a VM, and write to an Azure managed disk.

Download the provider

For migrating Hyper-V VMs, Azure Migrate:Server Migration installs software providers (Microsoft Azure Site Recovery provider and Microsoft Azure Recovery Service agent) on Hyper-V Hosts or cluster nodes. Note that the Azure Migrate appliance isn't used for Hyper-V migration.

  1. In the Azure Migrate project > Servers, in Azure Migrate: Server Migration, click Discover.

  2. In Discover machines > Are your machines virtualized?, select Yes, with Hyper-V.

  3. In Target region, select the Azure region to which you want to migrate the machines.

  4. Select Confirm that the target region for migration is region-name.

  5. Click Create resources. This creates an Azure Site Recovery vault in the background.

    • If you've already set up migration with Azure Migrate Server Migration, this option won't appear since resources were set up previously.
    • You can't change the target region for this project after clicking this button.
    • All subsequent migrations are to this region.
  6. In Prepare Hyper-V host servers, download the Hyper-V Replication provider, and the registration key file.

    • The registration key is needed to register the Hyper-V host with Azure Migrate Server Migration.
    • The key is valid for five days after you generate it.

    Download provider and key

  7. Copy the provider setup file and registration key file to each Hyper-V host (or cluster node) running VMs you want to replicate.

Install and register the provider

Copy the provider setup file and registration key file to each Hyper-V host (or cluster node) running VMs you want to replicate. To install and register the provider, follow the steps below using either the UI or commands:

Run the provider setup file on each host, as described below:

  1. Click the file icon in the taskbar to open the folder where the installer file and registration key are downloaded.
  2. Select AzureSiteRecoveryProvider.exe file.
    • In the provider installation wizard, ensure On (recommended) is checked, and then click Next.
    • Select Install to accept the default installation folder.
    • Select Register to register this server in Azure Site Recovery vault.
    • Click Browse.
    • Locate the registration key and click Open.
    • Click Next.
    • Ensure Connect directly to Azure Site Recovery without a proxy server is selected, and then click Next.
    • Click Finish.

After installing the provider on hosts, go to the Azure portal and in Discover machines, click Finalize registration.

Finalize registration

It can take up to 15 minutes after finalizing registration until discovered VMs appear in Azure Migrate Server Migration. As VMs are discovered, the Discovered servers count rises.

Discovered servers

Replicate Hyper-V VMs

With discovery completed, you can begin replication of Hyper-V VMs to Azure.

Note

You can replicate up to 10 machines together. If you need to replicate more, then replicate them simultaneously in batches of 10.

  1. In the Azure Migrate project > Servers, Azure Migrate: Server Migration, click Replicate.

  2. In Replicate, > Source settings > Are your machines virtualized?, select Yes, with Hyper-V. Then click Next: Virtual machines.

  3. In Virtual machines, select the machines you want to replicate.

    • If you've run an assessment for the VMs, you can apply VM sizing and disk type (premium/standard) recommendations from the assessment results. To do this, in Import migration settings from an Azure Migrate assessment?, select the Yes option.

    • If you didn't run an assessment, or you don't want to use the assessment settings, select the No options.

    • If you selected to use the assessment, select the VM group, and assessment name.

      Select assessment

  4. In Virtual machines, search for VMs as needed, and check each VM you want to migrate. Then, click Next: Target settings.

    Select VMs

  5. In Target settings, select the target region to which you'll migrate, the subscription, and the resource group in which the Azure VMs will reside after migration.

  6. In Replication Storage Account, select the Azure Storage account in which replicated data will be stored in Azure.

  7. Virtual Network, select the Azure VNet/subnet to which the Azure VMs will be joined after migration.

  8. In Availability options, select:

    • Availability Zone to pin the migrated machine to a specific Availability Zone in the region. Use this option to distribute servers that form a multi-node application tier across Availability Zones. If you select this option, you'll need to specify the Availability Zone to use for each of the selected machine in the Compute tab. This option is only available if the target region selected for the migration supports Availability Zones
    • Availability Set to place the migrated machine in an Availability Set. The target Resource Group that was selected must have one or more availability sets in order to use this option.
    • No infrastructure redundancy required option if you don't need either of these availability configurations for the migrated machines.
  9. In Azure Hybrid Benefit:

    • Select No if you don't want to apply Azure Hybrid Benefit. Then, click Next.
    • Select Yes if you have Windows Server machines that are covered with active Software Assurance or Windows Server subscriptions, and you want to apply the benefit to the machines you're migrating. Then click Next.

    Target settings

  10. In Compute, review the VM name, size, OS disk type, and availability configuration (if selected in the previous step). VMs must conform with Azure requirements.

    • VM size: If you're using assessment recommendations, the VM size dropdown will contain the recommended size. Otherwise Azure Migrate picks a size based on the closest match in the Azure subscription. Alternatively, pick a manual size in Azure VM size.
    • OS disk: Specify the OS (boot) disk for the VM. The OS disk is the disk that has the operating system bootloader and installer.
    • Availability Set: If the VM should be in an Azure availability set after migration, specify the set. The set must be in the target resource group you specify for the migration.

    VM compute settings

  11. In Disks, specify the VM disks that needs to be replicated to Azure. Then click Next.

    • You can exclude disks from replication.
    • If you exclude disks, won't be present on the Azure VM after migration.

    Screenshot shows the Disks tab of the Replicate dialog box.

  12. In Review and start replication, review the settings, and click Replicate to start the initial replication for the servers.

Note

You can update replication settings any time before replication starts, in Manage > Replicating machines. Settings can't be changed after replication starts.

Provision for the first time

If this is the first VM you're replicating in the Azure Migrate project, Azure Migrate: Server Migration automatically provisions these resources in same resource group as the project.

  • Cache storage account: The Azure Site Recovery provider software installed on Hyper-V hosts uploads replication data for the VMs configured for replication to a storage account (known as the cache storage account, or log storage account) in your subscription. The Azure Migrate service then copies the uploaded replication data from the storage account to the replica-managed disks corresponding to the VM. The cache storage account needs to be specified while configuring replication for a VM and The Azure Migrate portal automatically creates one for the Azure Migrate project when replication is configured for the first time in the project.

Track and monitor

  • When you click Replicate a Start Replication job begins.
  • When the Start Replication job finishes successfully, the machines begin their initial replication to Azure.
  • After initial replication finishes, delta replication begins. Incremental changes to on-premises disks are periodically replicated to Azure.

You can track job status in the portal notifications.

You can monitor replication status by clicking on Replicating servers in Azure Migrate: Server Migration. Monitor replication

Run a test migration

When delta replication begins, you can run a test migration for the VMs, before running a full migration to Azure. We highly recommend that you do this at least once for each machine, before you migrate it.

  • Running a test migration checks that migration will work as expected, without impacting the on-premises machines, which remain operational, and continue replicating.
  • Test migration simulates the migration by creating an Azure VM using replicated data (usually migrating to a non-production Azure VNet in your Azure subscription).
  • You can use the replicated test Azure VM to validate the migration, perform app testing, and address any issues before full migration.

Do a test migration as follows:

  1. In Migration goals > Servers > Azure Migrate: Server Migration, click Test migrated servers.

    Test migrated servers

  2. Right-click the VM to test, and click Test migrate.

    Test migration

  3. In Test Migration, select the Azure virtual network in which the Azure VM will be located after the migration. We recommend you use a non-production virtual network.

  4. The Test migration job starts. Monitor the job in the portal notifications.

  5. After the migration finishes, view the migrated Azure VM in Virtual Machines in the Azure portal. The machine name has a suffix -Test.

  6. After the test is done, right-click the Azure VM in Replicating machines, and click Clean up test migration.

    Clean up migration

    Note

    You can now register your servers running SQL server with SQL VM RP to take advantage of automated patching, automated backup and simplified license management using SQL IaaS Agent Extension.

    • Select Manage > Replicating servers > Machine containing SQL server > Compute and Network and select yes to register with SQL VM RP.
    • Select Azure Hybrid benefit for SQL Server if you have SQL Server instances that are covered with active Software Assurance or SQL Server subscriptions and you want to apply the benefit to the machines you're migrating.hs.

Migrate VMs

After you've verified that the test migration works as expected, you can migrate the on-premises machines.

  1. In the Azure Migrate project > Servers > Azure Migrate: Server Migration, click Replicating servers.

    Replicating servers

  2. In Replicating machines, right-click the VM > Migrate.

  3. In Migrate > Shut down virtual machines and perform a planned migration with no data loss, select Yes > OK.

    • By default Azure Migrate shuts down the on-premises VM, and runs an on-demand replication to synchronize any VM changes that occurred since the last replication occurred. This ensures no data loss.
    • If you don't want to shut down the VM, select No
  4. A migration job starts for the VM. Track the job in Azure notifications.

  5. After the job finishes, you can view and manage the VM from the Virtual Machines page.

Complete the migration

  1. After the migration is done, right-click the VM > Stop replication. This does the following:
    • Stops replication for the on-premises machine.
    • Removes the machine from the Replicating servers count in Azure Migrate: Server Migration.
    • Cleans up replication state information for the VM.
  2. Verify and troubleshoot any Windows activation issues on the Azure VM.
  3. Perform any post-migration app tweaks, such as updating host names, database connection strings, and web server configurations.
  4. Perform final application and migration acceptance testing on the migrated application now running in Azure.
  5. Cut over traffic to the migrated Azure VM instance.
  6. Remove the on-premises VMs from your local VM inventory.
  7. Remove the on-premises VMs from local backups.
  8. Update any internal documentation to show the new location and IP address of the Azure VMs.

Post-migration best practices

Next steps

Investigate the cloud migration journey in the Azure Cloud Adoption Framework.