Item — HN Reader

Last time I checked, Barman didn't support backups to S3. That's why (for us) pgBackRest was such a big deal: it could offload full and incremental backups to a basically limitless and reliable medium.

I think (and I'm probably wrong now) that Barman only could push backups to another Linux machine (e.g., EC2 box), so you had to worry about your backup system _on top_ of the main DB.

So I'm really hoping someone will pickup maintaining pgBackRest.

4 comments

Huh... Opposite experience. Barman cloud (s3 backups) is the only way I've ever used it. I didn't realize it wasn't the only way. Makes sense it could just use a filesystem.

https://docs.pgbarman.org/release/3.14.1/user_guide/barman_c...

They have a plugin that supports backups to cloud storage

https://docs.pgbarman.org/release/3.12.0/user_guide/barman_c...

For CNPG: https://github.com/cloudnative-pg/plugin-barman-cloud

Something like Rclone and a cron job, or else s3 mounted via FUSE, could possibly bridge that. Of course then you have to worry about reliability of the bridge...

There’s support via Barman cloud - we use it for azure at work but s3 and others are supported iirc

Mounting S3 with Fuse is not stable or performant enough at scale for backup storage

I can understand why it'd be preferable to avoid such a bridge layer, and indeed I too would rather just have a transparent view of what's going on at the protocol level.

Stability and performance at scale sound like implementation specific properties though. If you've tried this, I'd be curious to known about the specific issues you encountered.

https://github.com/Barre/ZeroFS Should do a great job at this.

There are other ways to mount S3, but you may want to check out Amazon's new product, S3 files: https://aws.amazon.com/about-aws/whats-new/2026/04/amazon-s3...

https://aws.amazon.com/s3/features/files/