pgBackRest Retired, Forcing PostgreSQL Backup Rethink

David Steele announced he is stepping away from pgBackRest, leaving v2.58.0 as the final release and asking forks to adopt new names. Steele maintained the widely-used PostgreSQL backup tool for 13 years, supported historically by Crunchy Data and currently by Supabase; Crunchy’s acquisition by Snowflake and lack of continued sponsorship made maintenance untenable. The move exposes a systemic risk: critical open-source infrastructure often depends on single maintainers or small teams and fragile corporate sponsorship, creating undercapitalization and stealthy decay rather than obvious failure. For PostgreSQL operators and the broader FOSS ecosystem, this raises questions about funding, succession, and operational risk for essential developer and production tooling.

The lead maintainer of pgBackRest announced they can no longer sustain the project and the repository has been archived, leaving the popular Postgres backup tool without active maintenance. Users on Hacker News expressed concern about finding secure, reliable alternatives—candidates mentioned include WAL-G and Barman—and debated forking versus archiving given sponsorship and trust issues. The maintainer cited failed attempts to secure employment or sponsorship after Crunchy Data’s sale, underscoring broader risks to critical open-source infrastructure when funding and stewardship lapse. This matters to operators and cloud providers relying on pgBackRest for continuous WAL and object-storage backups, as unmaintained tooling raises security, compatibility, and operational risks.

The creator of pgBackRest announced the project is no longer being maintained and has issued a notice of obsolescence, urging forks to take a new name. pgBackRest, a widely used open-source PostgreSQL backup and restore tool with features like parallel backup/restore, lz4/zstd compression, remote operation via TLS/SSH, block-level incremental backups, multiple repositories, and strong integrity checks, will stop receiving maintenance, bug fixes, and reviews. The maintainer cited loss of corporate sponsorship after Crunchy Data’s sale, unsuccessful efforts to secure funding or a suitable role, and the personal cost of sustained unpaid work. This matters because production PostgreSQL environments relying on pgBackRest must plan migrations, vet forks, or adopt alternatives to ensure continued security, support, and reliability.

pgBackRest, a widely used open-source backup and restore tool for PostgreSQL, is being retired by its long-time maintainer after 13 years. The author announced they will stop maintaining the project due to lack of sustainable sponsorship and the need to pursue other work, leaving the current stable release at v2.58.0. Key features—parallel backup/restore, lz4/zstd compression, remote TLS/SSH protocol, multiple repositories, full/differential/incremental and block-level backups, and integrity checks—remain documented, but future development and support are ending unless new maintainers fork the codebase and rebrand. This matters to enterprises and DBAs relying on pgBackRest for production backups, who must plan for maintenance handover, forks, or alternative tools.