db/pgbackrest
1
0
Fork 0
mirror of https://github.com/pgbackrest/pgbackrest.git synced 2025-01-18 04:58:51 +02:00
Code Issues Releases Activity
Reliable PostgreSQL Backup & Restore
195 Commits 3 Branches 114 Tags 106 MiB
C 97.1%
Perl 2.6%
Meson 0.3%
e68f836b2e
Go to file
David Steele e68f836b2e Documented enhancements planned for v0.15
2014-03-08 09:12:53 -05:00
test Squashed commit of the following: 2014-03-04 08:00:51 -05:00
.gitignore Squashed commit of the following: 2014-03-04 08:00:51 -05:00
LICENSE v0.01: Backup and archiving are functional 2014-03-05 18:56:15 -05:00
pg_backrest_backup.pm Squashed commit of the following: 2014-03-04 08:00:51 -05:00
pg_backrest_db.pm Squashed commit of the following: 2014-03-04 08:00:51 -05:00
pg_backrest_file.pm Squashed commit of the following: 2014-03-04 08:00:51 -05:00
pg_backrest_utility.pm Squashed commit of the following: 2014-03-04 08:00:51 -05:00
pg_backrest.conf Squashed commit of the following: 2014-03-04 08:00:51 -05:00
pg_backrest.pl Added comments. 2014-03-05 20:06:13 -05:00
README.md Documented enhancements planned for v0.15 2014-03-08 09:12:53 -05:00

README.md

pg_backrest

Simple Postgres Backup and Restore

release notes

v0.15: Added archive-get [THIS IS PLANNED FUNCTIONALITY FOR THIS RELEASE]

  • Added archive-get functionality to aid in restores.

  • Default restore.conf is written to each backup.

v0.10: Backup and archiving are functional

This version has been put into production at Resonate, so it does work, but there are a number of major caveats.

  • No restore functionality, but the backup directories are consistent Postgres data directories. You'll need to either uncompress the files or turn off compression in the backup. Uncompressed backups on a ZFS (or similar) filesystem are a good option because backups can be restored locally via a snapshot to create logical backups or do spot data recovery.

  • Archiving is single-threaded. This has not posed an issue on our multi-terabyte databases with heavy write volume. Recommend a large WAL volume or to use the async option with a large volume nearby.

  • Backups are multi-threaded, but the Net::OpenSSH library does not appear to be 100% threadsafe so it will very occasionally lock up on a thread. There is an overall process timeout that resolves this issue by killing the process. Yes, very ugly.

  • Checksums are lost on any resumed backup. Only the final backup will record checksum on multiple resumes. Checksums from previous backups are correctly recorded and a full backup will reset everything.

  • The backup.manifest is being written as Storable because Config::IniFile does not seem to handle large files well. Would definitely like to save these as human-readable text.

  • Absolutely no documentation (outside the code). Well, excepting these release notes.

  • Lots of other little things and not so little things. Much refactoring to follow.