![]() ![]() 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. Files that were already copied are compared with the checksums in the manifest to ensure integrity. Backup ResumeĪn interrupted backup can be resumed from the point where it was stopped. This feature allows page-level corruption to be detected early, before backups that contain valid copies of the data have expired. 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. All page checksums are validated during a full backup and checksums in files that have changed are validated during differential and incremental backups. If page checksums are enabled pgBackRest will validate the checksums for every file that is copied during a backup. PostgreSQL has supported page-level checksums since 9.3. This is advantageous for terabyte-scale databases that are time consuming to restore in the traditional way.Īll operations utilize file and directory level fsync to ensure durability. 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. After a backup finishes copying files, it waits until every WAL segment required to make the backup consistent reaches the repository.īackups in the repository may be stored in the same format as a standard PostgreSQL cluster (including tablespaces). Backup IntegrityĬhecksums are calculated for every file in the backup and rechecked during a restore or verify. In the latter case WAL required to make older backups consistent will be maintained in the archive. The WAL archive can be maintained for all backups or strictly for the most recent backups. Retention polices can be set for full and differential backups to create coverage for any time frame. ![]() Block-level backups save space by only copying the parts of files that have changed. pgBackRest is not susceptible to the time resolution issues of rsync, making differential and incremental backups safe without the requirement to checksum each file. Full, Differential, & Incremental Backups (at File or Block Level)įull, differential, and incremental backups are supported. 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. ![]() An interface to query PostgreSQL is also provided via the protocol layer so that remote access to PostgreSQL is never required, which enhances security. Local or Remote OperationĪ custom protocol allows pgBackRest to backup, restore, and archive locally or remotely via TLS/SSH with minimal configuration. Please find us on GitHub and give us a star if you like pgBackRest! Features Parallel Backup & RestoreĬompression is usually the bottleneck during backup operations so pgBackRest solves this problem with parallel processing and more efficient compression algorithms such as lz4 and zstd. PgBackRest v2.47 is the current stable release. PgBackRest aims to be a reliable, easy-to-use backup and restore solution that can seamlessly scale up to the largest databases and workloads by utilizing algorithms that are optimized for database-specific requirements. ![]() Reliable PostgreSQL Backup & Restore Introduction ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |