A Hyper-V Snapshot, now called a Hyper-V Checkpoint beginning with Windows Server 2012, is a fundamentally different thing than a Hyper-V backup. Hyper-V backup software works similar to file server backup software but is specialized in how it handles virtual machine data.
Hyper-V backups are used for disaster recovery and are hence full and portable copies of a Hyper-V virtual machine, whereas Hyper-V Snapshots are simply a frozen state of a VM, stored together with the VM data.
What are Hyper-V Snapshots?
Hyper-V Snapshots are great for development and testing, but not recommended for production use by Microsoft.
In order to freeze the VM's state you create one or more Hyper-V snapshots. Then, when you want to go back to an earlier state, simply delete the snapshot and Hyper-V merges the related files together and switches back to where the VM used to be in the past.
Hyper-V Snapshots a.k.a. Checkpoints use differencing disks internally to preserve the state of virtual disks in the past. Say you have a 1 TB VHDX file which is your VM's hard drive. When a checkpoint is created, an AVHDX file is created. It holds all the changes that would have been written to the virtual disk, but because a checkpoint is now running, the original VHDX remains unchanged and instead all updated and new data blocks are written to the AVHDX file. The AVHDX file usually resides right next to the VHDX file in the same folder; however, it must reside on the same server.
Hence, when disaster strikes and the hard drive is damaged, you would lose all your information. Even if you had stored the VHDX on a different drive, the VM wouldn't boot anymore since the configuration now points to non-existing or damanged snapshot files. Hard drive damage is only one of many scenarios leading to data loss. RAM corruption, for example, is another common one.
How are Hyper-V Backups Different?
Hyper-V backups are a totally different thing. A Hyper-V backup software, such as BackupChain is installed on the Hyper-V host and pulls a copy of the VM files while the virtual machine is running, without affecting the VM. The backups are stored on a different disk or another server on the network, such as a NAS server, or an FTP site. By storing backups elsewhere you eliminate data loss risks resulting from local hardware damage.
After a disaster or whenever you need a clone of your VM you can restore the Hyper-V backup back to the original server or to a new host. A snapshot cannot be moved to another server, unless you are using Hyper-V quick or live migration features. Obviously VMs can only migrate on a functioning network and are not suited as a disaster recovery solution.
Hyper-V backups are much more powerful than snapshots. Below are some interesting facts:
- They use less space by using deduplication and data compression.
- They don't affect virtual machine performance at all, once the backup is complete.
- Snapshots slow down the entire host for as long as you are using snapshotted VMs
- Snapshots use local storage
- Backups use backup storage elsewhere
- Snapshots are lost when the VM's disk is damaged
- Backups safer since they are independent and stored on another device
- Backups can be restored as a cloned VM, and run side-by-side to the original
- Snapshots need to be deleted in order to return to a previous state. No cloning is possible
- Hyper-V backup software is capable of backing up VMs and their snapshots, too
IT Professionals choose BackupChain to backup and restore Hyper-V virtual machines. Discover it for yourself by downloading our 20-day, fully functional trial.