Backups
Schedule backups of one application's files and database to an off-server destination, and see every backup that has run.
Backups is this application's slice of the server's backup system: what to copy, how often, how many to keep, and where it goes.
The full guide
This page covers the application tab. For storage destinations, the history across every application, and restoring, see Backups & restore.
Until a schedule exists the screen says the only thing worth saying: "If the server is lost, so is this application."
Set up a schedule
What to back up — Files and database ("Safest — a full restore"), Files without the database, or Database without the files.
When it runs — leave Back up automatically on and set How often and At what time. Times are UTC, and the dialog says so next to the field.
How many to keep — the retention count. The dialog translates it as you
type: 7 is "About 7 days of history. Older ones are deleted."
Where it is stored — pick a connected storage destination.
Optionally open Exclude files or folders to skip caches and other things not worth copying, then Save backup settings.
A summary line above the buttons restates the whole thing before you commit — "my-blog · Files and database · Daily · keep 7".
A destination comes first
With no storage connected, Save backup settings stays disabled and the dialog says "Backups need somewhere to go. Connect a storage destination first." Set up storage takes you to Integrations → Storage; Check again re-reads it without losing what you have filled in.
This is deliberate. A backup written to the same disk as the application is not a backup.
Recent backups
Once a schedule runs, each backup appears with its status, backup type, when and size. All backups opens the server-wide history filtered to this application, which is also where restores are run from.
The dashboard mirrors the headline: Not protected / Last backup — Never until the first one succeeds.