{"slug": "barman", "name": "Barman", "category": "databases", "category_name": "Databases", "description": "", "recommenders": 4, "commenters": 4, "warners": 0, "score": 3.61, "rising": -1.31, "first": "2026-04-27", "latest": "2026-07-20", "why": "Barman has always been solid for backup and restore", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 4, "neutral": 0, "compare": 0, "warn": 0}, "spark": [0, 0, 0, 0, 0, 1, 2, 0, 1, 0, 0, 0], "listed": true, "loved": [], "caveat": "", "short_quote": "Barman has always been solid for backup and restore", "icon": true, "domain": "pgbarman.org", "github_repo": null, "official_url": "https://pgbarman.org", "pricing": "", "aliases": ["Barman"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 783806688, "item_id": 48987918, "url": "https://news.ycombinator.com/item?id=48987918", "by": "pqdbr", "date": "2026-07-20", "stance": "recommend", "quote": "For postgres, we use barman.", "excerpt": "This is how we implemented this at our company: - We have 2 sources of data that we must backup to continue existing as a business; our postgres and binary files in S3. Everything else is derivable (elasticsearch, so on). - For postgres, we use barman. With the help of opus/fable, you can get a streaming replication backup working in no time. We have one into another server in the same datacenter (we use baremetal) a", "context": "runs baremetal company infrastructure", "use_case": "PostgreSQL backups", "switched_from": "", "story": "Hacker wipes Romania's land registry database"}, {"id": 781068322, "item_id": 48816770, "url": "https://news.ycombinator.com/item?id=48816770", "by": "pqdbr", "date": "2026-07-07", "stance": "recommend", "quote": "reliable, tested, fault tolerant postgres with streaming replication and barman for backups", "excerpt": "Claude Code has been a blessing for all our devops work. We use baremetal servers and now have reliable, tested, fault tolerant postgres with streaming replication and barman for backups configured and running, with less than a second of replication lag, including a S3 redundant backup with < 1 minute of data loss (archive_timeout=60s) with S3 object-lock set up in compliance mode (so even the ransonware scenario is ", "context": "Runs baremetal servers", "use_case": "PostgreSQL backups", "switched_from": "", "story": "PostgreSQL Benchmark: AWS RDS vs. Self-Hosted on Hetzner (2026)"}, {"id": 768334080, "item_id": 48020880, "url": "https://news.ycombinator.com/item?id=48020880", "by": "freedomben", "date": "2026-05-05", "stance": "recommend", "quote": "Barman[1] and Wal-G[2] are the two I've seen most recommended.", "excerpt": "Barman[1] and Wal-G[2] are the two I've seen most recommended. They do things a little differently though so not drop-in by any means. I've just transitioned to using a full compressed/encrypted sql dump from a cron job. It's been more convenient anyway when I want to restore. But incremental backups are hard that way so if your database is big, it's not a great solution. It's also not my primary backup (I use a mana", "context": "", "use_case": "PostgreSQL backups", "switched_from": "", "story": "pgxbackup: Continuity Support for pgBackRest"}, {"id": 767799424, "item_id": 47987464, "url": "https://news.ycombinator.com/item?id=47987464", "by": "ninjaoxygen", "date": "2026-05-02", "stance": "recommend", "quote": "Barman has always been solid for backup and restore", "excerpt": "We use Barman inside Kubernetes via CloudNativePG's plugin, as it is the default backup plugin. Barman has always been solid for backup and restore, however configuring backup in CNPG is a little more interesting - WAL limits need to be set carefully or you just end up filling WAL volumes and the database becoming unavailable.", "context": "", "use_case": "PostgreSQL backup in Kubernetes", "switched_from": "", "story": "Barman \u2013 Backup and Recovery Manager for PostgreSQL"}, {"id": 766766176, "item_id": 47922886, "url": "https://news.ycombinator.com/item?id=47922886", "by": "zie", "date": "2026-04-27", "stance": "recommend", "quote": "We use barman, very happily", "excerpt": "See the documentation: https://www.postgresql.org/docs/current/backup.html all of these various 3rd party backup tools use these things. Mostly it's QOL stuff that you get from a 3rd party tool. We use barman, very happily: https://pgbarman.org/", "context": "", "use_case": "PostgreSQL backups", "switched_from": "", "story": "Pgbackrest is no longer being maintained"}]}], "caveats": [], "who": [{"by": "pqdbr", "context": "runs baremetal company infrastructure", "url": "https://news.ycombinator.com/item?id=48987918", "date": "2026-07-20"}], "tags": [], "use_cases": ["postgresql backups", "postgresql backup in kubernetes"], "compared": [{"slug": "pgbackrest", "name": "pgBackRest", "co": 2, "switched_from": 0, "switched_to": 0}, {"slug": "claude-opus", "name": "Claude Opus", "co": 2, "switched_from": 0, "switched_to": 0}, {"slug": "postgresql", "name": "PostgreSQL", "co": 2, "switched_from": 0, "switched_to": 0}], "makers": [], "threads": [{"url": "https://news.ycombinator.com/item?id=48978605", "title": "Hacker wipes Romania's land registry database", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=48816129", "title": "PostgreSQL Benchmark: AWS RDS vs. Self-Hosted on Hetzner (2026)", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47988439", "title": "pgxbackup: Continuity Support for pgBackRest", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47948526", "title": "Barman \u2013 Backup and Recovery Manager for PostgreSQL", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47919997", "title": "Pgbackrest is no longer being maintained", "mentions": 1}], "sentiment_by_month": {"2025-11": {}, "2025-12": {}, "2026-01": {}, "2026-02": {}, "2026-03": {}, "2026-04": {"recommend": 1}, "2026-05": {"recommend": 2}, "2026-06": {}, "2026-07": {"recommend": 1}, "2026-08": {}, "2026-09": {}, "2026-10": {}}, "quotes": [{"id": 783806688, "item_id": 48987918, "url": "https://news.ycombinator.com/item?id=48987918", "by": "pqdbr", "date": "2026-07-20", "stance": "recommend", "quote": "For postgres, we use barman.", "excerpt": "This is how we implemented this at our company: - We have 2 sources of data that we must backup to continue existing as a business; our postgres and binary files in S3. Everything else is derivable (elasticsearch, so on). - For postgres, we use barman. With the help of opus/fable, you can get a streaming replication backup working in no time. We have one into another server in the same datacenter (we use baremetal) a", "context": "runs baremetal company infrastructure", "use_case": "PostgreSQL backups", "switched_from": "", "story": "Hacker wipes Romania's land registry database"}, {"id": 781068322, "item_id": 48816770, "url": "https://news.ycombinator.com/item?id=48816770", "by": "pqdbr", "date": "2026-07-07", "stance": "recommend", "quote": "reliable, tested, fault tolerant postgres with streaming replication and barman for backups", "excerpt": "Claude Code has been a blessing for all our devops work. We use baremetal servers and now have reliable, tested, fault tolerant postgres with streaming replication and barman for backups configured and running, with less than a second of replication lag, including a S3 redundant backup with < 1 minute of data loss (archive_timeout=60s) with S3 object-lock set up in compliance mode (so even the ransonware scenario is ", "context": "Runs baremetal servers", "use_case": "PostgreSQL backups", "switched_from": "", "story": "PostgreSQL Benchmark: AWS RDS vs. Self-Hosted on Hetzner (2026)"}, {"id": 768334080, "item_id": 48020880, "url": "https://news.ycombinator.com/item?id=48020880", "by": "freedomben", "date": "2026-05-05", "stance": "recommend", "quote": "Barman[1] and Wal-G[2] are the two I've seen most recommended.", "excerpt": "Barman[1] and Wal-G[2] are the two I've seen most recommended. They do things a little differently though so not drop-in by any means. I've just transitioned to using a full compressed/encrypted sql dump from a cron job. It's been more convenient anyway when I want to restore. But incremental backups are hard that way so if your database is big, it's not a great solution. It's also not my primary backup (I use a mana", "context": "", "use_case": "PostgreSQL backups", "switched_from": "", "story": "pgxbackup: Continuity Support for pgBackRest"}, {"id": 767799424, "item_id": 47987464, "url": "https://news.ycombinator.com/item?id=47987464", "by": "ninjaoxygen", "date": "2026-05-02", "stance": "recommend", "quote": "Barman has always been solid for backup and restore", "excerpt": "We use Barman inside Kubernetes via CloudNativePG's plugin, as it is the default backup plugin. Barman has always been solid for backup and restore, however configuring backup in CNPG is a little more interesting - WAL limits need to be set carefully or you just end up filling WAL volumes and the database becoming unavailable.", "context": "", "use_case": "PostgreSQL backup in Kubernetes", "switched_from": "", "story": "Barman \u2013 Backup and Recovery Manager for PostgreSQL"}, {"id": 766766176, "item_id": 47922886, "url": "https://news.ycombinator.com/item?id=47922886", "by": "zie", "date": "2026-04-27", "stance": "recommend", "quote": "We use barman, very happily", "excerpt": "See the documentation: https://www.postgresql.org/docs/current/backup.html all of these various 3rd party backup tools use these things. Mostly it's QOL stuff that you get from a 3rd party tool. We use barman, very happily: https://pgbarman.org/", "context": "", "use_case": "PostgreSQL backups", "switched_from": "", "story": "Pgbackrest is no longer being maintained"}]}