public inbox for [email protected]
help / color / mirror / Atom feedcould not find a valid record after in barman's backups
5+ messages / 3 participants
[nested] [flat]
* could not find a valid record after in barman's backups
@ 2025-11-06 10:06 lejeczek <[email protected]>
2025-11-06 12:03 ` AW: could not find a valid record after in barman's backups William Sescu (Suva) <[email protected]>
2025-11-06 14:49 ` Re: could not find a valid record after in barman's backups Ron Johnson <[email protected]>
0 siblings, 2 replies; 5+ messages in thread
From: lejeczek @ 2025-11-06 10:06 UTC (permalink / raw)
To: [email protected]
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?
many thanks, L.
^ permalink raw reply [nested|flat] 5+ messages in thread
* AW: could not find a valid record after in barman's backups
2025-11-06 10:06 could not find a valid record after in barman's backups lejeczek <[email protected]>
@ 2025-11-06 12:03 ` William Sescu (Suva) <[email protected]>
2025-11-06 14:01 ` Re: AW: could not find a valid record after in barman's backups lejeczek <[email protected]>
1 sibling, 1 reply; 5+ messages in thread
From: William Sescu (Suva) @ 2025-11-06 12:03 UTC (permalink / raw)
To: [email protected] <[email protected]>; +Cc: lejeczek <[email protected]>
The WAL files on the Barman Server might be compressed, depending on your Barman compression setting.
e.g. compression = gzip, or you are using a different PostgreSQL pg_waldump version, than the one on your
PostgreSQL host.
Cheers, William
Von: lejeczek <[email protected]>
Gesendet: Donnerstag, 6. November 2025 11:06
An: [email protected]
Betreff: could not find a valid record after in barman's backups
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?
many thanks, L.
________________________________
Disclaimer:
Diese Nachricht und ihr eventuell angehängte Dateien sind nur für den Adressaten bestimmt. Sie kann vertrauliche oder gesetzlich geschützte Daten oder Informationen beinhalten. Falls Sie diese Nachricht irrtümlich erreicht hat, bitten wir Sie höflich, diese unter Ausschluss jeglicher Reproduktion zu löschen und die absendende Person zu benachrichtigen. Danke für Ihre Hilfe.
This message and any attached files are for the sole use of the recipient named above. It may contain confidential or legally protected data or information. If you have received this message in error, please delete it without making any copies whatsoever and notify the sender. Thank you for your assistance.
Attachments:
[application/pkcs7-signature] smime.p7s (5.8K, ../../GV0P278MB0244502340016DA093363B7BE8C2A@GV0P278MB0244.CHEP278.PROD.OUTLOOK.COM/3-smime.p7s)
download
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: AW: could not find a valid record after in barman's backups
2025-11-06 10:06 could not find a valid record after in barman's backups lejeczek <[email protected]>
2025-11-06 12:03 ` AW: could not find a valid record after in barman's backups William Sescu (Suva) <[email protected]>
@ 2025-11-06 14:01 ` lejeczek <[email protected]>
0 siblings, 0 replies; 5+ messages in thread
From: lejeczek @ 2025-11-06 14:01 UTC (permalink / raw)
To: [email protected] <[email protected]>
across different OSes - which is my env - I should have
thought of this, different versions yes.
thanks, L.
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: could not find a valid record after in barman's backups
2025-11-06 10:06 could not find a valid record after in barman's backups lejeczek <[email protected]>
@ 2025-11-06 14:49 ` Ron Johnson <[email protected]>
2025-11-07 17:54 ` Re: could not find a valid record after in barman's backups lejeczek <[email protected]>
1 sibling, 1 reply; 5+ messages in thread
From: Ron Johnson @ 2025-11-06 14:49 UTC (permalink / raw)
To: Pgsql-admin <[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!
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: could not find a valid record after in barman's backups
2025-11-06 10:06 could not find a valid record after in barman's backups lejeczek <[email protected]>
2025-11-06 14:49 ` Re: could not find a valid record after in barman's backups Ron Johnson <[email protected]>
@ 2025-11-07 17:54 ` lejeczek <[email protected]>
0 siblings, 0 replies; 5+ messages in thread
From: lejeczek @ 2025-11-07 17:54 UTC (permalink / raw)
To: Pgsql-admin <[email protected]>
and yes /restore/ does restore - even though the host is
with different pgsql' libs version, but it does not restore
PITR.
So I wonder now - perhaps PITR not working is not due to the
"well-know" issue, maybe it was but it's not any more, but
it's in my case due to the fact that pgsql server(16) and
barman(13) use different pgsql versions - I'll tamper some
more some day.
thanks, L.
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2025-11-07 17:54 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-11-06 10:06 could not find a valid record after in barman's backups lejeczek <[email protected]>
2025-11-06 12:03 ` AW: could not find a valid record after in barman's backups William Sescu (Suva) <[email protected]>
2025-11-06 14:01 ` Re: AW: could not find a valid record after in barman's backups lejeczek <[email protected]>
2025-11-06 14:49 ` Ron Johnson <[email protected]>
2025-11-07 17:54 ` lejeczek <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox