Backup policies
A backup policy says when backups are made by themselves, how long they are kept, and where they go.
The organization’s defaults
Section titled “The organization’s defaults”Settings → Backup policies has one policy per environment type: dev, staging and production. An environment without a policy of its own follows the one for its type. Until you change one, the platform’s default applies.
To change one, open it, edit the form and press Save policy.
What a policy holds
Section titled “What a policy holds”| Field | What it is |
|---|---|
| Make backups on this schedule | Off: no automatic backups for this type |
| Frequency | A preset, or Custom with a Cron expression |
| Timezone | The schedule’s hours are read in this timezone |
| How long backups are kept | How many daily, weekly, monthly and yearly backups to keep |
| Include the filestore | Also back up attachments and images, not only the database |
| Storage | The organization’s default, or one you name |
| Notifications | When a backup is made, When a backup fails |
Frequency presets: every day at midnight, at 02:00 or at 03:00; every 6 hours; every 12 hours; every Sunday at 02:00. A custom cron expression is minute hour day month weekday, and the minute must be one number.
The platform starts the backups that are due every minute, and removes the ones whose time is over every hour.
A policy for one environment
Section titled “A policy for one environment”- Open the environment’s Backups tab and find the Backup policy card.
- Choose Use a policy of its own, fill in the form and press Use this policy.
It applies from the next run on. Back to the default makes the environment follow the organization’s policy again.
Compliance
Section titled “Compliance”Backups → Compliance lists every deployed environment with its Last finished backup and Next scheduled run. An environment with a finished backup from the last 24 hours is Protected; the others Need attention, with the reason in words.

