In this blog post I thought it would be fun to share how we migrated a customer environment from one Hyper-V Failover Cluster to another with Zero Downtime using Shared Nothing Live Migration.
The image below was some chicken scratch I drafted up during a meeting with the customer showing how we could do this.
I often tell people that I get paid to draw with crayons and see it really is true.
I hope you enjoy.
Dave
Shared Nothing Live Migration from Hyper-V Cluster to another Hyper-V Cluster (Without Down Time)
In this solution you will be able to migrate Virtual Machines between two Hyper-V Clusters without down time using Shared Nothing Live Migration. The steps below outline the process required to achieve these results.
Prerequisites
Infrastructure Servers Requirements
Component |
Requirement |
Servers |
|
Storage |
|
Migration Steps – Reverting to Standalone Virtual Machine from Highly Available
- Login to the Source Hyper-V Cluster and open Failover Cluster Manager
- Expand Cluster and select Roles.
-
Right-click on the Source Virtual Machine and select Remove
Note This step simply removes the Virtual Machine from the cluster and changes the availability of the Virtual Machine from Highly Available to Standalone. |
Migration Steps – Using Shared Nothing Live Migration to move the Virtual Machine to the target CSV Volume
- Open Hyper-V Manager and Right-click on the Source Virtual Machine that was removed from the cluster in the steps above and select Move.
- On the Before You Begin page, click Next.
- On the Choose Move type page, select Move the virtual machine and then click Next.
- On the Specify Destination Computer page, click Browse...
- Type the server name of the Target Cluster Node, click Check Names and click OK.
- Click Next on the Specify Destination Computer page.
- On the Choose Move Options page, select Move the virtual machine’s data to a signal location, click Next.
- Click Browse on the Choose a new location for virtual machine page.
- Click C drive and Select ClusterStorage folder.
- Select the desired destination Cluster Shared Volume and click Select Folder.
- Click Next on the Choose a new location for virtual machine page.
- On the Summary page, review and make sure all of information are correct and then click Finish.
Migration Steps – Making the Virtual Machine Highly Available on the new Hyper-V Failover Cluster
- Login to the Target node of the new Hyper-V Failover Cluster.
Note You moved the virtual machine to this node server. |
- Open Failover Cluster Manager.
- Expand Cluster and select Roles.
- On the Action pane, select Configure Role.
- On the Before You Begin page, click Next.
- On the Select Role page, select Virtual Machines and then click Next.
- Select the virtual machine which you would like to add it to the new cluster, click Next.
- Click Next on the Confirmation page.
- On Summary page, click Finish.
Is this work when migrating to hyper-v on windows server 2019
Yes this works on Server 2019
Will this work when migration from 2012R2 to 2019, Is there an boot issues you faced on VMs migrated to 2019 after migration
I can’t remember if this works from 2012R2 to 2019 –> There should be any boot issues as the VM Generation will stay the same.