this post was submitted on 10 Jul 2023
10 points (85.7% liked)

Sysadmin

7956 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
 

I have a customer with an old Windows Server 2012 with hyper v cluster configured for 2 nodes. One node died completely. I have 2 new HP proliant 360 Gen10 running Server 2022 DC and a big SAN, and I am trying to figure out the best way to move over the 6 VMs on the existing host. I’m new to this process but it seems like the host OSes must match for me to move the old VMs over. Is the best way to just export a Datto backup of the VMs to the new cluster? Any way to do this live? Any advice I’d appreciate and apologies if I wasn’t clear at all.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 3 points 2 years ago (1 children)

Did that before. First, ensure you aren't running on any snapshots. If your VMs have any snapshots, delete them.

If the move function works then use that but I suspect it won't. You can simply use the "move the vm's storage" option to ensure the VHD is properly consolidated, then you can put it on the new host and start the VM there (shut it off before moving of course). If your host is running a newer hyper v version you might need to bump the hypervisor version for each VHD in PowerShell, that might take a while but it's usually fast.

[–] thorbot 1 points 2 years ago

Thanks for the advice! I am pretty sure the move function won't work since the OS and hardware are 10 years apart but I will try it anyway. If not I will try the storage move.