today I want to share a challenge and step-by-step solution I had with one quite specific setup.
Following the scenario:
I have two Windows Server 2012 R2 Hyper-V Clusters, in different domains but connected to the same storage.
Now I needed to migrate 20 Virtual Machines from Cluster A to Cluster B.
Hyper-V has the “Copy Cluster Role” Wizard which is basically doing this kind of migration, but it’s not working cross-domain. Therefore I had so search another solution.
Here the process of moving the VMs:
- Using the Failover Cluster Manager, move all VMs which should be migrated to the same CSV and make sure no other VMs are on that disk.
- Shut down the Virtual Machines
- Take the CSV offline
- Unexport/Unpresent the VLUN from Cluster A
- Optional: Rename the VLUN in the storage system (my VLUNs are named according to the cluster they belong to)
- Export/Present the VLUN to Cluster B
- Take the disk online and add it as Cluster Shared Volume to the Failover Cluster
- Optional: Rename the disk in Disk Management / Failover Cluster Manager
- Import the VMs (register in-place) using the Hyper-V Manager
- Configure Cluster Role in Failover Cluster Manager.
This gives you the option to make all of the imported VMs HA in bulk
- Start your Virtual Machines and test the network connectivity and Live/Quick migration
Now comes the cleanup on the source cluster:
- Remove VMs from the Cluster
- Remove CSV from Cluster Shared Volumes
- Remove CSV from Cluster Disks
The migration time was around 30min for all of the above, whereas the most time was needed for the import of the VMs.