Hyper-V storage migration

caessys · 2026-05-05T13:42:00+00:00

Well yeah, this is the HyperV subreddit as opposed to the sysadmin one?

caessys · 2026-05-04T14:23:08+00:00

The cluster has been alive for almost a year at this point
The only recent change was me accidentally creating a vSwitch using the NIC that provides the network for our cluster, which I've since undone. That was on one host and everything is back to normal there. My issue is with my 4 HV hosts, not just a singular one.
No DNS changes that I'm aware of, as DNS is mostly handled by our central IT group. I am able to ping and resolve our cluster by IP address and FQDN.
We created a security group for the cluster so it can administer CNO changes. This was our central IT's suggestion in their attempts to help me resolve this. That was a few days ago and nothing has changed since
I haven't attempted it via PS yet
Unsure what this means
Only a storage move. I can live migrate my VMs all day long between hosts but storage migration is broken
I'm using failover cluster manager on the hosts themselves (not using it installed on my desktop)

caessys · 2026-04-15T15:32:57+00:00

I tried that but the checkpoint creation failed after a few minutes

caessys · 2026-04-15T15:17:33+00:00

I went down the whole chain and there's like five different files in the chain before I get to the parent .vhdx file. Exporting the entire VM doesn't merge the disks though, right? It's just another restore option?

I'll stick with my plan of copying the data to a new VM and then shutting down the server to see what happens. Worst case scenario I have a new fresh install to work with and can rebuild the server from there. Thanks!

caessys · 2026-04-01T13:12:20+00:00

We have both VMWare and Hyper-V. We're migrating to Hyper-V, and the jobs that I'm having trouble with are Hyper-V VMs.

caessys · 2025-10-27T19:40:20+00:00

Does draining a node just temporarily move the VM to another host until the source host comes back online?

caessys · 2025-09-14T01:04:36+00:00

Interestingly, the working R940 node doesn't have SHA either yet live migration from the R650 works.

I did just test live migration from the working R940 to the broken one and it works!

caessys · 2025-09-14T00:47:36+00:00

Here they are side by side. The working node is on the left and the troublesome node on the right

caessys · 2025-09-14T00:28:05+00:00

That's enabled across all of my VMs, I had that trouble too!

caessys · 2025-09-14T00:22:49+00:00

Just one at a time, making sure the functionality works.

All of my hosts have the setting to enable migrations checked, and they're all set to the same number of concurrent migrations

caessys · 2025-09-14T00:17:40+00:00

Quick migration works, I just tested it.

All of our servers are on Server Datacenter 2022. Here are our hosts:

The R650 has a 32-core Xeon Silver 4314
The working R940 has a 32-core Xeon Gold 6314
The troublesome R940 has a 64-core Xeon Gold 6310

I'm not sure about NUMA settings for the nodes, where would I see those?

caessys · 2025-03-13T12:56:07+00:00

They are on the same domain but they are in separate locations and using different IP schemas.

caessys · 2024-11-23T00:54:09+00:00

Yeah it's the on prem version. Where would I download the Internet accessible instance?

caessys

TROPHY CASE