Hello Tatyana,
That is the way that Barman does a recovery with PITR and no-get-wal.
There isn't an easy way to know which WALs would be needed and which
ones won't, so we send all available WALs.
What you can do to overcome this issue is use the `--get-wal` option,
preferably with the `barman-cli` package installed on the remote node
(where postgres will be recovered). That way, barman will not copy any
WALs, and instead will add a `restore_command` line in the postgres
configuration so Postgres asks the Barman server for the WALs
on-demand.
Hope this clarifies the situation and gives you a solution.
Kind regards, Martín
> --
> --
> 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, visit
https://groups.google.com/d/msgid/pgbarman/bb31d907-7b31-47d8-8be1-17af2c28b200n%40googlegroups.com.