# Your PostgreSQL data. A clear way back.

> Learn how CalmBackup uses pg_dump and pg_restore, what a PostgreSQL dump check proves, and how to prepare and validate an isolated recovery rehearsal.

Canonical page: https://www.calmbackup.com/guides/postgresql-backups

Understand CalmBackup’s PostgreSQL dump workflow, the tools it needs, and the checks to make before relying on a restore.

[Start free trial](https://app.calmbackup.com/register)

## Start with the database you actually need.

CalmBackup’s PostgreSQL driver backs up the database named in your configuration. It runs pg\_dump in custom format, then packages that dump with any selected directories. This gives you an encrypted archive of a particular database and its supporting files.

Make a short inventory before setup: the database name, connection details, application uploads, database extensions and the people who can authorize recovery. A configuration that points to a development database will happily protect the wrong environment unless you check it.

[Open the configuration reference](https://www.calmbackup.com/docs/configuration)

## Know what the dump includes.

A single-database dump is not a complete PostgreSQL cluster backup. Cluster-wide roles and tablespaces need a separate recovery plan. Document how to recreate the surrounding database environment, including required extensions and application credentials.

Check the version compatibility of pg\_dump, the server and the intended restore environment. The official PostgreSQL documentation explains these boundaries in detail.

**Snapshot recovery, not arbitrary point-in-time recovery**

This workflow restores a selected backup. It does not configure continuous WAL archiving or let you choose any second between snapshots.

[Read PostgreSQL’s pg\_dump reference](https://www.postgresql.org/docs/current/app-pgdump.html)

## A readable dump is the beginning.

The CLI checks the archive with pg\_restore --list. That is useful evidence that the dump can be inspected, but it does not run your application against a restored database.

For a rehearsal, prepare a separate destination and use an explicit recovery configuration. The PostgreSQL restore uses clean/if-exists behavior, so review the target before running it. Afterward, check important records, relationships, permissions and the application operations your team depends on.

1.  ### Prepare the destination
    
    Install the required PostgreSQL tools and recreate the environment your application needs. Confirm that the destination is isolated from production.
    
2.  ### Restore the selected snapshot
    
    Use the correct archive key and recovery configuration. Record the backup timestamp and any warnings from the import.
    
3.  ### Validate the application
    
    Check representative reads and writes, uploaded files and background jobs in the isolated environment. Record how long the complete exercise takes.
    

[Use the restore checklist](https://www.calmbackup.com/guides/restore-checklist)
