Re: Setting up continuous archiving

From: talk to ben <blo(dot)talkto(at)gmail(dot)com>
To: yuri(dot)kanivetsky(at)gmail(dot)com
Cc: ptim007(at)yahoo(dot)com, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Setting up continuous archiving
Date: 2018-10-15 13:24:36
Message-ID: CAPE8EZ4RfNVkE-JZvyTUBpkbGsJuHQ0v9QcLdmZNM6YFaHycLw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi,

I am not sure what you call discrete / continuous.
pgbackrest allows backups of different kinds: full, incremental and
differential.
It keeps the wals necessary to recover since the oldest backup until the
current time.
The retention is expressed in number of full backups. You can also specify
a number of differential backups.
You have the choice to keep the wal necessary to restore to the end of the
backup in the backup directory itself in addition to the archive directory.
If you use this method (parameter archive-copy) the backup is "standalone"
and you can copy it out of the pgbackrest backup repository and keep it
forever.

Le lun. 15 oct. 2018 à 12:31, Yuri Kanivetsky <yuri(dot)kanivetsky(at)gmail(dot)com> a
écrit :

> pgBackRest doesn't seem to allow the latter: recovery to any point in
> time, only to some discrete moments. Correct me if I'm wrong.
>

Are you talking about PITR ?
https://pgbackrest.org/user-guide.html#pitr

Is that doable with both of them (pgBackRest, Barman)? Does it make
> sense to use repmgr with pgBackRest?
>

It's doable but remgr and barman are supposed to work together more
seemlessly since they re both products of 2ndQ.
But does it make sense to use repmgr ?

My opinion: I use pgbackrest for three years now and am very happy with it.
My choice was made based on personal preference, features (at the time
there was more discrepencies) and I prefered the overall design.
I use corosync & pacemaker with PAF for HA so I never had to use repmgr.

Benoit.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2018-10-15 14:24:23 Re: Regarding varchar max length in postgres
Previous Message Adrian Klaver 2018-10-15 13:20:23 Re: FATAL: terminating connection because protocol synchronization was lost