Snapshot vs Backup
What a Snapshot Is and How It Differs from a Backup
Snapshot vs backup is a common comparison, and the two are often confused. A snapshot is a point-in-time record of a disk, volume or virtual machine that lets you roll back to the state it captured. A backup is a separate copy of data, kept so it can be restored after loss.
The key difference is where the copy lives and what it depends on. A snapshot is usually stored on the same storage system as the original, and it records only the changes since the snapshot was taken, so it relies on the original data and the platform that holds it. A backup is a self-contained copy that can be restored even if the original storage is gone.
Why Snapshots Are Not Full Backups
Snapshots are very useful, but they have limits that matter when something goes seriously wrong:
- Shared fate. If the storage system fails, is corrupted or is deleted, the snapshots kept on it can be lost too.
- Dependency. Snapshots are linked to the original disk. Damage to the base can make a snapshot chain unusable.
- Short life. Snapshots are often kept for days rather than months, and platforms may remove old ones automatically to save space.
- Limited scope. A snapshot captures the disk state, but it is not a separate, browsable copy of individual files, and it may not capture settings held outside the disk.
Snapshots are also taken at the storage level, not by the application. A busy database may be in the middle of a write when the snapshot is taken, which can produce a copy that needs repair. That is one reason databases usually need their own approach, covered in database backups.
A Snapshot Rollback Compared with a Ransomware Attack
A site owner takes a snapshot of a virtual private server before upgrading its operating system. The upgrade goes wrong and the server will not boot. Rolling back to the snapshot fixes the problem within minutes, which is exactly what snapshots are good for.
Now imagine the server is hit by ransomware that encrypts every file, including the snapshots kept on the same storage. The snapshot solved a bad update but not an attack that reached the storage behind it. An independent backup, stored offsite, would still hold a clean copy.
Using Snapshots and Backups Together
The two tools work best side by side. Snapshots give a fast way to undo a risky change, such as a software update, a configuration edit or a migration. Backups give a reliable way to recover from the loss of the system or the storage it lives on.
A practical pattern is to take a snapshot before a planned change, remove it once the change is confirmed, and keep regular independent backups running. The 3-2-1 backup rule describes how many independent copies to keep. A snapshot on the same storage normally does not count as one of them.
Frequently asked questions
Is a VPS snapshot a backup?
A VPS snapshot is not a full backup on its own. It is usually stored on the same platform as the server and may be removed automatically. It is useful for quick rollbacks, but a separate copy stored elsewhere is needed to protect against platform failure, account loss or attacks.
Can I restore a website from a snapshot?
Often you can, if the snapshot is still available and the storage it depends on is intact. A restore from a snapshot usually replaces the whole disk, so any changes made after the snapshot was taken are lost. Confirm that the snapshot is complete and test a restore before you rely on it. For full server copies, see bare metal backup.