Backups
Your data is backed up automatically and you can trigger a backup on demand. The Backups page lists your project’s restore points and applies the one you pick.
What is backed up
Every backup holds the structure and the data of your project schema, in a compressed file. It covers the project, never the whole platform.
- Manual backup: an immediate restore point, useful before a migration or an import.
- Automatic backups: added by the platform over the retention window shown at the top of the page.
- Pre-restore rollback point: created automatically before a dump is applied, when the option is active.
Read the list
Each row shows the date, the type, the size and the available action. The retention in force appears above the list: it decides how long a restore point stays available.
Restore
A restore replaces all data in your project schema with the contents of the chosen backup. Confirmation requires the exact project name: this is a destructive action, deliberately hard to trigger by mistake.
- Check the date and the size of the file before confirming; a recent manual backup is often the best pick.
- During the operation the screen follows its progress; at the end, the rollback point created beforehand is reported.
- When restore is disabled on the platform, backups are still listed and created, but the destructive apply is not offered.
Point-in-time restore
When continuous backup is active, the page shows the latest available point. That kind of restore brings the PostgreSQL instance back to a precise instant: it affects every project living there, not just yours. Use support for this case.