Taking storage snapshots has proven to be an extremely effective feature for those working in virtual environments. However, snapshot technology might backfire if used without proper knowledge of how it works, what pros and cons it entails, and how snapshots can function in your IT infrastructure. This blog post describes how storage snapshots are used in Hyper-V virtual environments and presents you with a list of the top 10 things that you should know about Hyper-V snapshots.
What is a Hyper-V snapshot?
A Hyper-V snapshot (currently known as a Hyper-V checkpoint) represents a point-in-time copy of a selected virtual machine (VM), which allows you to capture the VM state, data, and its hardware configuration at a particular moment. Hyper-V snapshots are primarily used to revert a VM to its previous state in case any unnecessary changes were applied to the VM and the user wants to discard them. The main advantage of this technology is that Hyper-V snapshots can be easily and rapidly taken online and offline, without causing any workflow interruptions within a running VM. In Hyper-V, multiple snapshots can be created, deleted, and applied to a single VM.