Barman – Backup and Recovery Manager for PostgreSQL

A backup tool moving from one download site to another should be the least dramatic story on the internet — and yet here we are. Barman, the open-source PostgreSQL backup and recovery tool maintained by EnterpriseDB, has officially settled into its newer GitHub-era home, replacing its old SourceForge setup for versions starting with 2.13. On paper, this is a tidy housekeeping update for a tool that helps companies save copies of their databases so they can recover after disaster. In the comments, though, it turned into a full-on group therapy session for database admins.

The loudest mood? “Solid, but…” Multiple users praised Barman as dependable in real-world deployments, especially through CloudNativePG, with one calling it the default choice in their setup and another saying it’s used for almost all of ParadeDB’s deployments. But the compliments came with battle scars: warnings about storage filling up and knocking databases offline, gripes about slow uploads for huge databases, and complaints that some cloud storage settings still feel limited. Then came the mini-rivalry: some commenters contrasted Barman with pgBackRest, especially around easy cloud backup support, while others suggested Barman may now be the comeback kid as rivals wobble. There was even a wonderfully blunt drive-by question — “how to use barman with aws RDS” — which had the energy of someone kicking open the door halfway through an argument. In short: people respect Barman, but they’re absolutely not done roasting its rough edges.