There are two mechanisms for backups within Postgres. Physical backups are a byte for byte backup of the data on disk. Logical backups are the raw data in a more portable format (a set of SQL statements such as CREATE table and INSERTs). You can read further on the difference between physical and logical backups here.

Crunchy Bridge automatically comes with physical backups for your database included at no extra charge. As part of the phsyical backup process we capture a PostgreSQL base backup every day. Then stream the WAL every 60 seconds or 16MB of WAL (whichever comes first). A backup can be restored as a fork.

Backups are provided for a rolling 10 day period. If you need a longer backup time, you can use the fork feature to create individual backup snapshots. Talk to customer success if you need additional considerations with backups.

If you wish to capture logical backups for your database you can do those by connecting to your database with pg_dump.

Forking from backup

On the cluster page there is a main landing page for backups which shows all stored backups and the timestamp. You can create a fork from a backup which will create a stand alone instance with a unique connections string.


Start a manual backup

The main backups page has the option to start a manual backup in the event that you need that available for a fork later.

Accessing your backups

On the backups page you can view and copy credentials to directly access the files for your backups. This can be used to access files or move backups for longer storage in case you want to store backups for longer than the current 10 day window.

Backup location


Both the CLI and API have capabitliies for managing backups and all the features described above.