Scenario 1: In-place migration of two standalone Windows Servers (Hyper-v role installed) into clustered Windows Servers (Hyper-v role installed).
Steps involved in this scenario. There will be downtime in this scenario.
- Delete all snapshots from VMs
- Update Windows Server to latest patches and hotfixes
- Reboot hosts
- Install Failover Clustering Windows Feature in both hosts
- Connect hosts with shared storage infrastructure either iSCSI or fibre channel
- Present shared storage (5GB for Quorum disk and additional disk for VMs store) to Hyper-v Hosts.
- Run Failover cluster Wizard, create cluster.
- From the failover cluster manager, Click Disk, select virtual machine storage and convert the disk to clustered share volume
- Open Hyper-v Manager from Server Manager, run storage migration and migrate all VM data to single location which is shared storage.
- Now use Configure Role Wizard from Failover Cluster Manager, Select Virtual Machine from drop down list, Select one or More VMs and migrate those VMs to Failover cluster node.
- Test Live migration.
Scenario 2: Migrating standalone Windows Servers (Hyper-v role installed) using local storage to different Windows Servers (Hyper-v role installed) cluster using shared storage.
In this scenario, clustered Windows servers doesn’t see local storage available in old Hyper-v host and old Hyper-v host doesn’t see shared storage in new Hyper-v clustered environment. There will be downtime when you migrate VMs. Delete any snapshot, backup all VMs before you proceed.
Option A: Download Veeam Backup & Replication 8 trial version, configure a VM as Veeam management server. Add Source host as standalone hyper-v host and target host as Hyper-v cluster. Replicate all the VMs. Shutdown old VMs in standalone Hyper-v Hosts, then Power on VMs in Hyper-v cluster. Delete old VMs.
Option B: Copy VHD and configuration file and save into clustered shared storage. Log on to one of the clustered hyper-v host, Open Hyper-v Manager, Import VM option to import VM. Then use Configure Role option in failover Cluster Manager in same host to migrate the VM into cluster, then Power on VM in cluster.
My recommendation: use Veeam B&R.
Scenario 3: Migrating standalone Windows Servers (Hyper-v role installed) using iSCSI storage to different Windows Servers (Hyper-v role installed) cluster using fibre channel or iSCSI storage.
Option A: shutdown VMs. Present same iSCSI storage connected standalone hosts to clustered hosts. Use storage migration to migrate VMs to clustered Hosts. Then use configure role option, Failover cluster manager to migrate VMs to Hyper-v cluster.
Option B: Again use Veeam to do the job.
There are many factors/challenges when migrating VMs from standalone environment to clustered environment.
- iSCSI storage to Fibre Channel storage. When new cluster has host bus adapter (HBA) and old standalone host doesn’t have HBA. You can use Microsoft iSCSI initiation to fulfil the initiator requirement in new host.
- Fibre channel storage to iSCSI storage. There will heaps of downtime to fulfil this requirement because of new architecture. Veeam can be part of a solution.
- Multi-site and geographically diverse cluster will depend on MPLS or IPVPN network latency and bandwidth.
In conclusion, there is no silver bullet for individual situation. You have to consult with Microsoft partner to get a correct migration path that best fit your requirements.