Skip to content

How backups work

CloudPress backs up every site automatically, and you can also take your own backup at any time. This page explains how those backups are made — what gets captured, how your files and database are backed up separately, and how the automatic schedule and retention work. If you're looking for the steps to take, restore, download, or delete a backup, see Backing up and restoring a site.

The short version

  • Your site's files and database are backed up separately.
  • Backups run automatically, once a day. You can take extra backups on demand whenever you like.

Sites are made of volumes

Every site is built from one or more volumes — independent pieces of storage. A typical WordPress site has two:

Volume What it holds
WordPress Data Your WordPress install: core files, themes, plugins, and uploads (the media library).
Database Your site's database — posts, pages, settings, users, and everything else WordPress stores in MariaDB.

On the Backups page in your dashboard (titled Backup & Volume Management), each volume gets its own card, and each card has its own list of backups. You'll see a WordPress Data card and a Database card, each showing its Current Data Usage, Backup Count, Backup Usage, and Backup Schedule. For more on volumes and how a CloudPress site fits together, see The platform model.

Restore one volume at a time

Restoring works on one volume at a time — for example, you can roll your database back to last night without touching the files you've uploaded since. To return your whole site to an earlier point, restore both the WordPress Data and Database volumes from backups taken close together.

How the database is backed up

Your database is backed up as a whole, not as a .sql file. You don't generate, store, or import .sql files for routine backups and restores. If you need a portable .sql export, for example to move your data elsewhere, export it yourself with the standard WordPress export tools or a database client.

How the WordPress files are backed up

The WordPress Data volume — your core files, themes, plugins, and uploads — is captured as a full backup of those files. Restoring it returns that volume's contents to the way they were when the backup was taken.

Automatic schedule and retention

Backups run automatically, once a day, for each volume — the daily schedule is fixed, with nothing for you to set up or configure. Each volume's card shows it under Backup Schedule.

Automatic backups keep recent daily recovery points, then weekly and monthly ones, so you keep recovery points at a range of ages. Backup Count shows how many backups a volume has, and Backup Usage shows the space they use. Don't rely on a specific old automatic backup still being there months later: if a moment matters, such as right before a big plugin update, take a manual on-demand backup and, for a copy of your own, download the archive. Both are covered in Backing up and restoring a site.

Manual (on-demand) backups

In addition to the automatic schedule, you can take a backup yourself at any time from the Backups page — for instance, just before updating a plugin, theme, or WordPress itself. Manual and automatic backups appear together in the same per-volume list and can be restored or downloaded the same way; in the list, automatic backups are marked with a calendar icon and manual ones with a person icon. See Backing up and restoring a site for the steps.

Restoring overwrites the current contents of that volume

Restoring a backup replaces everything currently on that volume with the contents of the backup — anything created or changed since that backup was taken is lost. If you're not sure, take a fresh manual backup first so you can get back to where you are now.