A PostgreSQL backup tool that dumps databases, globals, and configuration in flexible formats with encryption and cloud upload support.
pg_back is a comprehensive backup utility for PostgreSQL that extends beyond basic pg_dumpall functionality. It provides a unified way to dump databases, roles, tablespaces, and server configuration, addressing limitations in native PostgreSQL tools. The tool aims to be a robust, feature-rich alternative to manual pg_dump/pg_dumpall scripts, emphasizing flexibility, security, and integration with modern storage backends.
Database administrators and DevOps engineers managing PostgreSQL instances who need automated, secure, and flexible backup solutions. It's particularly useful for teams requiring integration with cloud storage, encryption, and complex purge policies.
Developers choose pg_back over native tools because it offers concurrent database dumps, multiple output formats per database, built-in encryption with age, and direct upload to various cloud storage providers (S3, GCS, Azure, B2, SFTP). It also provides advanced features like hot standby support, pre/post hooks, and configurable purge policies not available in standard PostgreSQL utilities.
Simple backup tool for PostgreSQL
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Allows dumping all, specific, or excluded databases including templates, and supports multiple output formats (custom, directory, tar, plain SQL) per database, as detailed in the Features section.
Dumps multiple databases simultaneously and uses parallel pg_dump sessions with the --jobs option, speeding up backup operations significantly.
Integrates age encryption for dumps and computes SHA checksums for integrity verification, enhancing backup security and reliability.
Direct upload to S3, GCS, Azure, B2, and SFTP simplifies off-site backup management, with options for remote purge and deletion.
Per-database settings require an INI config file, and options like schema exclusions add setup overhead, making it less straightforward than command-line-only tools.
Backups are written unencrypted to disk before encryption, posing a security risk if the host is compromised, as warned in the Encryption section.
The README states that Azure upload support is not guaranteed due to lack of free testing, which could be unreliable for Azure-dependent users.