RE: pgbackrest question

I agree, why – what is the point of archiving wals outside of backup to a different location? This is a general want to learn question and not a critque. Thanks. Thinking outloud – I would think you would want wals in the same location outside of backup so pgbackrest can restore to any time outside of the backup window for optimal point in time recovery.

From: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
Sent: Wednesday, July 22, 2026 4:22 PM
To: pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: pgbackrest question

On Wed, Jul 22, 2026 at 4: 13 PM Murthy Nunna <mnunna@ fnal. gov> wrote: Hi, I am new to pgbackrest… Using pgbackrest is it possible to run a backup that includes WALs that spans the duration of the backup ONLY. I prefer to archive WALs outside

On Wed, Jul 22, 2026 at 4:13 PM Murthy Nunna <mnunna(at)fnal(dot)gov<mailto:mnunna(at)fnal(dot)gov>> wrote:
Hi,

I am new to pgbackrest… Using pgbackrest is it possible to run a backup that includes WALs that spans the duration of the backup ONLY. I prefer to archive WALs outside of pgbackrest for the routine archiving.

Why? pgbackrest does a great job managing WALs and data backups, keeping everything consistent.

More importantly, during restore, pgbackrest assumes that all the WALs will be where it thinks they are. Thus, while the backups might work, restores would fail.

And if that is possible, can I use such a backup for PITR by providing the required WALs that go beyond the backup duration?

This is something I can do today using pg_basebackup. I am looking to mimic this using pgbackrest.

pgbackrest is not pg_basebackup; do not try to make pgbackrest act like pg_basebackup.

--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!