Hi,
I am not sure what you call discrete / continuous.
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.kanivetsky@xxxxxxxxx> 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 ?
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.
