Re: could not find a valid record after in barman's backups
| От | Ron Johnson |
|---|---|
| Тема | Re: could not find a valid record after in barman's backups |
| Дата | |
| Msg-id | CANzqJaAE9PpMfKmueA1LaUk-O=+wpyyjhQTdzofr0Nf6c_-V4g@mail.gmail.com обсуждение исходный текст |
| Ответ на | could not find a valid record after in barman's backups (lejeczek <peljasz@yahoo.co.uk>) |
| Ответы |
Re: could not find a valid record after in barman's backups
|
| Список | pgsql-admin |
On Thu, Nov 6, 2025 at 5:06 AM 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.
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
В списке pgsql-admin по дате отправления: