Skip to content

Backup policies

A backup policy is per site. It decides when backups run, what each one holds, where the archives go, and how long they are kept before ConstellaWP deletes them from your storage.

Open the site → Backups → Settings. You need at least one destination first. Scheduling requires a paid plan: on the Free plan, backups are taken by hand from the Backups tab.

Automatic backups turns the whole schedule on or off without losing its settings.

Turn on as many frequencies as you need: Hourly, Daily, Weekly and Monthly. Each one has its own settings:

Setting What it does
What it holds Full (every file and the whole database), Changed files + database, or Database only
Start time The time of day it starts. Hourly runs every hour
Day of the week Weekly only
Day of the month Monthly only, from the 1st to the 28th, the last day every month has
Keep for How many days its backups are kept, from 1 to 365. See Retention
  • Hourly is part of the Team plan. It never takes a full backup: rebuilding the whole site every hour would load the server and your storage for nothing.
  • At least one frequency has to take a full backup. Database-only and changed-files backups are restored on top of a full one, so on their own they cannot put a site back.
  • When several frequencies fall due at the same time, one backup is taken: the one that covers the most. A full backup already holds the database, so a daily database backup and a weekly full both due on Sunday give one full backup, and both frequencies count as done.

A common setup for a site that is worked on: a weekly full backup, plus a daily database-only or changed-files backup in between.

One timezone applies to every frequency of the site. When a site has no schedule yet, the field starts from the timezone in your Settings → Preferences.

Each site starts its backups a fixed number of minutes after the time you chose, the same every time, so that the sites ConstellaWP looks after do not all begin at once. The settings page shows that offset under the timezone. ConstellaWP checks for due backups every five minutes. If a backup of the site is already running, the next one waits for it rather than being skipped.

Each frequency keeps its backups for its own number of days: daily backups 10 days and monthly ones 120, for example. When you turn a frequency on for the first time, it starts from 2 days for hourly, 30 for daily, 90 for weekly and 365 for monthly.

  • One backup that settles several frequencies is kept as long as the longest of them. On the 1st of the month, the daily and the monthly backups above are one archive, kept 120 days.
  • Manual and pre-update backups sets how long a backup taken by hand from the Backups tab, or with Take a full backup first before updates, is kept: 1 to 365 days, 30 by default.
  • A safety backup, taken automatically before a restore, is kept 7 days.
  • On a site without a policy, backups taken by hand are kept until you delete them.

In the backups list, a badge names the frequencies a scheduled backup settled, so you can tell why one outlives its neighbours. Its Expires date is set when the backup is taken: a new retention applies to the backups taken from then on, and an existing backup keeps its date.

Once a day, a purge removes each expired backup from every destination it was copied to, then its record. ConstellaWP must still be able to reach the destination to delete the archive.

A database-only or changed-files backup needs the full backup it is restored on top of, so the purge keeps that full as long as a backup that depends on it remains, even past its own expiry. If a lighter frequency is kept longer than every full one, its fulls stay in your storage that long too: the settings page warns you when that is the case.

A policy copies every backup to up to three destinations, uploaded one after the other. A copy with a second provider is what survives a bucket being emptied or an account being lost. Restores read from the first destination, in the order you set, that still holds the archive.

An older agent uploads to one destination only: update the ConstellaWP Agent to add more.

Encrypt archives (recommended) seals each archive on your server before it leaves it, so whoever can read your bucket cannot read your site. The first time, download your Recovery Kit: it holds the private key to your archives, and ConstellaWP deletes its copy as soon as you download it. Archives stay restorable from ConstellaWP as usual. The kit is what opens them with the open-source age tool if you ever stop using ConstellaWP.

One path per line, left out of the archive: build artefacts, source videos, a cache no plugin owns.

Line Leaves out
node_modules Any file or folder with that name, at any depth
*.gz Every file matching the pattern
/my-files/ Only that folder at the root of the site

An excluded path is not restored, and a restore leaves it untouched on the site.

Danger Zone → Delete Backup Policy removes the schedule only. It does not delete the archives already stored.