Hyper-V - 3 VM migrations to new host
-
I have 3 VMs to move from one Hyper V host to a new Hyper V host. Has anyone had much luck with live migrations, or should I go straight to export/import?
-
-
Are the host of similar hardware?
If not I would recommend you shutdown and export it. This way if it's broken, you can just turn the old VM on and be functional.
-
Fortunately the hardware is not similar as the old hardware is a disaster. I like the fall back option.
-
Assuming both server have similar storage space, and only 2 nodes we are talking about. Take a look at Starwind's Virtual SAN. They can provide free license for 2 nodes (you have to ask for it). Anatoly Vilchinsky is a real champ. He hooked me up with the license. You should be able to find tutorial on how to set it up.
This will required downtime as it require restarts during installation and setting it up. It's a set and forget kind of deal. Crossover cable between the server highly recommended.
-
@Mike-Davis said in Hyper-V - 3 VM migrations to new host:
I have 3 VMs to move from one Hyper V host to a new Hyper V host. Has anyone had much luck with live migrations, or should I go straight to export/import?
I thought live migration only works on Failover Cluster environment. If it is not on a SAN or standalone storage, live migration may not work. I ran into issue with Live Migration due to delegation permission. Took me a while to find the cause and fixed it (don't remember what I changed but it was minor change).
-
@Mike-Davis said in Hyper-V - 3 VM migrations to new host:
I have 3 VMs to move from one Hyper V host to a new Hyper V host. Has anyone had much luck with live migrations, or should I go straight to export/import?
I would
- enable replication
- seed immediately
- wait for replication to complete
- fail over
- assuming it all works, disable replication
- delete from old host
-
Even if you have dissimilar hardware you should be able to live migrate between the two. I had an Intel CPU and an AMD CPU that I was able to live migrate between in the past.
-
@JaredBusch I was wondering if you could do that
My google skills must be lacking....
-
@aaronstuder said in Hyper-V - 3 VM migrations to new host:
@JaredBusch I was wondering if you could do that
My google skills must be lacking....
I've done it with my FreePBX install while on a call. I had about 15 seconds of silence when the network switched, but the call never dropped.
-
@JaredBusch Wow!
-
@JaredBusch said in Hyper-V - 3 VM migrations to new host:
@aaronstuder said in Hyper-V - 3 VM migrations to new host:
@JaredBusch I was wondering if you could do that
My google skills must be lacking....
I've done it with my FreePBX install while on a call. I had about 15 seconds of silence when the network switched, but the call never dropped.
Using Hyper-V failover?
-
@scottalanmiller said in Hyper-V - 3 VM migrations to new host:
@JaredBusch said in Hyper-V - 3 VM migrations to new host:
@aaronstuder said in Hyper-V - 3 VM migrations to new host:
@JaredBusch I was wondering if you could do that
My google skills must be lacking....
I've done it with my FreePBX install while on a call. I had about 15 seconds of silence when the network switched, but the call never dropped.
Using Hyper-V failover?
I had replication running and I timed the fail over to be immediately after a replication cycle. so a bit cheating on that. Was honestly luck on this one I feel.
I have also performed the built in Hyper-V migration while on a call with similar results. This I have done multiple times.
-
Were both of the Hosts domain joined? The old host is Server 2008 R2 and the new host is running Server 2012 R2 if that makes a difference.
-
in this case the servers can be offline all weekend long, so downtime isn't much of a concern.
-
@Mike-Davis said in Hyper-V - 3 VM migrations to new host:
Were both of the Hosts domain joined? The old host is Server 2008 R2 and the new host is running Server 2012 R2 if that makes a difference.
Then Export/Import
-
@Mike-Davis said in Hyper-V - 3 VM migrations to new host:
Were both of the Hosts domain joined?
Yes everything was domain joined. Honestly, they should always be domain joined.
You still need to allow constrained delegation though.
https://blogs.technet.microsoft.com/matthts/2012/06/10/configuring-kerberos-constrained-delegation-for-hyper-v-management/The old host is Server 2008 R2 and the new host is running Server 2012 R2 if that makes a difference.
This makes a HUGE difference. Hyper-V was completely redone for Server 2012+
In this instance, I would export and import.
-
@JaredBusch haha, same answer seconds apart
-
@scottalanmiller said in Hyper-V - 3 VM migrations to new host:
@JaredBusch said in Hyper-V - 3 VM migrations to new host:
@aaronstuder said in Hyper-V - 3 VM migrations to new host:
@JaredBusch I was wondering if you could do that
My google skills must be lacking....
I've done it with my FreePBX install while on a call. I had about 15 seconds of silence when the network switched, but the call never dropped.
Using Hyper-V failover?
Yep, I've also done this before with Hyper-V failover, 3CX was my PBX. I think I even recorded this on YouTube
-
@LAH3385 said in Hyper-V - 3 VM migrations to new host:
@Mike-Davis said in Hyper-V - 3 VM migrations to new host:
I have 3 VMs to move from one Hyper V host to a new Hyper V host. Has anyone had much luck with live migrations, or should I go straight to export/import?
I thought live migration only works on Failover Cluster environment. If it is not on a SAN or standalone storage, live migration may not work. I ran into issue with Live Migration due to delegation permission. Took me a while to find the cause and fixed it (don't remember what I changed but it was minor change).
Shared-nothing Live Migration is available since Hyper-V 2012:
