MIME-Version: 1.0
References: <718d5e0c-f353-4318-9581-00ce903f2571.ref@yahoo.co.uk>
 <718d5e0c-f353-4318-9581-00ce903f2571@yahoo.co.uk>
In-Reply-To: <718d5e0c-f353-4318-9581-00ce903f2571@yahoo.co.uk>
From: Ron Johnson <ronljohnsonjr@gmail.com>
Date: Thu, 6 Nov 2025 09:49:30 -0500
Message-ID: 
 <CANzqJaAE9PpMfKmueA1LaUk-O=+wpyyjhQTdzofr0Nf6c_-V4g@mail.gmail.com>
Subject: Re: could not find a valid record after in barman's backups
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000d5b2670642ee2c67"
Archived-At: 
 <https://www.postgresql.org/message-id/CANzqJaAE9PpMfKmueA1LaUk-O%3D%2BwpyyjhQTdzofr0Nf6c_-V4g%40mail.gmail.com>
Precedence: bulk

--000000000000d5b2670642ee2c67
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, Nov 6, 2025 at 5:06=E2=80=AFAM lejeczek <peljasz@yahoo.co.uk> 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.

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

--000000000000d5b2670642ee2c67
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Thu, Nov 6, 2025 at 5:06=E2=80=AFAM le=
jeczek &lt;<a href=3D"mailto:peljasz@yahoo.co.uk">peljasz@yahoo.co.uk</a>&g=
t; wrote:</div><div class=3D"gmail_quote gmail_quote_container"><blockquote=
 class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px so=
lid rgb(204,204,204);padding-left:1ex"><u></u>

 =20

   =20
 =20
  <div>
    <font size=3D"2" face=3D"Courier 10 Pitch">Hi guys.<br>
      <br>
      I know it&#39;s not strictly=C2=A0<i>barman</i>=C2=A0list but I presu=
me many
      here use it.<br>
      I do, but I only now realized that using barman&#39;s=C2=A0<i>recover=
y</i>=C2=A0with
      PIT is faulty - apparently have been for a while.<br>
      So I wonder - besides the fault(s) - I must be missing something
      or doing something incorrectly for...<br>
      when I check backups=C2=A0<i>wals</i>=C2=A0I get:<br>
      <br>
      -&gt; $ pg_waldump
      ubusrv-master-10-1-1-88/wals/00000B000000000D/00000B000000000D0000003=
0<br>
      pg_waldump: fatal: could not find a valid record after D/30000000<br>
      <br>
      and that is for every=C2=A0<i>wal</i>=C2=A0in the backup - which has =
to
      wrong, no?<br>
      How &amp; where do I start troubleshooting this?</font></div></blockq=
uote><div>=C2=A0</div><div>Can <i>barman</i> restore the instance?=C2=A0 Fo=
r example, pg_waldump would barf on WALs in a PgBackRest repo because it=
9;s encrypted in addition to being compressed, even though pgbackrest does =
PITR restores without complaint.</div></div><div><br></div><span class=3D"g=
mail_signature_prefix">-- </span><br><div dir=3D"ltr" class=3D"gmail_signat=
ure"><div dir=3D"ltr">Death to &lt;Redacted&gt;, and butter sauce.<div>Don&=
#39;t boil me, I&#39;m still alive.<br><div><div>&lt;Redacted&gt; lobster!<=
/div></div></div></div></div></div>

--000000000000d5b2670642ee2c67--