Backups

A full copy of your app's data at one moment, made on a schedule or on demand, kept on disk or in a storage bucket, and restored in about a second.

A backup is one zip file that holds your app's whole data at one moment: the database, and the uploaded files when they live on the server's disk.

How a backup is made#

One consistent moment. The app copies its database and its files while it holds writes for an instant. Every file a record names is in the copy, and the app keeps serving during the backup.
On a schedule, for example every night. The app keeps the newest backups up to a number you choose and deletes the older ones.
On demand, by an admin of the app.
Where they live: on the server's disk, or in a storage bucket compatible with Amazon S3. A bucket keeps the backups outside the server.

When the files themselves live in a bucket, they stay there, and the backup holds the database only.

Restore#

A restore checks the backup first, while the app still serves: every entry is read and checked, and the database inside is opened and tested. Only then the app stops, saves what it replaces as one more backup, swaps the data in, and starts again, in about one second. If any check fails, nothing changes.

A backup made by PocketBase restores too. See Coming from PocketBase.

Not available yet#

A mail to the admins when a scheduled backup fails. Today the failure is written in the app's log.

This page as markdown