Best way of moving a Hyper-v vm from one server to another

[TwistedHelixis]

Whats the best way to move a Hyper-v VM to a new server?

 

Both hosts will be 2012r2 & the VMS are Gen2

 

I can think of a few ways

 

1 - restore from backup

2 - export and then import

3 - replication

4 - live migration

5 - copy the vhdx files and use the import option

 

I think MS recommend live migration but as its not something I have ever needed to do I wanted to check with you all first.

https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/use-live-migration-without-failover-clustering-to-move-a-virtual-machine

[cpjitservices]

Right click and click Move.

 

Point to new server.

[Jawloms]

Live migration. Used it a number of times.

[PotNoodleTech]

Yep, no need to overcomplicate things. Use HyperV Manager, right click, move, select server, make sure to move all vm files to the same place. Off you go!

[caffrey]

I've literally just done this, with no issues onto two new servers (Move) with 14 VM's

[mrstrong]

Don't you need to be a bit careful e.g. with regards to processor compatibility and

the virtual switch names need to match ?

 

e.g. see

Windows Hyper-V Server :: Connect using RDC

[caffrey]

I didn't have an issue with processor compatibility. With the virtual switch, if it doesn't match it will ask you which vswitch to use on the new host

[TwistedHelixis]

Well clicking move brings up a message about live migrations. Setting up live migrations brings up a message about not being on a domain.

 

None of my hosts are domain joined, they are single server setups at each primary school and even though its not such an issue having domain joined hosts I was concerned about logging in to the host if the VM DC went down that was running on that host.

 

export import ?????

[cpjitservices]

You have to have them domain joined for live migrations to work as it uses Kerberos for authentication, you can do it via certificates but I have never done this. Edited May 8, 2017 by cpjitservices

[Davit2005]

With VMWare you can do vMotion (live migrations) as long as you have same processor family i.e Intel to AMD won't live migrate.

 

If you haven't got migration setup or not confident to domain join the Hyper-V hosts you could use free version of Veeam to backup and then restore onto new server??

[TwistedHelixis]

I do already backup vms using Windows backup, restoring to a new host works fine, I just wanted an even better method of moving them.

[Davit2005]

I do already backup vms using Windows backup, restoring to a new host works fine, I just wanted an even better method of moving them.

 

Veeam again, even the free version is leagues ahead of Windows Backup.

 

Used to be able to schedule backups using PowerShell with Version 9 at least. It doesn't give the full features like backing up incremental and a few other things the full version does.

[cpjitservices]

In the worst case you could import a machine and add the VHD file as a drive.

[TwistedHelixis]

Windows backup does do incremental, does do schedule backups, does do proper host vm backups and is free. When I get a chance I will have a play with veeam but last time I checked Windows was actually better from the free angle.

[GroovyNerd]

I've used the export-vm powershell command. This will create a checkpoint for the VM and export it. Then import this into the VHD store on the new host. Create the VM point it to said VHD and away you go