pg_combinebackup
Reconstruct a full (synthetic) PostgreSQL backup from an incremental backup chain. tldr-pages
On several platforms
Several platforms
Reconstruct a full (synthetic) PostgreSQL backup from an incremental backup chain. When specifying multiple backups order them from oldest to newest.
Combine a full and incremental backup into one synthetic full backup
pg_combinebackup path/to/full_backup path/to/incremental_backup --output path/to/output_directoryIdentifySimulate what would be done without creating files
pg_combinebackup --dry-run path/to/full_backup path/to/incremental_backup --output path/to/output_directoryIdentifyUse hard links instead of copying files (faster, same filesystem required)
pg_combinebackup --link path/to/full_backup path/to/incremental_backup --output path/to/output_directoryIdentifyUse file cloning (reflinks) for efficient copy if supported
pg_combinebackup --clone path/to/full_backup path/to/incremental_backup --output path/to/output_directoryIdentifyUse the copy_file_range system call for efficient copying
pg_combinebackup --copy-file-range path/to/full_backup path/to/incremental_backup --output path/to/output_directoryIdentifyRelocate a tablespace during reconstruction
pg_combinebackup path/to/backup1 path/to/backup2 ... --tablespace-mapping /path/to/old_tablespace=/path/to/new_tablespace --output path/to/output_directoryIdentifyDisable fsync for faster but unsafe writes (testing only)
pg_combinebackup --no-sync path/to/backup1 path/to/backup2 ... --output path/to/output_directoryIdentifyShow detailed debug output
pg_combinebackup --debug path/to/backup1 path/to/backup2 ... --output path/to/output_directoryIdentify