Barman 2.6 introduces support for geo-redundancy, meaning that Barman can now copy from another Barman instance, not just a PostgreSQL database.
Today our Devops team at 2ndQuadrant, led by my dear friend and trusted colleague Marco Nenciarini, released version 2.3 of Barman.
In Part 3 of this series (here are Part 1 and Part 2), I would like to demonstrate how the development of a new feature for Barman would flow through the Kanban board.
Barman 2.2 introduces support for parallel copy, by improving performance of both backup and recovery operations in your PostgreSQL disaster recovery solution.
If you live in the Melbourne area and you are passionate about PostgreSQL then don’t miss the chance to come to the Melbourne PostgreSQL Users Group Meetup this Monday, 21 November.
Now Available! Debian and Ubuntu packages for Power Architecture. The official announcement was published last Friday, September 30, 2016: the PostgreSQL repository for Debian and Ubuntu packages, apt.postgresql.org, has been extended by adding binary packages of IBM’s Little Endian POWER8 architecture.
This is my (very) biased opinion, but I am ready to bet that once you try Barman 2.0 you’ll agree with me.
Starting from Barman 1.6.1, PostgreSQL standby servers can rely on an “infinite” basin of WAL files and finally pre-fetch batches of WAL files in parallel from Barman, speeding up the restoration process as well as making the disaster recovery solution more resilient as a whole. The master, the backup and the standby Before we start, […]
PostgreSQL 9.6 has extended the traditional framework available for physical backups by allowing users to take backups concurrently. Barman will transparently support this new set of functions without requiring the pgespresso extension.
The upcoming version 1.6.1 of Barman will introduce a few interesting new features which consolidate its central role in business continuity installations of PostgreSQL databases. Discover why.