this post was submitted on 10 Jul 2023
10 points (85.7% liked)
Sysadmin
7955 readers
2 users here now
A community dedicated to the profession of IT Systems Administration
No generic Lemmy issue posts please! Posts about Lemmy belong in one of these communities:
[email protected]
[email protected]
[email protected]
[email protected]
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You can use the 'move' function in Hyper-V to perform a live migration which incurs no downtime. Select the VM, click Move, select 'Move the virtual machine' (not 'Move the virtual machine's storage', that only moves the storage, not the whole VM), and then finish out the wizard. IIRC that is sensitive to host architecture being sufficiently similar (changing processor generations can make it sufficiently different), so it may not work for you.
If you can't do that and since it is a single-digit number of VMs, you could turn them off, copy the .vhd files to the new location, set the VMs up on the new server, and turn them on. That is, of course, going to incur some downtime, so it isn't optimal.
Yep, if move function works than go with that. Otherwise, get the VMs ready on the new cluster, copy over the VHDs, attach and run.
I've done both methods multiple times and never had any issues.
Thank you! I am hoping this works but it is a 10 year gap between the 2 hosts so I was not sure, but I can at least give it a try.