October 2015 - New version has been released

A new release is available with many new features and bugfixes

Main features

  • Add functionality to stop automatically all backup definitions for databases that have been deleted with DROP DATABASE or renamed in the PgSQL nodes running them.
  • Possibility of pausing replication on slaves nodes when taking backups of large databases to avoid the termination of the backup process by postgreSQL.
  • Possibility of activating sending of alerts via SMTP when a backup, snapshot or restore terminates with an error message.
  • Overview of databases without backup definitions in the PgSQL nodes registered in PgBackMan.
  • Possibility of viewing snapshots and restores in progress.
  • Automatic upgrade of the 'pgbackman' database to a new version via the PgBackMan shell.

For a full overview of all changes, check the release notes page

August 2014 - PgBackMan manual translated to spanish

The spanish translation of the PgBackMan manual has been released and is available from this website and GitHub.

June 2014 - First version available to the public has been released

We are proud to announce the first release available to the public of PgBackMan - PostgreSQL backup manager.

About PgBackMan

PgBackMan is a tool for managing PostgreSQL logical backups created with pg_dump and pg_dumpall.

It is designed to manage backups from thousands of databases running in multiple PostgreSQL nodes, and it supports a multiple backup server topology.

The PgBackMan code is distributed under the GNU General Public License 3 and it is written in Python and PL/PgSQL. It has been developed and tested by members of the Database Operations Group at the Center for Information Technology at the University of Oslo.

Main Features

  • Central database with metadata information.
  • PgBackMan shell for interaction with the system.
  • Management of multiple backup servers.
  • Management of multiple PostgreSQL servers.
  • Management of thousands of backups dumps through a catalogue.
  • Manual and scheduled backups.
  • Management of retention policies for backups.
  • Fully detailed backup reports.
  • Multiple predefined database backup types, CLUSTER,FULL,SCHEMA,DATA.
  • Full backup of role information for a database.
  • Full backup of database configuration for a database.
  • Automatic definitions of backups for all databases running in a PgSQL node.
  • Automatic restore procedures.
  • Autonomous pgbackman_dump program that functions even if the central database with metadata information is not available.
  • Handling of error situations.