Releases: EnterpriseDB/barman
Barman 3.10.1
Version 3.10.1 - 12 June 2024
Bug fixes
- Make
argcomplete
optional to avoid installation issues on some
platforms. - Load
barman.auto.conf
only when the file exists. - Emit a warning when the
cfg_changes.queue
file is malformed. - Correct in documentation the postgresql version where
pg_checkpoint
is available. - Add
--no-partial
option tobarman-cloud-wal-restore
.
release/3.10.0
Version 3.10.0 - 24 January 2024
Features
- Limit the average bandwidth used by
barman-cloud-backup
when backing
up to either AWS S3 or Azure Blob Storage according to the value set by
a new CLI option--max-bandwidth
. - Add the new configuration option
lock_directory_cleanup
That enables cron to automatically clean up the barman_lock_directory
from unused lock files. - Add support for a new type of configuration called
model
.
The model acts as a set of overrides for configuration options
for a given Barman server. - Add a new barman command
barman config-update
that allows the creation
and the update of configurations using JSON
Bug fixes:
- Fix a bug that caused
--min-chunk-size
to be ignored when using
barman-cloud-backup as hook script in Barman.
Barman 3.9.0
Version 3.9.0 - 3 October 2023
Features
-
Allow
barman switch-wal --force
to be run against PG>=14 if the
user has thepg_checkpoint
role (thanks to toydarian for this patch). -
Log the current check at
info
level when a check timeout occurs. -
The minimum size of an upload chunk when using
barman-cloud-backup
with either S3 or Azure Blob Storage can now be specified using the
--min-chunk-size
option. -
backup_compression = none
is supported when usingpg_basebackup
. -
For PostgreSQL 15 and later: the allowed
backup_compression_level
values forzstd
andlz4
have been updated to match those allowed by
pg_basebackup
. -
For PostgreSQL versions earlier than 15:
backup_compression_level = 0
can now be used withbackup_compression = gzip
.
Bug fixes:
- Fix
barman recover
on platforms where Multiprocessing uses spawn by
default when starting new processes.
Barman 3.8.0
Version 3.8.0 - 31 August 2023
Features
-
Clarify package installation. barman is packaged with default python version
for each operating system. -
The
minimum-redundancy
option is added tobarman-cloud-backup-delete
.
It allows to set the minimum number of backups that should always be available. -
Add a new
primary_checkpoint_timeout
configuration option. Allows define
the amount of seconds that Barman will wait at the end of a backup if no
new WAL files are produced, before forcing a checkpoint on the primary server.
Bug fixes:
-
Fix race condition in barman retention policies application. Backup
deletions will now raise a warning if another deletion is in progress
for the requested backup. -
Fix
barman-cloud-backup-show
man page installation.
Barman 3.7.0
Version 3.7.0 - 25 July 2023
Features
-
Support is added for snapshot backups on AWS using EBS volumes.
-
The
--profile
option in thebarman-cloud-*
scripts is renamed
--aws-profile
. The old name is deprecated and will be removed in
a future release. -
Backup manifests can now be generated automatically on completion
of a backup made withbackup_method = rsync
. This is enabled by
setting theautogenerate_manifest
configuration variable and can
be overridden using the--manifest
and--no-manifest
CLI options.
Bug fixes:
-
The
barman-cloud-*
scripts now correctly use continuation
tokens to page through objects in AWS S3-compatible object
stores. This fixes a bug wherebarman-cloud-backup-delete
would only delete the oldest 1000 eligible WALs after backup
deletion. -
Minor documentation fixes.
Barman 3.6.0
Version 3.6.0 - 15 June 2023
Features
-
PostgreSQL version 10 is no longer supported.
-
Support is added for snapshot backups on Microsoft Azure using
Managed Disks. -
The
--snapshot-recovery-zone
option is renamed--gcp-zone
for
consistency with other provider-specific options. The old name
is deprecated and will be removed in a future release. -
The
snapshot_zone
option and--snapshot-zone
argument are
renamedgcp_zone
and--gcp-zone
respectively. The old names
are deprecated and will be removed in a future release. -
The
snapshot_gcp_project
option and--snapshot-gcp-project
argument are renamed togcp_project
and--gcp-project
. The
old names are deprecated and will be removed in a future release.
Bug fixes:
-
Barman will no longer attempt to execute the
replication-status
command for a passive node. -
The
backup_label
is deleted from cloud storage when a
snapshot backup is deleted withbarman-cloud-backup-delete
. -
Man pages for the
generate-manifest
andverify-backup
commands are added. -
Minor documentation fixes.
Barman 3.4.1
Version 3.4.1 - 31 March 2023
Bug fixes:
-
Fix a bug which prevented
barman-cloud-backup-show
from
displaying the backup metadata for backups made with
barman backup
and uploaded bybarman-cloud-backup
as a
post-backup hook script. -
Fix a bug where the PostgreSQL connection used to validate backup
compression settings was left open until termination of the
Barman command. -
Fix an issue which caused rsync-concurrent backups to fail when
running for a duration greater thanidle_session_timeout
. -
Fix a bug where the backup name was not saved in the backup
metadata if the--wait
flag was used withbarman backup
.
Acknowledgements
We thank the following who contributed to this release:
- barthisrael
- epolkerman
- hzetters
Barman 3.5.0
Version 3.5.0 - 29 March 2023
Features
-
Python 2.7 is no longer supported. The earliest Python version
supported is now 3.6. -
The
barman
,barman-cli
andbarman-cli-cloud
packages for
EL7 now require python 3.6 instead of python 2.7. For other
supported platforms, Barman packages already require python
versions 3.6 or later so packaging is unaffected. -
Support for PostgreSQL 10 will be discontinued in future Barman
releases; 3.5.x is the last version of Barman with support for
PostgreSQL 10. -
Backups and WALs uploaded to Google Cloud Storage can now be
encrypted using a specific KMS key by using the--kms-key-name
option withbarman-cloud-backup
orbarman-cloud-wal-archive
. -
Backups and WALs uploaded to AWS S3 can now be encrypted using a
specific KMS key by using the--sse-kms-key-id
option with
barman-cloud-backup
orbarman-cloud-wal-archive
along with
--encryption=aws:kms
. -
Two new configuration options are provided which make it possible
to limit the rate at which parallel workers are started during
backups withbackup_method = rsync
and recoveries.
parallel_jobs_start_batch_size
can be set to limit the amount of
parallel workers which will be started in a single batch, and
parallel_jobs_start_batch_period
can be set to define the time
in seconds over which a single batch of workers will be started.
These can be overridden using the arguments--jobs-start-batch-size
and--jobs-start-batch-period
with thebarman backup
and
barman recover
commands. -
A new option
--recovery-conf-filename
is added tobarman recover
.
This can be used to change the file to which Barman should write the
PostgreSQL recovery options from the defaultpostgresql.auto.conf
to an alternative location.
Bug fixes
-
Fix a bug which prevented
barman-cloud-backup-show
from
displaying the backup metadata for backups made with
barman backup
and uploaded bybarman-cloud-backup
as a
post-backup hook script. -
Fix a bug where the PostgreSQL connection used to validate backup
compression settings was left open until termination of the
Barman command. -
Fix an issue which caused rsync-concurrent backups to fail when
running for a duration greater thanidle_session_timeout
. -
Fix a bug where the backup name was not saved in the backup
metadata if the--wait
flag was used withbarman backup
.
Acknowledgements
We thank the following who contributed to this release:
- barthisrael
- epolkerman
- hzetters
- mhkarimi1383
- mojtabash78
Barman 3.4.0
Version 3.4.0 - 26 January 2023
Features
-
This is the last release of Barman which will support Python 2 and
new features will henceforth require Python 3.6 or later. -
A new
backup_method
namedsnapshot
is added. This will create
backups by taking snapshots of cloud storage volumes. Currently
only Google Cloud Platform is supported however support for AWS
and Azure will follow in future Barman releases. Note that this
feature requires a minimum Python version of 3.7. Please see the
Barman manual for more information. -
Support for snapshot backups is also added to
barman-cloud-backup
,
with minimal support for restoring a snapshot backup added to
barman-cloud-restore
. -
A new command
barman-cloud-backup-show
is added which displays
backup metadata stored in cloud object storage and is analogous to
barman show-backup
. This is provided so that snapshot metadata
can be easily retrieved at restore time however it is also a
convenient way of inspecting metadata for any backup made with
barman-cloud-backup
.
Bug fixes
-
The instructions for installing Barman from RPMs in the docs are
updated. -
The formatting of NFS requirements in the docs is fixed.
-
Supported PostgreSQL versions are updated in the docs (this is a
documentation fix only - the minimum supported major version is
still 10).
Barman 3.3.0
Version 3.3.0 - 14 December 2022
Features
-
A backup can now be given a name at backup time using the new
--name
option supported by thebarman backup
andbarman-cloud-backup
commands. The backup name can then be used in place of the backup ID
when running commands to interact with backups. Additionally, the
commands to list and show backups have been been updated to include
the backup name in the plain text and JSON output formats. -
Stricter checking of PostgreSQL version to verify that Barman is
running against a supported version of PostgreSQL.
Bug fixes
-
Fix inconsistencies between the barman cloud command docs and the help
output for those commands. -
Use a new PostgreSQL connection when switching WALs on the primary
during the backup of a standby to avoid undefined behaviour such as
SSL error
messages and failed connections. -
Reduce log volume by changing the default log level of stdout for
commands executed in child processes toDEBUG
(with the exception
ofpg_basebackup
which is deliberately logged atINFO
level due
to it being a long-running process where it is frequently useful to
see the output during the execution of the command).