Virtual machine checkpoints (formerly known as virtual machine snapshots) capture the state, data, and hardware configuration of a running virtual machine. In Windows Server 2012 R2, virtual machine snapshots were renamed to virtual machine checkpoints in Hyper-V manager to match the terminology used in System Center Virtual Machine Management. Checkpoints provide a fast and easy way to revert the virtual machine to a previous state. For this reason, virtual machine checkpoints are intended mainly for use in development and test environments. Having an easy way to revert a virtual machine can be very useful if you need to recreate a specific state or condition so that you can troubleshoot a problem.
We have got a few options when it comes to checkpoints; create, apply and delete them.
The last two always confuse me and I wanted to test it myself in my lab environment. I created a VM server 2012 R2 and just right clicked and choose create a checkpoint.
Before the checkpoint
After the checkpoint;
Now let me change some settings on the server; Background changed and a folder and a file created on the desktop.
APPLYING the CheckPoint; (I think the name is misleading)
Clicked on that…
So looks like if you want to just in case keep the changes on a different chackpoint, you can create a new one but I don’t want it now as I want to see what will happen just for applying.
VM in the background greyed out and status showing as starting..
And then a few seconds later status showing as RESTORING….
Looks like everything taken back to the beginning and I still got the checkpoint. So All the changes I have made have been deleted.
And now what will happen if I choose DELETE CHECKPOINT …
Again i have made some changes.
Chose delete checkpoint…..
It has deleted the checkpoint and also copied and saved all the changes on to the original VM.
No snapshots in the folder where they normally saved.
Common Issues with deleting;
Deleting snapshots, but they failed to merge because there is not enough space on the disk (error 0x80070070)
Export the virtual machine from the current location.
Import the virtual machine to a location that has sufficient storage space. The location should be a different volume on the same host to avoid configuration problems.
If the version of Hyper-V is earlier than Windows Server 2008 R2, turn on the virtual machine and then shut it down, to trigger the merge process at the new storage location.
If you want to move the virtual machine back to the original location, free up additional space. Then, import the virtual machine back to the original location.
Very useful link from Microsoft….