Skip to main content

How backups work

DBHost uses pg_dump piped through gzip to create compressed SQL backups and stores them off-host in AWS S3 eu-north-1 as timestamped .sql.gz files. Whether a database gets a daily scheduled backup depends on its environment: production always does, staging does by default, development and other databases use the choice made at creation, and previews have none unless you choose daily. Logical backups are kept for 30 days. See Backups and retention for the full policy. Scheduled jobs run throughout the UTC day with no single guaranteed backup time. The dashboard shows a backup as complete only after the file has been verified.

Triggering a backup

  1. Go to your database detail page and open the Backups tab
  2. Click Back up now. The same button is on the All backups page
The backup is queued as an operation. The dashboard polls its status and updates the list without requiring a page refresh. On-demand backups work on every plan, including when the scheduled backup choice is none.

Viewing backup history

The backups page shows all available backups with:
  • Filename (timestamp-based: YYYYMMDD_HHMMSS.sql.gz)
  • Size (compressed)
  • Created at (UTC)
  • Actions — download, delete and restore, depending on your role
Developers can view and download backups. Owners and admins can trigger, delete and restore backups. Restoring a database with managed or additional roles, and cloning a backup, is limited to the database owner.

Restoring from a backup

Choose Restore on a verified backup to replace the database’s current contents with that backup. DBHost restores into an isolated copy, verifies it, takes a fresh backup of the current database and then switches over. Open connections are dropped during the cutover. Databases with managed SQL roles and databases that opted in to additional roles restore from the same Restore action, available to the database owner on DBHost-produced verified backups. The dashboard reserves the restore and advances it until it finishes; keep the page open. Role usernames and passwords stay the same. If the restore stops, press Restore again to continue the same operation. The managed restore API does the same from your own tooling. See Restore from a DBHost backup for every path.

Cloning a backup

On a database with managed SQL roles, the owner can choose Clone to new database on a verified backup. DBHost creates a separate database from that backup with its own credentials and leaves the original untouched. The clone counts toward your plan’s database limit.

Restore your own file

DBHost does not restore uploaded .sql, .sql.gz, .dump, or .backup files. The upload endpoints return 409 CUSTOM_RESTORE_UPLOAD_DISABLED. Import your own dump with psql or pg_restore using the owner role over verify-full TLS:
Restore your own dump covers .sql.gz files, grants and ownership repair.

Downloading and deleting backups

  • Use Download to fetch the exact .sql.gz file. The file may be served directly from S3 through a short-lived link.
  • Use Delete to remove a backup file from the available backup list. Older S3 versions may remain until storage retention expires.
Deleting a backup cannot be undone from the dashboard or API.

Deleted databases

When a database is deleted, its verified deletion backup stays downloadable from Recently deleted for seven days. After that, the database and the deletion backup are deleted permanently and automatically.