Great video, exactly what I was looking for. One thing I didn't see though is why in the snapshots folder when I create a checkpoint (say 89F2E75D-D0B2-48B4-B2E8-4786683A8641), I also always get a empty folder with the same name? I am running Windows 10 Pro, so not sure if this is something new vs. when you posted the video.
Hello, thank you for explaining checkpoints, I have a VM which is hosted on Hyper-V Failover Cluster with 2 nodes. The total size of VM is now 11TB, I was taking backup through Veeam. Now backup is getting failed, as per Veeam there are multiple checkpoints (267) leftover in VM hard drive folder, but when I check on Hyper-V Manager console , I don’t see any checkpoint. I tried to create new checkpoint then delete. Checkpoint is deleted but while merging process I have seen message checkpoint merging failed. Please help to how to delete checkpoints leftover from HDD folder. Thank you
1. Identify and Confirm the Checkpoint Files Check the VM Folder: Navigate to the folder where the VM’s virtual hard disks (VHDX) are stored. This is usually in C:\ClusterStorage\VolumeX\VMName or wherever your VM resides. Look for AVHDX files (differencing disks). These indicate leftover checkpoint files. Verify Dependencies: Use the Inspect Disk feature in Hyper-V Manager: Open Hyper-V Manager. Click Edit Disk and browse to one of the AVHDX files. Select Inspect to see its parent disk. This helps understand the chain of dependencies. 2. Attempt to Merge Checkpoints Manually Backup Critical Files: Before making changes, back up the VM’s entire folder (including all VHDX and AVHDX files) to ensure recoverability. Manually Merge the Differencing Disks: Open Hyper-V Manager. Navigate to Edit Disk and select one of the AVHDX files. Choose Merge and follow the prompts: Merge to the parent disk. Repeat this for all AVHDX files, ensuring the chain merges correctly. Restart the VM: Once all differencing disks are merged, ensure the VM boots properly. 3. Check for Orphaned Checkpoints with PowerShell List Checkpoints: powershell Copy code Get-VMSnapshot -VMName "YourVMName" If no checkpoints are listed but files remain, proceed with manual cleanup. Force Remove Orphaned Checkpoints: powershell Copy code Remove-VMSnapshot -VMName "YourVMName" -IncludeAll This removes all associated snapshots. 4. Reconnect or Recreate the Virtual Disk Chain Fix VM Configuration: If merging fails, reattach the VHDX file directly to the VM: Shut down the VM. Remove the current disk from the VM settings. Add the base VHDX file back to the VM. Repair Configuration Files: Use the following PowerShell commands: powershell Copy code $VM = Get-VM -Name "YourVMName" $VM | Update-VMConfiguration 5. Remove Residual Files Delete Remaining AVHDX Files: Once all AVHDX files are merged, ensure no residual files remain in the VM folder. Clean Up: Verify the folder contains only the base VHDX file and other essential configuration files. 6. Test Backups Again Retry the Veeam backup job to confirm it completes successfully. If issues persist, check Veeam logs for further insights. Additional Tips Cluster Awareness: Ensure all cluster nodes are synchronized, as mismatched states can cause checkpoint issues. Disk Space: Verify sufficient disk space is available on the storage where the VM resides, as merging checkpoints requires extra space. If the issue persists or the VM configuration appears corrupted, you may need to recreate the VM and attach the existing VHDX file to avoid data loss.
Carlos, I struggled understanding it also so I knew that it was a great topic for a video that might help others better understand these complex concepts.
I have a scenario here...if any one knows pls help me I have Base machine with 200 GB space and now I need to delete checkpoints which is of 190 GB.....is that possible.....????
I'm having a hard time understanding what each scenario would look like in the Hyper-V window. It would be helpful if you would show how each scenario looks on the Hyper-V window with the Checkpoint names corresponding to how you refer to them in the flowchart slide - e.g. "Checkpoint 2" instead of "VLC app installed" Ideally with a split screen BEFORE / AFTER for each scenario explained.
Finding deeply final solution requested. I appreciate your support. TANK YOU
Thank you for watching!
Very well done. Thanks for creating a very well put together lesson!
Thank you for watching!
Great video! Thank you for posting this.
Glad you enjoyed it!
Very well explained. This is awesome work.
Glad it was helpful!
Thumbs UP! Well done. Good explanation.
Thanks for watching!
Great video, exactly what I was looking for. One thing I didn't see though is why in the snapshots folder when I create a checkpoint (say 89F2E75D-D0B2-48B4-B2E8-4786683A8641), I also always get a empty folder with the same name? I am running Windows 10 Pro, so not sure if this is something new vs. when you posted the video.
thank you for your support! Let me look into it
Hello, thank you for explaining checkpoints, I have a VM which is hosted on Hyper-V Failover Cluster with 2 nodes. The total size of VM is now 11TB, I was taking backup through Veeam. Now backup is getting failed, as per Veeam there are multiple checkpoints (267) leftover in VM hard drive folder, but when I check on Hyper-V Manager console , I don’t see any checkpoint.
I tried to create new checkpoint then delete. Checkpoint is deleted but while merging process I have seen message checkpoint merging failed.
Please help to how to delete checkpoints leftover from HDD folder. Thank you
1. Identify and Confirm the Checkpoint Files
Check the VM Folder:
Navigate to the folder where the VM’s virtual hard disks (VHDX) are stored. This is usually in C:\ClusterStorage\VolumeX\VMName or wherever your VM resides.
Look for AVHDX files (differencing disks). These indicate leftover checkpoint files.
Verify Dependencies:
Use the Inspect Disk feature in Hyper-V Manager:
Open Hyper-V Manager.
Click Edit Disk and browse to one of the AVHDX files.
Select Inspect to see its parent disk. This helps understand the chain of dependencies.
2. Attempt to Merge Checkpoints Manually
Backup Critical Files:
Before making changes, back up the VM’s entire folder (including all VHDX and AVHDX files) to ensure recoverability.
Manually Merge the Differencing Disks:
Open Hyper-V Manager.
Navigate to Edit Disk and select one of the AVHDX files.
Choose Merge and follow the prompts:
Merge to the parent disk.
Repeat this for all AVHDX files, ensuring the chain merges correctly.
Restart the VM:
Once all differencing disks are merged, ensure the VM boots properly.
3. Check for Orphaned Checkpoints with PowerShell
List Checkpoints:
powershell
Copy code
Get-VMSnapshot -VMName "YourVMName"
If no checkpoints are listed but files remain, proceed with manual cleanup.
Force Remove Orphaned Checkpoints:
powershell
Copy code
Remove-VMSnapshot -VMName "YourVMName" -IncludeAll
This removes all associated snapshots.
4. Reconnect or Recreate the Virtual Disk Chain
Fix VM Configuration:
If merging fails, reattach the VHDX file directly to the VM:
Shut down the VM.
Remove the current disk from the VM settings.
Add the base VHDX file back to the VM.
Repair Configuration Files:
Use the following PowerShell commands:
powershell
Copy code
$VM = Get-VM -Name "YourVMName"
$VM | Update-VMConfiguration
5. Remove Residual Files
Delete Remaining AVHDX Files:
Once all AVHDX files are merged, ensure no residual files remain in the VM folder.
Clean Up:
Verify the folder contains only the base VHDX file and other essential configuration files.
6. Test Backups Again
Retry the Veeam backup job to confirm it completes successfully. If issues persist, check Veeam logs for further insights.
Additional Tips
Cluster Awareness: Ensure all cluster nodes are synchronized, as mismatched states can cause checkpoint issues.
Disk Space: Verify sufficient disk space is available on the storage where the VM resides, as merging checkpoints requires extra space.
If the issue persists or the VM configuration appears corrupted, you may need to recreate the VM and attach the existing VHDX file to avoid data loss.
LV is the man !
Thank you for watching!!
This sounds like a VM hosting account where you go back in time to fix issues like your website being hijacked or comprised Yes?
If the website server is a single server, yes. When you bring in load balancing and backend systems then it becomes more complex.
Thank you for the clear explanation, I didn't understand checkpoint in Hyper-V until I watched your video. It will help me a lot.👍
Carlos, I struggled understanding it also so I knew that it was a great topic for a video that might help others better understand these complex concepts.
Wait why does you shirt change all the time LOL Very nice explanation , it makes sense to me
This lecture took a long time!
I have a scenario here...if any one knows pls help me
I have Base machine with 200 GB space and now I need to delete checkpoints which is of 190 GB.....is that possible.....????
Sharan I explain in the the video how to identify the checkpoint components and how to successfully delete the checkpoints you desire.
Thank you
Thank you for watching
I'm having a hard time understanding what each scenario would look like in the Hyper-V window. It would be helpful if you would show how each scenario looks on the Hyper-V window with the Checkpoint names corresponding to how you refer to them in the flowchart slide - e.g. "Checkpoint 2" instead of "VLC app installed" Ideally with a split screen BEFORE / AFTER for each scenario explained.
Thanks for the good feedback, your point taken. Thanks for watching!