pgbackrest with PAF(corosync and pacmaker)

Started by Ajay Pratapover 6 years ago2 messagesgeneral
Jump to latest
#1Ajay Pratap
ajaypratap@ameyo.com

##Arch
OS: Centos 7
PostgreSQL 10
pgbackrest 2.18
PAF: two nodes(primary and secondary ) with corosync and pacemaker

##Query
I am using pacemaker and corosync to setup two nodes High availability
cluster for postgreSQL 10. In the scenario I want to setup timely backup
with pgbackrest.
Using the _backup from standby_ feature I could able to take backup from my
secondary postgres. But if secondary postgres is down, it does not take
backup from primary.

What I want?
I want to take backup from secondary postgres (--backup-standby), If
secondary is unavailable, take backup from primary postgres.
Or if Primary postgres goes down backup should still continues from
secondary (which would have been promoted to master now)

All backups are with remote repository
pgbackrest.conf for repo:

*[data]pg1-host=pgprimarypg1-path=/var/lib/pgsql/10/datapg2-host=pgsecpg2-path=/var/lib/pgsql/10/data[global]backup-standby=yprocess-max=3repo1-path=/var/lib/pgbackrestrepo1-retention-full=2start-fast=y*

pgbackrest for primary and secondary postgres:

*[data]pg1-host=mainpg1-path=/var/lib/pgsql/10/datapg2-host=secpg2-path=/var/lib/pgsql/10/data[global]backup-standby=nprocess-max=3repo1-path=/var/lib/pgbackrestrepo1-retention-full=2start-fast=y*

Is there any way to achieve this?
This sounds like a generic problem? Or am I doing something wrong

Regards,
ajay

--

*Disclaimer:* The information in this communication is confidential and
may be legally privileged. It is intended solely for the use of the
individual or entity to whom it is addressed and others authorized to
receive it. If you are not the intended recipient you are hereby notified
that any disclosure, copying, distribution or taking action in reliance of
the contents of this information is strictly prohibited and may be
unlawful. Drishti is neither liable for the improper, incomplete
transmission of the information contained in this communication nor any
delay in its receipt. The communication is not intended to operate as an
electronic signature under any applicable law. Drishti assumes no
responsibility for any loss or damage resulting from the use of e-mails.

#2David Steele
david@pgmasters.net
In reply to: Ajay Pratap (#1)
Re: pgbackrest with PAF(corosync and pacmaker)

On 10/17/19 9:48 AM, Ajay Pratap wrote:

I am using pacemaker and corosync to setup two nodes High availability
cluster for postgreSQL 10. In the scenario I want to setup timely backup
with pgbackrest.
Using the _backup from standby_ feature I could able to take backup from
my secondary  postgres. But if secondary postgres is down, it does not
take backup from primary.

This is entirely on purpose. Backup from standby is designed to reduce
load on the primary so we believe it is counter-intuitive to put load
back on the primary when the standby is down. Running backups *at all*
when degraded is usually a bad idea.

Is there any way to achieve this?

You can run more than one standby and pgBackRest will automatically
select the first one it finds that is up. If you must take a backup
when degraded then you can specify --no-backup-standby on the command
line to disable standby for that one backup.

Regards,
--
-David
david@pgmasters.net