Hola Guillermo,
Given that you are upgrading from 2.x to 3.x, I suggest testing a 3.9
backup system with a working configuration.
Once you have that working as expected, do the following:
- disable `barman cron`
- upgrade `barman` from 2.18 to 2.9 (apt upgrade barman)
- make any modifications to the barman configuration based on the
tests you ran earlier
- You may need to stop and restart the pg_receivewal process. This is
documented in the website's doc, in the barman man page, and in the
output from `barman receive-wal --help`
- run `barman cron` manually and verify that WALs are being archived
to the right place and retention policies are being applied as
expected
- test backups by running a `barman backup`
After each step run `barman check` to make sure that things are
working as expected. Also, test, test, and test before moving anything
to production.
Saludos, 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 on the web, visit
https://groups.google.com/d/msgid/pgbarman/5c78da95-ca1b-4501-9042-b0f9d0a5b634n%40googlegroups.com.