Barman

Features

- BREAKING CHANGE: PostgreSQL versions 9.6 and earlier are no longer
supported. If you are using one of these versions you will need to
use an earlier version of Barman.

- BREAKING CHANGE: The default backup mode for Rsync backups is now
concurrent rather than exclusive. Exclusive backups have been
deprecated since PostgreSQL 9.6 and have been removed in PostgreSQL
15. If you are running Barman against PostgreSQL versions earlier
than 15 and want to use exclusive backups you will now need to set
`exclusive_backup` in `backup_options`.

- BREAKING CHANGE: The backup metadata stored in the `backup.info` file
for each backup has an extra field. This means that earlier versions
of Barman will not work in the presence of any backups taken with
3.0.0. Additionally, users of pg-backup-api will need to upgrade it
to version 0.2.0 so that pg-backup-api can work with the updated
metadata.

- Backups taken with `backup_method = postgres` can now be compressed
by pg_basebackup by setting the `backup_compression` config option.
Additional options are provided to control the compression level,
the backup format and whether the pg_basebackup client or the
PostgreSQL server applies the compression. NOTE: Recovery of these
backups requires Barman to stage the compressed files on the recovery
server in a location specified by the `recovery_staging_path` option.

- Add support for PostgreSQL 15. Exclusive backups are not supported
by PostgreSQL 15 therefore Barman configurations for PostgreSQL 15
servers are not allowed to specify `exclusive_backup` in
`backup_options`.

- Various documentation improvements.

- Use custom_compression_magic, if set, when identifying compressed
WAL files. This allows Barman to correctly identify uncompressed
WALs (such as `*.partial` files in the `streaming` directory) and
return them instead of attempting to decompress them.

Bug fixes

- Fix an ordering bug which caused Barman to log the message
"Backup failed issuing start backup command." while handling a
failure in the stop backup command.

- Fix a bug which prevented recovery using `--target-tli` when
timelines greater than 9 were present, due to hexadecimal values
from WAL segment names being parsed as base 10 integers.

- Fix an import error which occurs when using barman cloud with
certain python2 installations due to issues with the enum34
dependency.

- Fix a bug where Barman would not read more than three bytes from
a compressed WAL when attempting to identify the magic bytes. This
means that any custom compressed WALs using magic longer than three
bytes are now decompressed correctly.

- Fix a bug which caused the `--immediate-checkpoint` flag to be
ignored during backups with `backup_method = rsync`.

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.