public inbox for [email protected]  
help / color / mirror / Atom feed
From: Ron Johnson <[email protected]>
To: Pgsql-admin <[email protected]>
Subject: Re: could not find a valid record after in barman's backups
Date: Thu, 6 Nov 2025 09:49:30 -0500
Message-ID: <CANzqJaAE9PpMfKmueA1LaUk-O=+wpyyjhQTdzofr0Nf6c_-V4g@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>

On Thu, Nov 6, 2025 at 5:06 AM lejeczek <[email protected]> wrote:

> Hi guys.
>
> I know it's not strictly *barman* list but I presume many here use it.
> I do, but I only now realized that using barman's *recovery* with PIT is
> faulty - apparently have been for a while.
> So I wonder - besides the fault(s) - I must be missing something or doing
> something incorrectly for...
> when I check backups *wals* I get:
>
> -> $ pg_waldump
> ubusrv-master-10-1-1-88/wals/00000B000000000D/00000B000000000D00000030
> pg_waldump: fatal: could not find a valid record after D/30000000
>
> and that is for every *wal* in the backup - which has to wrong, no?
> How & where do I start troubleshooting this?
>

Can *barman* restore the instance?  For example, pg_waldump would barf on
WALs in a PgBackRest repo because it's encrypted in addition to being
compressed, even though pgbackrest does PITR restores without complaint.

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


view thread (5+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: could not find a valid record after in barman's backups
  In-Reply-To: <CANzqJaAE9PpMfKmueA1LaUk-O=+wpyyjhQTdzofr0Nf6c_-V4g@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

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