Postgres backup tools: pg_dump, pg_basebackup, pgBackRest, Barman, WAL-G and managed services

Postgres backup tools at a glance

The main Postgres backup tools are the two that ship with PostgreSQL, pg_dump and pg_basebackup, plus three open-source managers built on physical backups and WAL: pgBackRest, Barman and WAL-G. Managed services such as SimpleBackups sit on top for scheduling and alerts. Each fact below comes from that tool's own documentation, read on 3 October 2026.

The tools that ship with PostgreSQL

pg_dump writes a consistent logical copy of one database and does not block normal reads and writes. It has four output formats; the custom format (-Fc) is compressed by default and lets pg_restore pick which objects to restore. It does not include roles or tablespaces, which is the job of pg_dumpall. See pg_dump versus pg_dumpall.

pg_basebackup copies the whole running cluster over a replication connection. It needs a role with the REPLICATION privilege or a superuser, and it cannot back up a single database. Paired with WAL archiving it becomes the base for point-in-time recovery, but PostgreSQL leaves retention, scheduling and cleanup of old WAL to you. The next three tools fill that gap.

pgBackRest, Barman and WAL-G: what each adds

• pgBackRest. Its documentation lists parallel backup and restore, full, differential and incremental backups down to block level, retention policies, checksums on every file, repository encryption, and repositories in S3, Azure or GCS compatible object stores. You define a stanza, set archive_command = 'pgbackrest --stanza=demo archive-push %p', and run pgbackrest --stanza=demo backup. One limitation: it has its own configuration model to learn. SimpleBackups versus pgBackRest compares the two.
• Barman. Maintained by EnterpriseDB and written in Python. It runs on a separate backup server and takes backups with backup_method = postgres (which uses pg_basebackup) or backup_method = rsync, collecting WAL by archive_command or streaming. Commands follow the pattern barman backup and barman restore. One limitation: it is designed around a backup server with SSH or replication connections to each Postgres host, which is more to set up than a single-server tool.
• WAL-G. Uses wal-g backup-push for base backups and wal-g wal-push from archive_command, with backup-fetch and wal-fetch for restore. Compression can be lz4 (the default), lzma, zstd or brotli. One limitation: it is a command-line tool configured through environment variables or a config file, so scheduling and alerting are yours to build.

Where managed services and SimpleBackups fit

The command-line tools above do not alert you when a job fails unless you wire that up. A managed service does. SimpleBackups says it connects to self-hosted PostgreSQL over SSH, a local agent, Docker or a secure tunnel, and directly to managed databases such as Amazon RDS, Supabase and Neon. Its pricing page, read on 3 October 2026, lists Basic at $0 for one job and Lite at $49 per month (monthly billing) for five jobs with a 5 GB maximum database size.

Where it does not fit: its documentation describes PostgreSQL backups as scheduled pg_dump files and does not describe WAL archiving, and it classes database restores as manual: you download the file and run the native restore tool. If you need recovery to a chosen minute, use pgBackRest, Barman, WAL-G or your cloud provider's own point-in-time recovery, and consider a managed service only for the off-site copy.

Which Postgres backup tool to choose by team

• Solo developer, database under a few GB: pg_dump -Fc on a schedule. Native tools are enough. Start with how to back up a Postgres database.
• Self-hosted production database that cannot lose an hour: pgBackRest, or WAL-G if everything goes to object storage.
• Several Postgres servers and a DBA: Barman on its own host.
• Small team, several databases, no one on call for backups: a managed service such as SimpleBackups.
• Database on a managed platform: turn on the provider's backups first, then add an independent copy. Provider backups explains why both matter.