Barman (backup and recovery manager) for PostgreSQL is an administration tool for disaster recovery of PostgreSQL servers. It allows remote backups of multiple servers in business-critical environments and helps DBAs during the recovery phase. Barman's most-wanted features include backup catalogs, retention policies, remote recovery, archiving, and compression of WAL files and backups.
|Tags||Disaster Recovery database backup Database postgres postgresql business continuity|
|Operating Systems||Mac OS X FreeBSD Unix Linux|
We have released a video of Barman that in 83 seconds explain the importance of a disaster recovery solution for your PostgreSQL databases.
Release Notes: This major release has a new code infrastructure in terms of output, subprocesses, remote commands, file system, events (‘hooks’) and metadata management, making the application more robust. It introduces a few configuration options for managing hook scripts before and after archiving a WAL file, network compression of remote backup and recovery operations, and immediate checkpoint at backup time. Remote recovery code has been improved in order to behave exactly like local recovery does, including preparation of the directories layout. A few minor bugs have been fixed.
Release Notes: This minor release adds compatibility with PostgreSQL 9.3. It also introduces support for the "--target-name" recovery option, which allows it to restore to a named point previously specified with pg_create_restore_point (only for PostgreSQL 9.1 and above users). Experimental compatibility with Python 3 has been added. Minor bugs have been fixed.
Release Notes: This minor version adds the "bandwidth_limit" global/server option which allows limiting the I/O bandwidth (in KBPS) for backup and recovery operations. More control is given by the "tablespace_bandwidth_limit" global/server option, which allows limiting the I/O bandwidth (in KBPS) for backup and recovery operations on a per-tablespace basis. Minor bugs have been fixed.
Release Notes: This is a major release that introduces automated support for retention policies based on the redundancy of periodical backups or recovery window. Retention policies are integrated by a safety mechanism that allows administrators to specify a minimum number of periodical backups that must exist at any time for a server. This version fixes minor bugs and adds minor features.
Release Notes: This version adds the "configuration_files_directory" option that allows administrators to include multiple server configuration files from a directory (e.g. /etc/barman.d). The following aliases for special backup identifiers (ID) are now supported: latest, last, oldest, and first. With 'barman list-backup all', you can now list backups for all the configured servers. This release honors the "application_name" option for connection information on PostgreSQL >= 9.0. It fixes an important bug: missing WAL files are now ignored during deletion (#18).