Re: broken backup trail in case of quickly patroni switchback andforth - Mailing list pgsql-general

From Laurenz Albe
Subject Re: broken backup trail in case of quickly patroni switchback andforth
Date
Msg-id f284269e5b4bd64f69ce04a9c190dd254f606762.camel@cybertec.at
Whole thread Raw
In response to broken backup trail in case of quickly patroni switchback and forth  ("Zwettler Markus (OIZ)" <Markus.Zwettler@zuerich.ch>)
Responses AW: broken backup trail in case of quickly patroni switchback andforth
List pgsql-general
On Thu, 2019-11-07 at 13:52 +0000, Zwettler Markus (OIZ) wrote:
> we are using Patroni for management of our Postgres standby databases.
> 
> we take our (wal) backups on the primary side based on intervals and thresholds.
> our archived wal's are written to a local wal directory first and moved to tape afterwards.
> 
> we got a case where Patroni switched back and forth sides quickly, e.g.:
> 12:00h: primary - standby
> 12:05h: standby - primary
> 12:10h: primary - standby
> 
> we realised that we will not have a wal backup of those wal's generated between 12:05h and 12:10h in this scenario.
> 
> how can we make sure that the whole wal sequence trail will be backuped? any idea?

You'll have to archive WAL from both machines.  Then you have everything you should need.

Make sure "recovery_target_timeline = 'latest'" so that recovery will
follow the timeline jumps.

Yours,
Laurenz Albe
-- 
Cybertec | https://www.cybertec-postgresql.com




pgsql-general by date:

Previous
From: "Zwettler Markus (OIZ)"
Date:
Subject: AW: AW: AW: broken backup trail in case of quickly patroni switchbackand forth
Next
From: "Brad Nicholson"
Date:
Subject: Re: AW: AW: AW: broken backup trail in case of quickly patroni switchbackand forth