Barman

Features

- Change `barman diagnose` output date format to ISO8601.

- Add Google Cloud Storage (GCS) support to barman cloud.

- Support `current` and `latest` recovery targets for the `--target-tli`
option of `barman recover`.

- Add documentation for installation on SLES.

Bug fixes

- `barman-wal-archive --test` now returns a non-zero exit code when
an error occurs.

- Fix `barman-cloud-check-wal-archive` behaviour when `-t` option is
used so that it exits after connectivity test.

- `barman recover` now continues when `--no-get-wal` is used and
`"get-wal"` is not set in `recovery_options`.

- Fix `barman show-servers --format=json ${server}` output for
inactive server.

- Check for presence of `barman_home` in configuration file.

- Passive barman servers will no longer store two copies of the
tablespace data when syncing backups taken with
`backup_method = postgres`.

Acknowledgements

We thank richyen for his contributions to this release.

Features
- Add snappy compression algorithm support in barman cloud (requires the optional python-snappy dependency).
- Allow Azure client concurrency parameters to be set when uploading WALs with `barman-cloud-wal-archive`.
- Add `--tags` option in barman cloud so that backup files and archived WALs can be tagged in cloud storage (aws and azure).
- Update the barman cloud exit status codes so that there is a dedicated code (2) for connectivity errors.
- Add the commands `barman verify-backup` and `barman generate-manifest` to check if a backup is valid.
- Add support for Azure Managed Identity auth in barman cloud which can be enabled with the `--credential` option.

Bug fixes
- Change `barman-cloud-check-wal-archive` behavior when bucket does not exist.
- Ensure `list-files` output is always sorted regardless of the underlying filesystem.
- Man pages for `barman-cloud-backup-keep`, `barman-cloud-backup-delete` and `barman-cloud-check-wal-archive` added to Python packaging.

Acknowledgements

Thanks to the following for their contributions:
- richyen
- stratakis

Bug fixes
- Resolves a performance regression introduced in version 2.14 which
increased copy times for `barman backup` or `barman recover` commands
when using the `--jobs` flag.
- Ignore rsync partial transfer errors for `sender` processes so that
such errors do not cause the backup to fail (thanks to barthisrael).

Features
- Add the commands `barman-check-wal-archive` and `barman-cloud-check-wal-archive` to validate if a proposed archive location is safe to use for a new PostgreSQL server.
- Allow Barman to identify WAL that's already compressed using a custom compression scheme to avoid compressing it again.
- Add `last_backup_minimum_size` and `last_wal_maximum_age` options to `barman check`.

Bug fixes
- Use argparse for command line parsing instead of the unmaintained argh module.
- Make timezones consistent for `begin_time` and `end_time`.

Thanks for their contributions:
- chtitux
- George Hansper
- stratakis
- Thoro
- vrms

Features

- Add plural forms for the `list-backup`, `list-server` and
`show-server` commands which are now `list-backups`, `list-servers`
and `show-servers`. The singular forms are retained for backward
compatibility.

- Add the `last-failed` backup shortcut which references the newest
failed backup in the catalog so that you can do:
`barman delete <SERVER> last-failed`

Bug fixes

- Tablespaces will no longer be omitted from backups of EPAS
versions 9.6 and 10 due to an issue detecting the correct version
string on older versions of EPAS.

Features

- Add the `barman-cloud-backup-delete` command which allows backups in
cloud storage to be deleted by specifiying either a backup ID or a
retention policy.

- Allow backups to be retained beyond any retention policies in force by
introducing the ability to tag existing backups as archival backups
using `barman keep` and `barman-cloud-backup-keep`.

- Allow the use of SAS authentication tokens created at the restricted
blob container level (instead of the wider storage account level) for
Azure blob storage

- Significantly speed up `barman restore` into an empty directory for
backups that contain hundreds of thousands of files

Bug fixes

- The backup privileges check will no longer fail if the user lacks
"userepl" permissions and will return better error messages if any
required permissions are missing (318 and 319)