#RAPID RECOVERY POWERSHELL COMMAND HOW TO#

I guess this is to protect people from trying to delete one by mistake when they see one during backups. The fact is youвЂ™re not supposed to have to do this, so the functionality is not there. IвЂ™m not convinced the fact that you canвЂ™t do it in the GUI is to be considered a bug as some would suggest. The good news is that this can be done via PowerShell. But you donвЂ™t have to do this! As a matter of fact you should avoid this if possible at all. I have discussed this process in blog posts 3 Ways To Deal With Lingering Hyper-V Checkpoints Formerly Known as Snapshots and Manually Merging Hyper-V Checkpoints. Some people turn to manually merging these checkpoints. When we look ad the files we see the traces of a Windows Server 2012R2 Hyper-V backup You can read more about that in my blog posts Some Insights Into How Windows 2012 R2 Hyper-V Backups Work and What Is AutoRecovery.avhdx all about?. ItвЂ™s there as part of the backup process. You can right click on the checkpoint but you will not find an option to apply or delete it.This is a recovery snapshot and youвЂ™re not supposed to manipulate this manually. You see checkpoint with a вЂњoddвЂќ icon that looks like this

#RAPID RECOVERY POWERSHELL COMMAND HOW TO#

WeвЂ™re going to show you how to remove lingering Backup checkpoints from a Hyper-V Virtual Machine that where not properly removed after a backup on Windows Server 2012 R2 Hyper-V.

There are many reasons for this, but thatвЂ™s not the focus of this blog post.

Sometimes things go wrong with a backup job.

Rapid recovery powershell command