Blog Post

Azure Stack Blog
2 MIN READ

Hyper-V VM Migration to Azure Stack HCI, version 23H2

KerimHanif's avatar
KerimHanif
Icon for Microsoft rankMicrosoft
Feb 12, 2024

Written by Kerim Hanif, Senior Program Manager on the Azure Edge & Platform team

 

 

Azure Migrate is a unified platform that simplifies migration, modernization, and optimization of on-premises resources to Azure. We have been working very closely with Azure Migrate team to add more destinations for Azure Migrate like VMware and Hyper-V. Last year we launched the private preview of Hyper-V virtual machine (VM) migration with Azure Migrate, and today we are very happy to announce the public preview of this capability.

Note: VMware migration is currently in private preview. Please fill this form if you would like to be part of the private preview and help us build a high-quality migration capability. 

 

What is new in this public preview?

This feature enables you to migrate your Windows and Linux VMs running on Hyper-V to Azure Stack HCI, version 23H2 clusters (GA as of Feb 1st of this year). A wide range of source environments starting from Hyper-V on Windows Server 2012 R2 to Windows Server 2022 are supported.

This feature uses the agentless migration option of Azure Migrate. This means that you don't need any prep such as installing an agent on the source VMs. All you need are two appliances, one on the source, and one on the target.

While you can manage, monitor, and configure via the cloud (Azure Migrate), the data transfer between the source and the target is kept local.  

All the migrated VMs are Arc-enabled by default. This means that the full power of Arc VM management is immediately available to you once the migration is complete. 

 

Migrating variety of VMs (Windows and Linux) from Hyper-V to Azure Stack HCI

How to get started?

  • Make sure that you have an Azure Stack HCI cluster running version 23H2.
  • Create a migration project in Azure Migrate.
  • Discover the VMs on your source Hyper-V servers and clusters.
  • Select the VMs you want to migrate and start replicating them to the target Azure Stack HCI cluster (source VMs can continue running at this stage).
  • When ready, start the migration, and migrate your VMs with minimal downtime.
  • Track the progress from the Azure portal.

Where to learn more?

For more information and detailed steps, please visit the following links:

Updated Feb 09, 2024
Version 1.0
  • Hi KerimHanif, I'm facing issue when starting to setup Target Appliance.

    (AzSHCI 23H2 cluster ready with Arc Resource Bridge, Storage Path, Logical Nic configured) 

     

    I've setup the Source Appliance and done the Discover progress, how ever, when I want to start the replication and selecting Azure Stack HCI, the screen shows that no Source Appliance detected.

     

    How show I troubleshoot further? 

     

     

  • adavissacc's avatar
    adavissacc
    Copper Contributor

    Where can I get support for stack hci migration? 1/2 of my hyperv migrated, but then 2 got stuck (dns went down mid way due to IP's not re-setting up properly) and now all migrations dont work, and the 2 stuck wont delete (the dns issue is resolved and the appliances rebooted during troubleshoot(

  • For those that are having issues, public preview is fully supported by Microsoft support. Please open a ticket to troubleshoot your issues. adavissacc LCKho3693 

  • adavissacc's avatar
    adavissacc
    Copper Contributor

    Seem to be issues with the data discs during migration

     

    They come across during replication but when doing the migrate it mounts a 1GB VHD instead of the data from the seed, OS drive is fine but 2nd disks not so much. I had 4 VMs all do this

     

    Lodging a case with support for it to determine if its issues with my setup 

     

     

  • KerimHanif great works from your team.

     

    I've just completed a test on migrating VM from stand-alone Hyper-V to AzSHCI 23H2.  Entire process pretty smooth with some minor enrichment appreciated, especially on the Replication Overview page. 

     

    Overall, well done. (Testing continue..... ing)