Barman review
A mature, self-hosted choice for continuous PostgreSQL backup and recovery.
Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026
Barman is an open-source Python administration tool for backing up and recovering PostgreSQL servers. It is designed for database administrators managing business-critical PostgreSQL environments, particularly teams that need centralized backup catalogs and recovery operations across multiple servers. The software supports full physical hot backups, incremental backups through rsync or PostgreSQL streaming, WAL archiving and streaming, and local or remote recovery over SSH. Its continuous backup model and PostgreSQL focus make it a fit for established operations rather than teams seeking a general-purpose, multi-database backup service.
Barman is distributed as free open-source software under GPLv3, with no vendor-hosted pricing tiers. The published model gives teams access to the full feature set without plan-based packaging. Retention policies can be configured around redundancy or recovery windows, while backup and WAL compression can help manage stored recovery data. Encryption is available for backups and WAL through GPG. These controls give administrators room to shape retention and protection policies around their PostgreSQL environment instead of selecting among fixed commercial plans.
Recovery depth is the main reason to choose Barman. Point-in-time recovery can target a time, transaction, LSN, or named restore point, and WAL can be archived or streamed, including through synchronous streaming. Remote recovery over SSH supports operations distributed across systems, while pg_verifybackup provides backup verification. The trade-off is operational scope: Barman is self-hosted on Linux and focused on PostgreSQL, so organizations needing vendor-hosted operations, broader database coverage, or a different deployment model should look elsewhere. PostgreSQL teams with experienced administrators should find its backup catalog and recovery controls closely aligned with established disaster-recovery workflows.
Barman pros and cons
- Where it wins
- Point-in-time recovery with time, transaction, LSN, and named targets
- WAL archiving and streaming, including synchronous streaming
- Encryption, compression, retention policies, and pg_verifybackup checks
- Where it doesn't
- Supports PostgreSQL rather than multiple database types
- Linux deployment limits platform coverage
- Self-hosted operation requires database administration resources
Barman fact sheet, pricing and score →
Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.
Last updated · How we research and update