Recovering DB including the partial WAL

42 views
Skip to first unread message

Geraldine Oo

unread,
Jan 4, 2023, 8:36:14 PM1/4/23
to Barman, Backup and Recovery Manager for PostgreSQL
Hi All,
Previously when I tested with v3.0, when I recover, it copies the current partial WAL to the barman_wal folder for recovery. But I've upgraded to v3.2 and when I test restore, its no longer taking into consideration the partial WAL.

This is the command I used - 
barman recover POC latest /u02/pgdata/POC-2 --recovery-staging-path /tmp --target-tli latest

Processing xlog segments from streaming for POC
        00000003000000000000000D
Processing xlog segments from file archival for POC
        00000003000000000000000D
Starting local restore for server POC using backup 20230104T073555
Destination directory: /u02/pgdata/POC-3
Doing PITR. Recovery target timeline: '3'
Copying the base backup.
Staging compressed backup files on the recovery host in: /tmp/barman-staging-POC-20230104T073555
Copying required WAL segments.
Generating recovery configuration
Identify dangerous settings in destination directory.

IMPORTANT
These settings have been modified to prevent data losses

postgresql.auto.conf line 25: archive_command = false

Recovery completed (start time: 2023-01-05 01:11:51.466954+00:00, elapsed time: 13 seconds)
Your PostgreSQL server has been successfully prepared for recovery!

I have a partial WAL streaming "00000003000000000000000E.partial" - and I expected it to restore this partial WAL as well - but it's not doing that. 

How can I include the partial WAL as well? 
Thanks

Regards,


Mike Wallace

unread,
Jan 5, 2023, 4:52:35 AM1/5/23
to pgba...@googlegroups.com
Hi,

The .partial file is currently only restored when either `barman
recover` is invoked with the --get-wal argument or `get-wal` is set in
`recovery_options` in the barman config. There is an open issue [1]
for updating the behaviour so that the .partial files are included
without requiring `get-wal` - I hope to get this merged in time for a
Barman release due in March 2023.

Best,

Michael

[1]: https://github.com/EnterpriseDB/barman/issues/393
> --
> --
> You received this message because you are subscribed to the "Barman for PostgreSQL" group.
> To post to this group, send email to pgba...@googlegroups.com
> To unsubscribe from this group, send email to
> pgbarman+u...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/pgbarman?hl=en?hl=en-GB
>
> ---
> You received this message because you are subscribed to the Google Groups "Barman, Backup and Recovery Manager for PostgreSQL" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to pgbarman+u...@googlegroups.com.
> To view this discussion on the web, visit https://groups.google.com/d/msgid/pgbarman/e32029e7-ac16-43dc-8e13-5ac2e14eb23bn%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages