Smaller, single-file database backups

Database backups are now written as a single compressed file per database rather than a dump inside a .tar.gz. A backup now needs about one compressed copy's worth of free disk instead of room for the dump and its tarball together. Postgres dumps also stop being compressed twice.

New backups are named:

• PostgreSQL: <database>.dump, restore with pg_restore
• MySQL: <database>.sql.gz
• Redis/Valkey: <database>.rdb.gz
• SQLite: <database>.sqlite3.gz

Existing databases keep their current .tar.gz backups until you switch them. To switch, open the database, choose Backups → Configure and click Save. You don't need to change anything. New databases and backup settings use the new format automatically. If you use the API or MCP, updating a database's backup configuration does the same.

If you have scripts that look for *.tar.gz files in your bucket or in /home/deploy/backups, update them before you switch.

Each database page now has a How to restore this backup section under Backups, with the exact commands for your engine and server. Docker clusters get docker exec versions. Older .tar.gz backups still work and get their own restore steps.