| From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
|---|---|
| To: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: could not find a valid record after in barman's backups |
| Date: | 2025-11-06 14:49:30 |
| Message-ID: | CANzqJaAE9PpMfKmueA1LaUk-O=+wpyyjhQTdzofr0Nf6c_-V4g@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Thu, Nov 6, 2025 at 5:06 AM lejeczek <peljasz(at)yahoo(dot)co(dot)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.
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | lejeczek | 2025-11-07 17:54:47 | Re: could not find a valid record after in barman's backups |
| Previous Message | lejeczek | 2025-11-06 14:01:07 | Re: AW: could not find a valid record after in barman's backups |