The most common use case for checkpoints is the creation of point-in-time copies before you update the operating system or application on your VMs. The same principle works for virtual machines. You can use the previously made restore point to discard the latest changes and launch a fully functional operating system. That restore point comes in handy when, for example, a driver or OS update installation goes wrong. In case you are not a virtualization pro, you can find it easier to perceive a snapshot as a regular restore point in Windows OS. Whenever necessary, you can roll back a virtual machine to the moment when a snapshot was taken. When a checkpoint is created, the hypervisor “memorizes” the state of a VM’s OS, apps, RAM data, and other objects at that particular moment. In simple words, a checkpoint is a point-in-time copy of a virtual machine. What Is a Hyper-V Checkpoint and How Is It Used? What is a checkpoint in Hyper-V? Is a snapshot different from a checkpoint? Can checkpoints and snapshots be treated as backups? How to reliably protect data in a Hyper-V environment? In this post, we’ll answer those questions. The technology of snapshots is among the main advantages of virtualization solutions. Organizations of all types and sizes use virtual machines (VMs) because of the functionality and performance benefits they bring.

Drive snapshot 1.4