Published: 28.09.2026
Snapshots and backups both give you a way back, but they answer different questions. A snapshot captures the state of a disk at one moment, which makes it quick to take and useful before a risky change. A backup is a separate copy that should survive problems with the server itself. The client area of our VPS offers both, and this article explains when to use each one.
What a snapshot is
A snapshot records the state of a disk at a given moment. Because it works on the whole disk, it is quick to create and gives a fast way to return the server to a known state. Snapshots suit moments such as before a major upgrade, a change of operating system or an experiment with the configuration, because rolling back is usually much faster than rebuilding the server.
What a backup is
A backup is a copy of your data kept apart from the working system, ideally in a different place and under your own retention rules. It protects you against events that affect the server itself, such as accidental deletion, serious damage to its storage or an attack that changes files over several days. Backups take longer to restore than snapshots, but they give you control over where the copies live and how long they stay.
Comparing the two
- Creation: snapshots are quick; backups take longer on large disks.
- Restore: a snapshot returns the whole disk to its earlier state, while a backup can also return single files or folders.
- Location: a snapshot usually stays on the same platform as the server, so it does not replace an independent copy.
- Typical use: snapshots for a quick undo, backups for long-term recovery.
When to take a snapshot
- Before a major system upgrade or a change of distribution.
- Before editing a critical configuration file that could lock you out.
- Before installing software that changes shared system libraries.
- Before a test that you want to be able to undo afterwards.
When to rely on a backup
- For data you cannot recreate, such as databases, uploads and customer files.
- For recovery after damage that you may discover only days later.
- For copies you must keep for a long time, according to your own policy.
- For moving data to a new server or to a different location.
Restore tests
Neither a snapshot nor a backup is worth much until you have restored it successfully. Once a quarter, restore a recent copy to a separate test server or test disk. Start the services and check the website, the database and the logs. Write the steps down while you do it, because the notes will matter during a real emergency.
A simple routine
- Take a snapshot before any risky change, and remove it once the change is confirmed and you no longer need it.
- Run automatic backups of data and databases to separate storage every day.
- Check the logs of the backup jobs once a week.
- Restore a copy to a test system every few months.
Frequently asked questions
Is a snapshot a backup? Not by itself. A snapshot is useful, but it usually lives with the same server platform, so keep an independent backup as well.
How many snapshots should I keep? Keep the ones your recovery plan needs: a recent one before each change, and a longer history of backups for recovery.
Can I restore a single file from a snapshot? Snapshots work at the level of the whole disk, so single files are often easier to recover from a file-level backup. Check what the client area offers for your server.
