Barman

Barman is a free, open-source Python tool for disaster recovery across PostgreSQL servers. Designed for business-critical databases, it supports remote backups and local or remote recovery, including point-in-time recovery. Backup management includes catalogs, incremental and parallel operations, retention policies, and WAL archiving or streaming. Synchronous WAL streaming supports zero data loss (RPO=0). Remote backups can use rsync over SSH or pg_basebackup, and recovery can run locally or over SSH.

Barman integrates with PostgreSQL and archiving tools such as tar. It can compress WAL files using bzip2, gzip, or a custom method. Encryption of backups and WAL files with GPG depends on configuration, and immutable storage has a required grace period in the current implementation. The experimental cloud-streaming method supports only S3-compatible destinations and does not support encryption or direct restores in Barman. It runs on Linux or UNIX-like systems, uses an INI configuration file, and stores metadata locally. Its code is distributed under GNU General Public License 3.

Barman provides PostgreSQL backup and recovery capabilities, including point-in-time recovery, WAL support, and flexible remote transfers. Its experimental cloud-streaming method has specific limitations, and encryption features depend on configuration.

Barman suits database administrators and organizations managing recovery for business-critical PostgreSQL databases. It is intended for self-hosted use on Linux or UNIX-like systems.

Overview

Barman is an open-source administration tool for recovering PostgreSQL databases after disruption. It is best suited to database administrators responsible for business-critical systems who can operate Linux or UNIX-like infrastructure. Its strongest case is flexible, continuous PostgreSQL recovery at no license cost; its narrow database focus and cloud-streaming constraints limit its appeal elsewhere.

Key features

Barman can manage remote backups for multiple PostgreSQL servers through rsync over SSH or pg_basebackup. Backup catalogs, incremental and parallel operations, and retention policies give administrators control over how backups and WAL files are created and kept. That range suits organizations with recovery requirements that go beyond retaining a single latest copy, though it calls for staff able to manage a self-hosted database tool.

Continuous backup, WAL archiving and streaming, and point-in-time recovery let teams target a specific recovery moment. Synchronous WAL streaming supports zero data loss (RPO=0), which matters when losing even recent database changes is unacceptable. Recovery can run locally or remotely, including over SSH, and restore verification is supported.

Barman integrates with PostgreSQL and standard archiving tools such as tar. It uses an INI configuration file and stores metadata locally. WAL files can be compressed with bzip2, gzip, or a custom method. GPG encryption is supported for backups and WAL files, but it depends on configuration, so administrators must account for that setup. Immutable storage can reduce the risk of accidental deletion or malicious changes; its current implementation requires a grace period.

The documented experimental cloud-streaming method is limited to S3-compatible destinations and does not support encryption or direct restores in Barman. Optional libraries add integrations for AWS S3 and EC2 snapshots, Azure Blob Storage and VM snapshots, and Google Cloud Storage and Compute snapshots. Those integrations broaden deployment choices, but the experimental streaming path has meaningful recovery and security limitations.

Pricing

Barman's plan is free: free. The open-source tool is distributed under the GNU General Public License 3, and there is no free trial because the product is already free. There are no paid plan tiers or per-seat charges in the stated plan. The tradeoff is operational ownership: organizations run it themselves and arrange support separately if community channels are insufficient.

Community support is available through a mailing list and GitHub bug tracker. EnterpriseDB offers 24x7 production support, consulting, and training; no price is stated for those services, so organizations needing a formal support arrangement should expect custom pricing.

Platforms

Barman is self-hosted and runs on Linux or UNIX-like systems, including FreeBSD and OpenBSD. This is a fit for teams that can maintain their own backup environment, but not for readers seeking a hosted, browser-managed service. The project lists PGDG and EDB repositories, PyPI, and GitHub releases as download sources.

Who it's for

Barman fits organizations and database administrators managing disaster recovery for business-critical PostgreSQL databases, especially when continuous WAL handling, point-in-time recovery, retention controls, or zero-data-loss streaming matter. It is a weaker fit for teams needing one backup tool across different database systems or wanting encrypted direct restores from its experimental cloud-streaming workflow.

Pros and cons

• Pro: Point-in-time recovery, WAL archiving and streaming, and continuous backups give PostgreSQL teams several ways to meet demanding recovery objectives.
• Pro: Incremental and parallel backup and recovery, plus retention policies, support larger and more structured backup operations.
• Pro: The free, GPL-licensed plan avoids a software license charge for self-hosted use.
• Con: PostgreSQL-only support rules it out for teams seeking a single tool for other database engines.
• Con: GPG encryption depends on configuration, while experimental cloud streaming does not support encryption or direct Barman restores.
• Con: Self-hosting and configuration place deployment and ongoing administration on the organization.

Alternatives

Database Backup Software is a useful place to compare products across the category if Barman's PostgreSQL focus is too narrow.

Choose MySQL when a GPL-licensed option with SQL and NoSQL applications and replication and high-availability components better matches the database environment. Database Vault may suit readers who want a web-based option with weekly automated backups, seven-day retention, and 1 GB of storage on its free plan. For a free community option with three connections and three schedules, consider DBAegis.

DT Database Backup Wizard offers a Windows free demo capped at two manual backups per database, with limited scheduling, cloud destinations, and retention. mariadb-backup is a free alternative for physical MariaDB backups on Linux and Windows. Medusa is a free, Apache-2.0-licensed option for Apache Cassandra. Percona Backup for MongoDB is another free, community database backup tool. SQLBackupAndFTP is a freemium Windows option with a free plan and trial.

Verdict

Choose Barman if your team runs PostgreSQL on Linux or UNIX-like systems and needs free, self-hosted disaster recovery with continuous WAL support and point-in-time restores. Its breadth of recovery controls is compelling for administrators who can own the infrastructure. Look elsewhere if you need multi-database coverage, managed hosting, or encrypted direct recovery from cloud streaming.