You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
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.
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
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Sign in to report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
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.