pg.ddx.io  pgbackrest/pgbackrest GitHub issues and pull requests  
help / color / mirror / Atom feed
From: dwsteele (@dwsteele) <noreply+dwsteele@github.com>
To: pgbackrest/pgbackrest <noreply+pgbackrest-pgbackrest@github.com>
Subject: Re: [pgbackrest/pgbackrest] issue #2920: Question: re-import "expired" backup sets
Date: Fri, 13 Nov 2026 11:44:32 +0000
Message-ID: <gh-pgbackrest-pgbackrest-2920-c6851870761@github.com> (raw)
In-Reply-To: <gh-pgbackrest-pgbackrest-2920@github.com>
References: <gh-pgbackrest-pgbackrest-2920@github.com>

Copying expired backups back into the active repo does work but is not tested or supported. Even if they are added back to backup.info the next expire will remove them again.

A better, safer, and supported way to do this is to restore the old repo from tape to a separate location and use it as repo2 next to your current repo. Restore the complete stanza directories under archive/ and backup/ from the same point in time, including backup.info and archive.info, and make sure any diff/incr backup you want has the backups it depends on.

If you restore with --type=time (or lsn) pgBackRest will use a backup from repo2 when repo1 has none old enough, or you can select one with --set. WAL required for recovery is fetched from both repos.

Do not add repo2 to the configuration used by archive-push and backup, since archive-push will then push WAL to repo2 as well. Put repo2 in a separate config file and pass it with --config to restore. Command-line options are copied into restore_command so recovery will use the same config.

view thread (9+ messages)  latest in thread

Message-ID: <gh-pgbackrest-pgbackrest-2920-c6851870761@github.com>
Permalink:  ../gh-pgbackrest-pgbackrest-2920-c6851870761@github.com/

 · 


This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox