db/pgbackrest
1
0
Fork 0
mirror of https://github.com/pgbackrest/pgbackrest.git synced 2025-02-03 13:21:32 +02:00
Code Issues Releases Activity

Update NEWS.md for new version and features.

Browse Source
This commit is contained in:
David Steele 2023-06-12 15:41:39 +02:00 committed by GitHub
parent 6875358d11
commit 396e237d53
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 15 additions and 23 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

38
doc/NEWS.md
View File

@ -1,42 +1,34 @@
**February 10, 2022**: [Crunchy Data](https://www.crunchydata.com) is pleased to announce the release of [pgBackRest](https://pgbackrest.org/) 2.37, the latest version of the reliable, easy-to-use backup and restore solution that can seamlessly scale up to the largest databases and workloads.
**June 12, 2023**: [Crunchy Data](https://www.crunchydata.com) is pleased to announce the release of [pgBackRest](https://pgbackrest.org/) 2.46, the latest version of the reliable, easy-to-use backup and restore solution that can seamlessly scale up to the largest databases and workloads.
pgBackRest has recently introduced many exciting new features including a built-in TLS server, binary protocol, new authentication methods, backup history retention, restore enhancements, backup integrity enhancements, and increased option indexes.
Over the last year pgBackRest has introduced many exciting new features including block incremental backup, file bundling, repository verification, backup annotations, and SFTP repository storage.
IMPORTANT NOTE: pgBackRest 2.37 is the last version to support PostgreSQL 8.3/8.4.
IMPORTANT NOTE: pgBackRest 2.44 is the last version to support PostgreSQL 9.0/9.1/9.2.
pgBackRest supports a robust set of features for managing your backup and recovery infrastructure, including: parallel backup/restore, full/differential/incremental backups, multiple repositories, delta restore, parallel asynchronous archiving, per-file checksums, page checksums (when enabled) validated during backup, multiple compression types, encryption, partial/failed backup resume, backup from standby, tablespace and link support, S3/Azure/GCS support, backup expiration, local/remote operation via SSH or TLS, flexible configuration, and more.
pgBackRest supports a robust set of features for managing your backup and recovery infrastructure, including: parallel backup/restore, full/differential/incremental backups, block incremental backup, multiple repositories, delta restore, parallel asynchronous archiving, per-file checksums, page checksums (when enabled) validated during backup, multiple compression types, encryption, partial/failed backup resume, backup from standby, tablespace and link support, S3/Azure/GCS/SFTP support, backup expiration, local/remote operation via SSH or TLS, flexible configuration, and more.
You can install pgBackRest from the [PostgreSQL Yum Repository](https://yum.postgresql.org/) or the [PostgreSQL APT Repository](https://apt.postgresql.org). Source code can be downloaded from [releases](https://github.com/pgbackrest/pgbackrest/releases).
pgBackRest can be installed from the [PostgreSQL Yum Repository](https://yum.postgresql.org/) or the [PostgreSQL APT Repository](https://apt.postgresql.org). Source code can be downloaded from [releases](https://github.com/pgbackrest/pgbackrest/releases).
## Major New Features
### TLS Server
### Block Incremental Backup
The TLS server provides an alternative to SSH for remote operations such as backup. Containers benefit because pgBackRest can be used as the entry point without any need for SSH. In addition, performance tests have shown TLS to be significantly faster than SSH. See [User Guide](https://pgbackrest.org/user-guide-rhel.html#repo-host/setup-tls).
Block incremental backup saves space in the repository by only storing file parts that have changed since the prior backup. In addition to space savings, this feature makes backup faster since there is less data to compress and transfer. Delta restore is also improved because less data from the repository is required to restore files. See [User Guide](https://pgbackrest.org/user-guide-rhel.html#backup/block) and [pgBackRest File Bundling and Block Incremental Backup](https://www.crunchydata.com/blog/pgbackrest-file-bundling-and-block-incremental-backup).
### Binary Protocol
### File Bundling
The binary protocol provides a faster and more memory efficient way for pgBackRest to communicate with local and remote processes while maintaining the ability to communicate between different architectures.
File bundling combines smaller files to improve the efficiency of repository reads and writes, especially on object stores such as S3, Azure, and GCS. Zero-length files are stored only in the manifest. See [User Guide](https://pgbackrest.org/user-guide-rhel.html#backup/bundle) and [pgBackRest File Bundling and Block Incremental Backup](https://www.crunchydata.com/blog/pgbackrest-file-bundling-and-block-incremental-backup).
### New Authentication Methods
### Verify
The GCS storage driver now supports automatic authentication on GCE instances and the S3 storage driver supports WebIdentity authentication. See [Config Reference](https://pgbackrest.org/configuration.html#section-repository/option-repo-gcs-key-type).
The `verify` command checks that files in the repository have not been lost or corrupted and generates a report when problems are found. See [Command Reference](https://pgbackrest.org/command.html#command-verify).
### Additional Backup Integrity Checks
### Backup Key/Value Annotations
A number of integrity checks were added to ensure the backup is valid or errors are detected as early as possible, including: loop while waiting for checkpoint LSN to reach replay LSN, check archive immediately after backup start, timeline and checkpoint checks before backup, check that clusters are alive and correctly configured during a backup, and warn when checkpoint_timeout exceeds db-timeout.
Backup annotations allow custom annotations to be stored with a backup and queried with the `info` command. See [User Guide](https://pgbackrest.org/user-guide-rhel.html#backup/annotate).
### Increase Maximum Index Allowed for PG/REPO Options to 256
### SFTP Repository Storage
Up to 256 PostgreSQL clusters and repositories may now be configured.
### Restore Enhancements
The restore command has a number of new features, including: db-exclude option (see [Config Reference](https://pgbackrest.org/configuration.html#section-restore/option-db-exclude)), link-map option can create new links (see [Config Reference](https://pgbackrest.org/configuration.html#section-restore/option-link-map)), automatically create data directory, restore --type=lsn (See [Command Reference](https://pgbackrest.org/command.html#command-restore/category-command/option-type)), and error when restore is unable to find a backup to match the time target.
### Backup History Retention
The backup manifest history can now be expired. See [Config Reference](https://pgbackrest.org/configuration.html#section-repository/option-repo-retention-history).
Repositories can now be stored on an SFTP server. See [User Guide](https://pgbackrest.org/user-guide-rhel.html#sftp-support).
## Links
- [Website](https://pgbackrest.org)