Re: Barman disaster recovery solution

From: David Steele <david(at)pgmasters(dot)net>
To: Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Barman disaster recovery solution
Date: 2019-03-01 09:40:01
Message-ID: 739bc6f3-28df-4a69-aefd-42338f4dcdb6@pgmasters.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Achilleas,

On 2/27/19 11:39 AM, Achilleas Mantzios wrote:
> On 21/2/19 9:28 π.μ., Achilleas Mantzios wrote:
>> On 21/2/19 9:17 π.μ., Julie Nishimura wrote:
>>> Does anyone use this solution? any recommenations?
>>>
>>> Thanks!
>>
>> Barman will fit most requirements. PgBackRest excels when WAL traffic
>> goes on 100000 files/day or more. I have written an article, not yet
>> publised, on a comparison on the 3 most known solutions. Will post a
>> link as soon as it gets published.
>
> Hello, as promised here is my blog :
> https://severalnines.com/blog/current-state-open-source-backup-management-postgresql

Indeed, the pgBackRest user guide is a bit out of date. I've been
meaning to update to a newer version of Postgres but haven't had the
chance. This gave me the extra nudge I needed.

The docs have been update to PG10 for the next release, though the only
visible change is to remove the `stop-auto` option since it is not
relevant to PG10.

https://github.com/pgbackrest/pgbackrest/commit/6ce3310f8a2900d1af717da8d4c3345a9016933b

Thanks!
--
-David
david(at)pgmasters(dot)net

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Thomas Güttler Lists 2019-03-01 13:54:06 Thank you. Was: Where **not** to use PostgreSQL?
Previous Message Andrew Gierth 2019-03-01 09:32:37 Re: Overloaded && operator from intarray module prevents index usage.