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

We have a central pgBackRest server that is used to backup our PostgreSQL databases, but due to disk space constraints we have a relatively low retention period for the backup sets. However we do still retain a copy of the old WAL/backup set files found in the `archive/` and `backup/` in our offsite backups (ie. on backup tapes).

I am wondering if it is possible to restore old WAL/backup sets files to the `archive/` and `backup/` directories then "re-import" them into pgBackRest to do a DB restore? I assume this would mainly involve re-creating the missing entries in the `backup.info` file somehow.

I couldn't find any documentation about this sort of use-case, so I'm wondering if doing this is supported by pgBackRest? If not, is there some supported/recommended way to restoring a database for these "expired" backup set files?

view thread (9+ messages)  latest in thread

Message-ID: <gh-pgbackrest-pgbackrest-2920@github.com>
Permalink:  ../gh-pgbackrest-pgbackrest-2920@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