Snapshots vs backups: what's the difference
Snapshots and backups are often confused, and hosts list them on the same line of a plan. They are different tools. A snapshot quickly takes a server back an hour after a failed update. A backup brings your data back when the server, the disk or the account is already gone. Below: how they differ, what each protects against and how to combine them on one VPS.
The short answer. A snapshot is an image of the server's disk at a given moment. It is kept in the same storage system at the same host and is created in seconds. A backup is a separate copy of the data in another place, preferably at another provider. You take a snapshot before every change and a backup on a schedule, every day. One does not replace the other.
Side-by-side comparison
| Host snapshot | Backup | |
|---|---|---|
| Where it is stored | In the same storage system as the server's disk | Somewhere else: another server, object storage, another host |
| How fast it is created | Seconds, the server keeps running | Minutes to hours, depending on the volume |
| What it restores | The whole disk | The whole server, a single database or one file |
| Survives a storage failure at the host | No | Yes |
| Survives deletion of the server or account | Usually not | Yes, if it is kept at another provider |
| Database consistency | As after a sudden power cut | Full, if the database is exported as a dump |
| How it is billed | Per gigabyte per month, or included in the plan | Storage plus traffic |
How a snapshot works
The storage system does not copy the whole disk at the moment of the snapshot. It records the disk's state and from then on saves only the blocks that change. That is why a snapshot is created almost instantly and takes up almost no space at first. But there is a flip side: the snapshot does not exist separately from the original disk and from the storage that holds it. If that storage fails, both the disk and all its snapshots are lost.
The second limitation is lifetime. As long as a snapshot exists, the storage keeps a chain of changes for the disk. Long chains on formats such as qcow2 and LVM slow down writes and take up more and more space. A snapshot is a tool for hours and days, not months.
Snapshots of a running server and databases
A snapshot of a running server captures the disk in the state it would be in after a sudden power cut. Data that programs held in memory and had not yet written to disk does not make it into the snapshot. PostgreSQL and MySQL with InnoDB are designed for this case: on startup they recover from their own log. But that is only guaranteed if the snapshot is taken simultaneously across all the disks holding the database's data and log.
A guest agent makes snapshots more reliable. If qemu-guest-agent is installed on the server and the host uses it, the file systems are frozen for an instant before the snapshot and all pending writes are flushed to disk. Proxmox does this, for example: its documentation describes the mode for backing up a running machine as the one with the least downtime at the cost of a small risk of inconsistency, which freezing through the guest agent reduces. For a database a separate dump is still more reliable: you can restore it on any server and any version of the system.
What hosts offer
In the accsly catalog on 14 November 2026, backup terms are recorded for 1,406 of 1,857 VPS hosts, and 285 of them explicitly mention snapshots. The terms vary widely. A few examples, as recorded in the catalog from the hosts' own pages:
- BuyVM: free snapshots, daily backups for an extra fee;
- Bandwagon Host: free automatic backups and snapshots;
- REG.RU: automatic VPS backups and snapshots, storage at ₽0.0072 per gigabyte per hour, up to ₽5.26 a month;
- Fotbo: backups, snapshots and images at €0.10 per gigabyte per month excluding VAT;
- RareCloud: cloud server snapshots at €0.05 per gigabyte per month;
- MojoHost: snapshots at $0.03 per gigabyte per month, backups only as a paid service: by default once a week with 28-day retention;
- Cherry Servers: 50 GB of backup space free for all virtual servers, daily backups kept for 7 days.
At these prices, a snapshot of a 50 GB disk costs from $1.50 (MojoHost) to €5 (Fotbo) a month. That is not much, but forgotten snapshots pile up for years. Check your control panel to see how many you have right now.
What each one protects against
| What happened | Snapshot | Backup |
|---|---|---|
| A system or application update broke the server | Yes, rollback in minutes | Yes, but slower |
| An important file was deleted a week ago | Only if a week-old snapshot still exists | Yes, a single file can be restored |
| The host's storage failed | No | Yes |
| The server was hacked and the data encrypted | No, if the attacker has access to the control panel | Yes, if the backups cannot be deleted from the server itself |
| Account blocked, host shut down, server deleted for non-payment | No | Yes, if the backup is at another provider |
| Moving to another host | Usually not: the snapshot cannot be downloaded | Yes |
Most hosts delete snapshots together with the server. If you are about to delete a server thinking "the snapshot is still there", check the host's terms first.
How to combine them on one VPS
- A snapshot before every change: a system update, a database version upgrade, a large data migration. If all went well, delete it a day or two later. How to run updates with a way back is covered in the article updating a server without downtime.
- A daily backup of files and database dumps to storage at another provider. Tools, schedules and the 3-2-1 rule are covered in the article VPS backups.
- A restore test once a month: deploy the backup to a temporary server and open the site. A server with hourly billing will cost next to nothing for this.
A separate server with a large disk is a convenient place for backups; see the selections VPS for backups and VPS with large storage. If you run your own hypervisor, it takes the snapshots and backups of your machines itself; see the selection servers for Proxmox.
What to ask your host
- Where are snapshots and backups stored: in the same storage, in the same data centre or separately?
- How many snapshots can I keep, and how much does a gigabyte of storage cost?
- Are automatic backups made, how often, and for how many days are they kept?
- Is a guest agent used to freeze the file system before a snapshot?
- Can I download a snapshot or disk image and deploy it somewhere else?
- What happens to snapshots and backups after the server is deleted?