This is not the first time that 2ndQuadrant has looked at Puppet. Gabriele Bartolini has already written an article in two parts on how to rapidly configure a PostgreSQL server through Puppet and Vagrant, accompanied by the release of the code used in the example on GitHub (http://github.com/2ndquadrant-it/vagrant-puppet-postgresql).
The 1.4.0 version of Barman adds new features such as incremental backup and automatic integration with pg_stat_archiver which aim to simplify the life of DBAs and system administrators.
“Ooooh that smell! Can’t you smell that smell?“. That’s a classic rock song by legends Lynyrd Skynyrd, I know. But also a warning that your new Barman 1.3.3 installation can now emit.
Version 1.3.3 of Barman, Backup and Recovery Manager for PostgreSQL, has been released.
Version 1.3.1 of Barman, Backup and Recovery Manager for PostgreSQL, has been released. Barman now supports concurrent backup from PostgreSQL 9.2 and 9.3 servers, using the pgespresso extension, allowing users to issue backups from a streaming replicated standby server. Read the full announcement at http://www.pgbarman.org/barman-1-3-1-released/. Many thanks for funding towards the development of this release […]
Version 1.3.0 of Barman, Backup and Recovery Manager for PostgreSQL, has been released, making the tool more robust through a new code infrastructure in terms of output, subprocesses, remote commands, file system, events (‘hooks’) and metadata management. Barman now supports: hook scripts before and after archiving a WAL file network compression of remote backup and […]
Version 1.2.3 of Barman, Backup and Recovery Manager for PostgreSQL, has been released, adding support for the upcoming PostgreSQL 9.3. Read the full announcement at http://www.pgbarman.org/barman-1-2-3-released/. 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 […]
Version 1.2.1 of Barman, Backup and Recovery Manager for PostgreSQL, has been released, introducing bandwidth limitation for both backup and recovery operations at three different levels: global, server (PostgreSQL instance) and tablespace.
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.