In our previous article we went through describing what retention policies are and how they can be enforced on your PostgreSQL server backups with Barman 1.2. In this post, we will go through the configuration aspects.
Defining a disaster recovery plan involves defining backup policies. A key aspect of backup policies is to define how long backup data is retained for disaster recovery purposes. This applies to all digital content, including PostgreSQL databases. Barman 1.2.0 introduces automated management of backup retention policies of PostgreSQL servers.
Barman, backup and recovery manager for PostgreSQL, is designed to manage the archive of WAL files separately from periodical backups (in Postgres terms, base backups). You can see this archive as a “continuous” stream of files from the first available backup to the last shipped file (backup available history for a server). In this article […]
It took longer than expected, but we have finally managed to release Barman as open-source under GNU GPL 3. Barman stands for “Backup and Recovery Manager” and it is an administration tool for disaster recovery of PostgreSQL servers. Currently only Linux systems are officially supported, however Python allows to plan porting and maintenance on different […]
2ndQuadrant is happy to announce the release of Barman 1.0. Barman (backup and recovery manager) is an open source administration tool for disaster recovery of PostgreSQL servers written in Python for Linux systems. It allows remote backups of multiple Postgres servers in business critical environments and helps database administrators during the recovery phase. Barman’s most […]