The schedule
Backups are taken by the platform’s scheduler, which checks every couple of minutes whether one is due, so a daily backup at 03:00 UTC starts shortly after 03:00. If one was missed while nothing was running, the next check takes it.
How old backups are removed
After each scheduled backup, Pawabase goes through the scheduled backups from newest to oldest and removes any that is beyond the count in Keep the last or older than Keep for (days), whichever applies first. Pinned backups and backups you took by hand are never removed by the schedule.Back up now
Back up now takes one immediately. Give it:
It appears under Saved backups next to the scheduled ones.
Pin a backup
Pin a backup to keep it until you unpin or delete it. Pin one before a release, a risky migration, a large import or a restore. You can rename a backup or change its note at any time.Check a backup
Verify reads a saved backup back and checks it the way a restore would: that it can be read, its checksums match, and which parts it contains with a summary of their contents. Verify important backups, for example the one you pinned before a migration.Download a saved backup
Download gives you the backup as one file, to keep somewhere else or to restore into another environment or project. A backup can contain password hashes and personal data: store the file as carefully as the database itself.From code
A sensible plan
- Daily automatic backups of everything, keeping the last 14 to 30.
- Hourly backups for environments with frequent important changes, keeping the last 24 to 48.
- A pinned backup before every release or risky change.
- A download of an important backup kept outside Pawabase.
- A test restore into a non-production environment every quarter. A backup you’ve never restored is a hope, not a backup.