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: Re: [pgbackrest/pgbackrest] issue #2920: Question: re-import "expired" backup sets
Date: Mon, 16 Nov 2026 04:31:35 +0000
Message-ID: <gh-pgbackrest-pgbackrest-2920-c6907375047@github.com> (raw)
In-Reply-To: <gh-pgbackrest-pgbackrest-2920@github.com>
References: <gh-pgbackrest-pgbackrest-2920@github.com>

Hi @dwsteele, thanks for the info.

One of the issues I was hitting was the the `backup.info` file was being overwritten each time a backup was being taken, but the backup set files were not. Because of this the older copies of `backup.info` were no longer available because the tape retention policy is based on "keep X copies of a file" while the backup set files themselves where still around until they expired out of the tapes due to time limits (so hang around much longer).

I guess one way to work around this is to manually take a time-stamped copy of the `backup.info` file after each pgBackRest run so we still have older copies to restore.

I note the pgBackRest repositories have a `backup.history/` directory which automatically keeps old copies of the `backup.manifest` files. Would it be possible to add support to pgBackRest to do the same for the `backup.info` (and `archive.info`?) files as well (or is this already supported)?


view thread (9+ messages)  latest in thread

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