Oxford, United Kingdom – May 17, 2019

2ndQuadrant today announced the release of Barman version 2.8, introducing support for incremental backup in geo-redundancy. It also includes various performance enhancements and bug fixes.

Barman 2.8 deprecates support for PostgreSQL 9.3 and older versions, and declares official support for Python 3 – deprecating Python 2.

Barman (Backup and Recovery Manager) is an open source administration tool for managing backup and disaster recovery of PostgreSQL servers. It allows you to perform remote backups of multiple servers in business-critical environments and helps DBAs during the recovery phase.

This release includes performance enhancements and other changes listed below:

  • Add support for reuse_backup in geo-redundancy for incremental backup copy in passive nodes
  • Improve performance of rsync based copy by using strptime instead of the more generic dateutil.parser
  • Add –test option to barman-wal-archive and barman-wal-restore to verify the connection with the Barman server
  • Complain if backup_options is not explicitly set, as the future default value will change from exclusive_backup to concurrent_backup when PostgreSQL 9.5 will be declared EOL by the PGDG
  • Display additional settings in the show-server and diagnose commands: archive_timeout, data_checksums, hot_standby, max_wal_senders, max_replication_slots
    and wal_compression.
  • Merge the barman-cli project in Barman

We strongly recommend upgrading to Barman v2.8 at the earliest opportunity available.

Upgrade Information
Users of rsync backup method on a primary server should set backup_options to either concurrent_backup (recommended for PostgreSQL 9.6 or higher) or exclusive_backup (current default) before upgrading to Barman 2.8.

A complete list of changes and bug fixes is available here.

Download and installation instructions are available here.

Source files are available for download here.

Barman is developed and maintained by 2ndQuadrant and distributed under GPL v3.

For more information, please send an email to [email protected]