This is a Server 2016 Hypervisor and single server 2016 guest VM.
It looks like the backup software has been creating checkpoints that have failed to merge for about a week now. There are multiple .avhdx files for the VM in the file system but the Hyper-V UI shows no checkpoints exist.
In addition the Get-VMSnapshot command in Powershell agrees with the UI - no checkpoints:
However, checking the machine settings in Hyper-V manager, I find that the hard drive is pointing to one of the differencing disks and the message "Edit is not available because checkpoints exist for this virtual machine."
To make matters worse, I have no idea how to do a manual merge for these avhdx files because both the root/parent vhdx and TWO of the child avhdx files show the exact same date modified stamp - the time I shut down the VM last night. So I am not sure which avhdx is last in the chain.
Hyper-V is currently pointing to the differencing disk ending in B2C2 above. The one ending in CAC5 looks like it was created earlier (base on the .mrt file) but has the same stamp.
Also - at this point in the write-up I restarted the hypervisor, and when it came back up, the virtual machine had disappeared from Hyper-V:
So I went through the process of re-importing and registering in place:
This threw an error saying it failed, but the VM now re-appears in HyperV manager anyway. VERY strange.
I have started the VM again and will disable backup so no more checkpoints are created, but I really need to get this resolved quickly as the disk only has 116 GB of free space remaining and I do not want it to get so full that I cannot merge these checkpoints.
Help!
[Edit] - This post is for some reason being flagged as spam and so some of the embedded images are missing. I am trying to resolve this so the images can be displayed.