Barman 1.2.1 released

1 minute read

2ndQuadrant is proud to announce the release of version 1.2.1 of Barman, Backup and Recovery Manager for PostgreSQL.

This minor release introduces support for bandwidth limitation through the bandwidth_limit option. This option allows administrators to set the maximum number of kilobytes per second for backup and recovery operations. Different bandwidth caps can be set for different servers.

More control on bandwidth limitations can be achieved through the tablespace_bandwidth_limit option that allows to cap the bandwidth usage for one or more specific PostgreSQL tablespaces.

By default, no bandwidth limitation is enforced, making Barman 1.2.1 fully compatible with configuration files from previous versions. This set of features gives administrators finer control on regular backup activities, reducing the impact of these operations on live systems.

Minor bugs have also been fixed.

For a complete list of changes, see the “Release Notes” section below.

Release Notes:

  • Added the “bandwidth_limit” global/server option which allows to limit the I/O bandwidth (in KBPS) for backup and recovery operations
  • Added the “tablespace_bandwidth_limit” global/server option which allows to limit the I/O bandwidth (in KBPS) for backup and recovery operations on a per tablespace basis
  • Added /etc/barman/barman.conf as default location
  • Bug fix: avoid triggering the minimum_redundancy check on FAILED backups (thanks to Jérôme Vanandruel)

About Barman

Barman (Backup and Recovery Manager) is an open source administration tool for disaster recovery of PostgreSQL servers written in Python. It allows your organisation to perform remote backups of multiple servers in business critical environments and help DBAs during the recovery phase. Barman’s most requested features include backup catalogues, retention policies, remote recovery, archiving and compression of WAL files and backups.