| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | "Zwettler Markus (OIZ)" <Markus(dot)Zwettler(at)zuerich(dot)ch>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: broken backup trail in case of quickly patroni switchback and forth |
| Date: | 2019-11-07 16:45:03 |
| Message-ID: | f284269e5b4bd64f69ce04a9c190dd254f606762.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brad Nicholson | 2019-11-07 17:18:57 | Re: AW: AW: AW: broken backup trail in case of quickly patroni switchback and forth |
| Previous Message | Zwettler Markus (OIZ) | 2019-11-07 16:32:42 | AW: AW: AW: broken backup trail in case of quickly patroni switchback and forth |