Hey everyone,
I'm trying to find the easiest way to migrate my single-node Hyper-V setups to the new Azure Local 23h2. Everything is on the same subnet and switch, so I'm looking for the quickest route. However, I'm a bit confused about why a direct connection isn't really an option since it feels like it should be a straightforward node-to-node transfer.
I've considered using Veeam for replication, but it's a bit too complex for my liking. Azure Migrate also doesn't seem to be the right tool for moving to on-prem Azure Local.
Any recommendations or alternatives you could suggest? Thanks!
2 Answers
You might want to look into using Hyper-V Replica if you're mainly focusing on moving your VMs. But, if managing them via the Azure portal (like controlling power states and sizing) is important to you, then Azure Migrate is the way to go. Just keep in mind that you'll need to set up an Azure Migrate appliance on each standalone Hyper-V node you have.
I think I missed the part about logical networks too. Need to dive deeper into that. The VMs will need to keep their IPs, right?
For a simpler approach, you could export the VMs to .VHDX files and copy them over via SMB. Then, use the New-AzStackHCI command (or whatever your local setup requires) to import them. It might be a bit 'old school,' but it could save you from the complexities of using full replication tools for a one-time migration.
The only issue is that I need to keep everything as live as possible during this process. Exporting and importing would mean downtime, and that’s something we’re trying to avoid.
Got it! We usually rely on FCM and Hyper-V manager, but I see now that managing from the Azure portal is probably more efficient. By the way, I've already set up Azure Migrate, so I've got appliances on both ends and everything's discovered.