ABOUT THIS PROJECT
TL;DR: pgBunker is a community-maintained fork of pgBackRest, started after the upstream project wound down maintenance in April 2026. We owe an enormous debt of gratitude to David Steele and every pgBackRest contributor.
In April 2026, after thirteen years of stewardship, David Steele announced that he could no longer continue maintaining pgBackRest. Following the sale of Crunchy Data he had searched for a position or sponsorship that would let him keep the project going full-time, but neither came together at a level that could sustain the work. Rather than do the maintenance poorly or sporadically, he chose a hard stop — a decision he has every right to make and that we respect entirely.
pgBackRest is a foundational piece of the PostgreSQL ecosystem: battle-tested code, a uniquely thorough test suite, and a reputation for correctness that any backup tool aspires to. Letting it stagnate was not an outcome we were willing to accept, so we forked the project under a new name — as David explicitly requested any future fork should — and committed to carrying the work forward.
We are pgBunker. Our scope is deliberately modest: keep the project building on current PostgreSQL versions, address security and reliability issues, accept high-quality contributions, and earn trust the same way the original project did — slowly, and through careful work.
Our thanks go to David Steele, every pgBackRest contributor over the years, and the sponsors — Crunchy Data, Resonate, and others — who made thirteen years of free, reliable PostgreSQL backup software possible. Every line of pgBunker rests on that foundation. Thank you.
Introduction
pgBunker is a reliable backup and restore solution for PostgreSQL that seamlessly scales up to the largest databases and workloads.
Features
Parallel Backup & Restore
Compression is usually the bottleneck during backup operations so pgBunker solves this problem with parallel processing and more efficient compression algorithms such as lz4 and zstd.
Local or Remote Operation
A custom protocol allows pgBunker to backup, restore, and archive locally or remotely via TLS/SSH with minimal configuration. An interface to query PostgreSQL is also provided via the protocol layer so that remote access to PostgreSQL is never required, which enhances security.
Multiple Repositories
Multiple repositories allow, for example, a local repository with minimal retention for fast restores and a remote repository with a longer retention for redundancy and access across the enterprise.
Full, Differential, & Incremental Backups (at File or Block Level)
Full, differential, and incremental backups are supported. pgBunker is not susceptible to the time resolution issues of rsync, making differential and incremental backups safe without the requirement to checksum each file. Block-level backups save space by only copying the parts of files that have changed.
Backup Rotation & Archive Expiration
Retention polices can be set for full and differential backups to create coverage for any time frame. The WAL archive can be maintained for all backups or strictly for the most recent backups. In the latter case WAL required to make older backups consistent will be maintained in the archive.
Backup Integrity
Checksums are calculated for every file in the backup and rechecked during a restore or verify. After a backup finishes copying files, it waits until every WAL segment required to make the backup consistent reaches the repository.
Backups in the repository may be stored in the same format as a standard PostgreSQL cluster (including tablespaces). If compression is disabled and hard links are enabled it is possible to snapshot a backup in the repository and bring up a PostgreSQL cluster directly on the snapshot. This is advantageous for terabyte-scale databases that are time consuming to restore in the traditional way.
All operations utilize file and directory level fsync to ensure durability.
Page Checksums
If page checksums are enabled pgBunker will validate the checksums for every file that is copied during a backup. All page checksums are validated during a full backup and checksums in files that have changed are validated during differential and incremental backups.
Validation failures do not stop the backup process, but warnings with details of exactly which pages have failed validation are output to the console and file log.
This feature allows page-level corruption to be detected early, before backups that contain valid copies of the data have expired.
Backup Resume
An interrupted backup can be resumed from the point where it was stopped. Files that were already copied are compared with the checksums in the manifest to ensure integrity. Since this operation can take place entirely on the repository host, it reduces load on the PostgreSQL host and saves time since checksum calculation is faster than compressing and retransmitting data.
Streaming Compression & Checksums
Compression and checksum calculations are performed in stream while files are being copied to the repository, whether the repository is located locally or remotely.
If the repository is on a repository host, compression is performed on the PostgreSQL host and files are transmitted in a compressed format and simply stored on the repository host. When compression is disabled a lower level of compression is utilized to make efficient use of available bandwidth while keeping CPU cost to a minimum.
Delta Restore
The manifest contains checksums for every file in the backup so that during a restore it is possible to use these checksums to speed processing enormously. On a delta restore any files not present in the backup are first removed and then checksums are generated for the remaining files. Files that match the backup are left in place and the rest of the files are restored as usual. Parallel processing can lead to a dramatic reduction in restore times.
Parallel, Asynchronous WAL Push & Get
Dedicated commands are included for pushing WAL to the archive and getting WAL from the archive. Both commands support parallelism to accelerate processing and run asynchronously to provide the fastest possible response time to PostgreSQL.
WAL push automatically detects WAL segments that are pushed multiple times and de-duplicates when the segment is identical, otherwise an error is raised. Asynchronous WAL push allows transfer to be offloaded to another process which compresses WAL segments in parallel for maximum throughput. This can be a critical feature for databases with extremely high write volume.
Asynchronous WAL get maintains a local queue of WAL segments that are decompressed and ready for replay. This reduces the time needed to provide WAL to PostgreSQL which maximizes replay speed. Higher-latency connections and storage (such as S3) benefit the most.
The push and get commands both ensure that the database and repository match by comparing PostgreSQL versions and system identifiers. This virtually eliminates the possibility of misconfiguring the WAL archive location.
Tablespace & Link Support
Tablespaces are fully supported and on restore tablespaces can be remapped to any location. It is also possible to remap all tablespaces to one location with a single command which is useful for development restores.
File and directory links are supported for any file or directory in the PostgreSQL cluster. When restoring it is possible to restore all links to their original locations, remap some or all links, or restore some or all links as normal files or directories within the cluster directory.
Getting Started
pgBunker strives to be easy to configure and operate:
- User guides for various operating systems and PostgreSQL versions.
- Command reference for command-line operations.
- Configuration reference for creating pgBunker configurations.
Sponsorship
pgBunker would not exist without sponsors. Writing new features, fixing bugs, reviewing contributions, answering questions from the community, and maintenance all take a considerable amount of time.
Current sponsors:
Past sponsors: Crunchy Data, Resonate.