pg_probackup
is a utility to manage backup and recovery of PostgreSQL database clusters. It is designed to perform periodic backups of the PostgreSQL instance that enable you to restore the server in case of a failure.
The utility is compatible with:
As compared to other backup solutions, pg_probackup
offers the following benefits that can help you implement different backup strategies and deal with large amounts of data:
checkdb
command.time to live
(TTL) for a particular backup. Expired backups can be merged or deleted._vm
or _fsm
data directory
(PGDATA), such as scripts, configuration files, logs, or SQL dump files.To manage backup data, pg_probackup
creates a backup catalog. This directory stores all backup files with additional meta information, as well as WAL archives required for point-in-time recovery. You can store backups for different instances in separate subdirectories of a single backup catalog.
Using pg_probackup
, you can take full or incremental backups:
Full
backups contain all the data files required to restore the database cluster from scratch.Incremental
backups only store the data that has changed since the previous backup. It allows to decrease the backup size and speed up backup operations. pg_probackup
supports the following modes of incremental backups:
PAGE
backup. In this mode, pg_probackup
scans all WAL files in the archive from the moment the previous full or incremental backup was taken. Newly created backups contain only the pages that were mentioned in WAL records. This requires all the WAL files since the previous backup to be present in the WAL archive. If the size of these files is comparable to the total size of the database cluster files, speedup is smaller, but the backup still takes less space.DELTA
backup. In this mode, pg_probackup
read all data files in PGDATA directory and only those pages, that where changed since previous backup, are copied. Continuous archiving is not necessary for it to operate. Also this mode could impose read-only I/O pressure equal to Full
backup.PTRACK
backup. In this mode, PostgreSQL tracks page changes on the fly. Continuous archiving is not necessary for it to operate. Each time a relation page is updated, this page is marked in a special PTRACK
bitmap for this relation. As one page requires just one bit in the PTRACK
fork, such bitmaps are quite small. Tracking implies some minor overhead on the database server operation, but speeds up incremental backups significantly.Regardless of the chosen backup type, all backups taken with pg_probackup
support the following strategies of WAL delivery:
Autonomous backups
streams via replication protocol all the WAL files required to restore the cluster to a consistent state at the time the backup was taken. Even if continuous archiving is not set up, the required WAL segments are included into the backup.Archive backups
rely on continuous archiving.PTRACK
backup support provided via following options:
pg_probackup
currently has the following limitations:
Documentation can be found at github and Postgres Professional documentation
master
branch contains minor fixes that are planned to the nearest minor release.release_2_6
.For detailed release plans check Milestones
Installers are available in release assets. Latests.
See the Installation section in the documentation.
Once you have pg_probackup
installed, complete the setup.
For users of Postgres Pro products, commercial editions of pg_probackup are available for installation from the corresponding Postgres Pro product repository.
To compile pg_probackup
, you must have a PostgreSQL installation and raw source tree. Execute this in the module's directory:
make USE_PGXS=1 PG_CONFIG=<path_to_pg_config> top_srcdir=<path_to_PostgreSQL_source_tree>
The alternative way, without using the PGXS infrastructure, is to place pg_probackup
source directory into contrib
directory and build it there. Example:
cd <path_to_PostgreSQL_source_tree> && git clone https://github.com/postgrespro/pg_probackup contrib/pg_probackup && cd contrib/pg_probackup && make
Currently pg_probackup can be build using only MSVC 2013. Build PostgreSQL using pgwininstall or PostgreSQL instruction with MSVC 2013. If zlib support is needed, src/tools/msvc/config.pl must contain path to directory with compiled zlib. Example
CALL "C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\vcvarsall" amd64
SET PATH=%PATH%;C:\Perl64\bin
SET PATH=%PATH%;C:\msys64\usr\bin
gen_probackup_project.pl C:\path_to_postgresql_source_tree
This module available under the license similar to PostgreSQL.
Do not hesitate to post your issues, questions and new ideas at the issues page.
Postgres Professional, Moscow, Russia.
pg_probackup
utility is based on pg_arman
, that was originally written by NTT and then developed and maintained by Michael Paquier.
Description of how to add new translation languages.
For more information, follow the link below: https://postgrespro.ru/docs/postgresql/12/nls-translator