Merging Orphaned Veeam Snapshot

Merging Orphaned Veeam Snapshot

This is very much a reminder for myself on how to do this as, thankfully, it doesn't rear its head as a problem too often.

The scenario is this: You're clicking through the nodes in your server farm, looking at what the various VMs are doing and you realise that you have several with a snapshot from several weeks ago that hasn't re-merged. If you're really lucky you'll have a chain of several with none sequential dates. Hyper-V manger won't merge them back in. Neither will Veeam. What fun...

Thankfully it's pretty easy to fix - I came across this post from several years ago, and it remains relevant now. Thank you Workinghardinit.

This is a very nice, easy fix.

Admin powershell, logged on as someone with sufficient rights to be removing production Hyper-V checkpoints. First we need to find our orphaned snapshots:

Get-VMSnapshot -ComputerName "MyHyperVHost" -VMName "VMthatwontmerge"

Resulting in:

Now we just need to use the ever-awesome pipe command to feed these checkpoints in to a removal cmdlet:

Get-VMSnapshot -ComputerName "MyHyperVHost" -VMName "VMthatwontmerge" | Remove-VMSnapshot

Sit and wait for the merge to complete and done!

I love an easy solution.

Rob Stevens

Rob Stevens

Tyne and Wear, UK