barman

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 managed pg with point-in-time backups) just a snapshot backup, so that's worth considering as well. [1] https://github.com/wal-g/wal-g [2] https://github.com/EnterpriseDB/barman

Wow, this is pretty surprising, I was under the impression that this is the leading PG backup/recovery tool. Anybody know how WAL-G and Barman compare? https://github.com/wal-g/wal-g https://github.com/EnterpriseDB/barman

> The first consideration should be backups. Useful to look at barman and see if it can meet one's needs: * https://www.pgbarman.org/ * https://github.com/2ndquadrant-it/barman No sense re-inventing the wheel if it can be avoided.

I agree, Postgres having its own storage subsystem would be wrong. Fortunately the PG philosophy is to leave what the OS does best to the OS, so its unlikely that situation would arise. However, a middle ground of being able to backup just the changes in a multi-terabyte database that have been made since the last full backup, wouldn't be controversial and is a common use case. I've read of a few attempts on the PG dev mailing list over the last couple of years, so hopefully one of them will be completed sometime soon and merged into core. Some of the work I have come across : https://github.com/ossc-db/pg_rman https://github.com/2ndquadrant-it/barman/issues/21