Backups
SES does not manage its own backups. Backing up is the responsibility of an external backup system / the hosting provider.
What needs to be backed up
The application data lives in a named PostgreSQL/Docker volume, independent of
the code in /opt/ses and the running containers. It survives deploys,
rebuilds and restarts. The external backup system should protect this data
store, for example:
| Approach | What it does |
|---|---|
Logical dump (pg_dump) | Consistent SQL dump of the database |
| Volume / disk-level backup | Snapshot of the named volume |
Backups are your responsibility
SES offers no in-app backup, dump, WAL-archive or off-site push mechanism. If data is lost and no backup exists, it cannot be restored.
Verification checklist
- A backup job exists and runs on a schedule
- Backups are stored off-site / on a separate host
- A restore test is performed regularly
- The
.env.secretsvalues needed to restore are stored safely