9 July 2020: 2ndQuadrant is proud to announce the release of Barman version 2.11, a Backup and Recovery Manager for PostgreSQL.
This minor release introduces the
barman-cli-cloud package, which contains all cloud related utilities previously released with version 2.10, such as
barman-cloud-backup, as well as 3 additional ones:
barman-cloud-wal-restore: script to be used as
restore_commandin PostgreSQL to directly retrieve WAL files from an object store such as AWS S3;
barman-cloud-restore: script to be used to retrieve a backup from an object store and prepare the recovery of a PostgreSQL instance;
barman-cloud-backup-list: script to be used to list the content of an object store.
If you are upgrading from version 2.10 and are already using
barman-cloud-backup, you must install the
barman-cli-cloud package as described in the release notes.
In terms of security, Barman now supports non superuser connections to a PostgreSQL 10 (or higher) database. The user requires
pg_read_all_stats privileges, as well as execution grants on some backup related functions. Please refer to the documentation for more details.
The upcoming PostgreSQL 13 is fully supported.
Minor bugs have also been fixed.
For a complete list of changes, please refer to the release notes for version 2.11.
- Man page, section 1
- Man page, section 5
- pgespresso extension
Introduction of the
barman-cli-cloudpackage that contains all cloud related utilities.
barman-cloud-wal-restoreto restore a WAL file previously archived with
barman-cloud-wal-archivefrom an object store
barman-cloud-restoreto restore a backup previously taken with
barman-cloud-backupfrom an object store
barman-cloud-backup-listto list backups taken with
barman-cloud-backupin an object store
Add support for arbitrary archive size for
Add support for
--endpoint-urloption to cloud utilities
Remove strict superuser requirement for PG 10+ (by Kaarel Moppel)
--log-levelruntime option for
barmanto override default log level for a specific command
Support for PostgreSQL 13
- Suppress messages and warning with SSH connections in barman-cli (GH-257)
- Fix a race condition when retrieving uploaded parts in barman-cloud-backup (GH-259)
- Close the PostgreSQL connection after a backup (GH-258)
- Check for uninitialized replication slots in receive-wal --reset (GH-260)
- Ensure that begin_wal is valorised before acting on it (GH-262)
- Fix bug in XLOG/WAL arithmetic with custom segment size (GH-287)
- Fix rsync compatibility error with recent rsync
- Fix PostgreSQLClient version parsing
- Fix PostgreSQL exception handling with non ASCII messages
- Ensure each postgres connection has an empty search_path
- Avoid connecting to PostgreSQL while reading a backup.info file
If you are using already
barman-cloud-backup installed via RPM/Apt package and you are upgrading your system, you must install the
barman-cli-cloud package. All cloud related tools are now part of the
barman-cli-cloud package, including
barman-cloud-backup that were previosly shipped with
barman-cli. The reason is complex dependency management of the
boto3 library, which is a requirement for the cloud utilities.
- Release Notes
- RPM repositories
- Deb repositories
- Online documentation
- PDF documentation
- pgespresso on PostgreSQL Extension framework (PGXN)
- pgespresso RPM/Debian packages
Barman is an open-source administration tool for backup and disaster recovery of PostgreSQL servers written in Python. It allows organizations to perform remote backups of multiple servers in business critical environments and help DBAs during the recovery phase.
Barman is developed and maintained by 2ndQuadrant and distributed under GPL v3.
2ndQuadrant was founded in 2001 by Simon Riggs, a major developer of the PostgreSQL project. As the largest single collective organization of PostgreSQL experts of any company globally, it is 2ndQuadrant's mission to provide the gold standard of products and services to support PostgreSQL and its continuous growth. Comprised of some of the best known developers from around the globe, all members actively contribute to the development of PostgreSQL.