I'm dealing with a couple of virtual machines that have .avhdx files, but when I check, they don't display any checkpoints. I ran the Get-VMSnapshot command in PowerShell, and it came back empty for these VMs. The servers have been really slow to access, and I'm worried this all began when backups started running slowly, causing a bottleneck.
I'm thinking of shutting down the servers this weekend to see if that triggers any merging processes. If that doesn't work, I might have to try manually merging the disks. In the meantime, I'm creating new VMs to transfer data over. Has anyone faced a similar issue? What did you do to fix it?
5 Answers
I spent two whole days trying to map out orphaned checkpoints and manually merged them, but it all ended up being pointless since the server had already been in trouble longer than the backup history, so we had to start from scratch.
.avhdx files with no snapshots often mean that you've got a backup or VSS checkpoint chain that's become stranded. Before you go for a manual merge, you should check the parent chain and the backup history. Merging the wrong branch could really complicate things, so if you can export or restore to a new VM, that's usually a safer option.
I've encountered this too! Creating a new checkpoint and then deleting it typically helps clear out those orphaned .avhdx files. Just keep an eye on the Hyper-V Manager to track the merging progress and wait for a success message before checking in Explorer.
Have you thought about moving the VM to a different datastore? Sometimes that can help resolve these types of issues.
I’ve had a similar situation before. Using a backup agent like Veeam to back up the VM and then restoring it as a new VM has worked for me.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures