How backups use disk space (incremental snapshots explained)

For server administrators · Updated 2026-10-29

On this page
  1. Where backups are stored
  2. Why snapshots take little space
  3. What databases cost
  4. What full backup archives cost
  5. How to free space
  6. Good to know
  7. Common questions

Backup jobs to This server (incremental) are cheap in space for files and email, and full-size for databases. Knowing the difference helps you choose how often to copy and how many copies to keep.

Where backups are stored

WhatWhere on the server
Snapshots (backup jobs to this server, Snapshot now)/backup/snapshots/<account>/<YYYYmmdd-HHMMSS>/
Full backup archives (Create backup, archives kept here)/backup/<account>/<account>-<date>-<time>-<id>.tar
Temporary work space while a backup or restore runs/backup/.staging/

Backups belong to the system, not to the customer, so they do not count against the account's disk quota.

Why snapshots take little space

Each snapshot folder holds the account's files (home/), mailboxes (mail/) and database dumps (mysql/, postgres/). A file that has not changed since the previous copy is not stored again: the new snapshot points to the same data on disk (a hard link). So:

  • The first snapshot of an account takes about as much space as the account.
  • Every later snapshot adds only the files that changed or are new.
  • Every snapshot is still complete. Deleting an old one never damages the others.

The New data column on Daily Snapshots (section Websites) shows how much space each snapshot added.

What databases cost

Database dumps are made fresh every time and compressed. Each copy of a database takes its full compressed size, even if nothing changed. A job that copies databases every 15 minutes and keeps 96 copies keeps 96 compressed dumps per database. Check the size of your largest database before choosing a short interval and a high number of copies.

What full backup archives cost

An archive is a complete compressed copy every time. Seven archives of an account take about seven times the compressed size of the account. That is why archives suit external destinations, where they do not use this server's disk. A job to an external destination needs free space in /backup/.staging/ for one account's archive while it is built and sent.

How to free space

  1. Open Backup Jobs (section Websites) and lower Copies to keep per account in a job. The extra copies of each account are removed after that job's next successful copy of it.
  2. In Full Backups, click Delete next to archives you no longer need.
  3. Move long-term copies to an external destination.

The Destinations list on Backup Jobs shows the free space of the disk next to This server.

Good to know

  • Snapshots cannot be deleted one by one in the panel. They are removed by their job's Copies to keep per account.
  • Copies of a deleted job are no longer removed automatically. They stay restorable and keep using space.
  • Snapshots made by hand are kept apart: the newest 14 per account by default.

Common questions

Why is the first snapshot so big?

It is a full copy. Later snapshots only add what changed.

Does copying files every hour fill the disk?

Usually not: only changed files take new space. Busy sites that rewrite large files (logs, caches, uploads) add more per copy.

Is /backup on its own disk?

It is a folder on the server. If your server has a separate disk mounted at /backup, backups use that disk.

Was this article helpful?

Still stuck?

Ask the AI about your exact situation — it answers from this knowledge base — or contact us.