Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vmoOu-00GWVR-2G for pgsql-announce@arkaria.postgresql.org; Mon, 02 Feb 2026 07:31:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vmoOs-00CWag-1S for pgsql-announce@arkaria.postgresql.org; Mon, 02 Feb 2026 07:31:11 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vmoOr-00CWa6-1w for pgsql-announce@lists.postgresql.org; Mon, 02 Feb 2026 07:31:10 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1vmoOo-00000000dZy-3cB6 for pgsql-announce@lists.postgresql.org; Mon, 02 Feb 2026 07:31:10 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:From:To:Subject: MIME-Version:Content-Type:Sender:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:In-Reply-To:References; bh=JX2TJwRYW8shM0dfIi8Uk4y9bfnzngUsgGI3Gc/M0J4=; b=ijkgXeNYxc0DZnu6avULptJOQT 6cgLPULAquuGgbkPIhsU8juHIW6BeWB3mO059+dwtyF7eAdZ/rRdlusrHVqWjibd9mFDzyOH+sWkW jIISj3MM0nVUaS3mVmhUnN8qW9RPrmVtDEOziD3YunTYiNndw8uU06RG56UGQ3pWP9fWXjHKUATjL t5RV5RyhnwGH5duwaZVpH2XWDkZYYXkAHvMHBuvuY+f/wKs1oTtEDtjCJvECSPaMpjMWfMDb3EFai cIpYjGghDoJeNqxHcA0CECt/6sw+eqB1+5QLwWvnRJ/qeC1US/4UpjfcrdkWbTmY0j5h7QzE0uh8v BhaBJysQ==; Received: from wrigleys.postgresql.org ([217.196.149.60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vmoOn-001o6W-0f for pgsql-announce@lists.postgresql.org; Mon, 02 Feb 2026 07:31:05 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vmoOk-003ArJ-2q for pgsql-announce@lists.postgresql.org; Mon, 02 Feb 2026 07:31:03 +0000 Content-Type: multipart/alternative; boundary="===============7662754628317864201==" MIME-Version: 1.0 Subject: Barman 3.17 Released To: PostgreSQL Announce From: EDB via PostgreSQL Announce Reply-To: david.wagoner@enterprisedb.com Date: Mon, 02 Feb 2026 07:30:17 +0000 Message-ID: <177001741771.807.15370128464071383132@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: related X-pglister-tagsig: 59be77019f9f351fb136bf163f55d0294f9c29daae5aa772042e87bd3ed91c6b List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============7662754628317864201== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable We are pleased to announce the release of Barman 3.17.0. **Barman** (Backup and Recovery Manager) is an open-source administration t= ool for remote backups and disaster recovery of PostgreSQL servers in busin= ess-critical environments. It relies on PostgreSQL=E2=80=99s point-in-time = recovery technology, allowing DBAs to manage a complete catalog of backups = and the recovery phase of multiple remote servers from one location. This release focuses on operational flexibility for disabled servers, compl= iance improvements for S3 storage, and important deprecation notices regard= ing compression. ### Release Highlights =20 **Operations on Inactive Servers** =20 Barman 3.17 introduces the ability to perform read and recovery operations = on servers that have been manually disabled or marked inactive. This allows= administrators to query the catalog, list files, and perform restores (inc= luding get-wal) even if the specific server configuration is disabled to pr= event new backup execution. This provides a safer environment for restoring= data from servers that may have configuration conflicts. **S3 Object Lock Support** =20 To support governance and compliance retention policies, the barman-cloud-b= ackup-delete command now includes a --check-object-lock option. This preven= ts the accidental deletion of objects in AWS S3 that are protected by Objec= t Lock, aborting the operation if locked objects are detected. **Custom SSH Ports for Remote Restore** =20 The barman restore command now accepts a --recovery-option-port flag. This = allows users to specify a custom SSH port for the barman-wal-restore comman= d, facilitating remote restores in environments with non-standard port conf= igurations. ### Important Notices =20 **Deprecation of Custom Compression**: The custom compression option (and r= elated filters) is now deprecated. We strongly advise users to migrate to o= ne of Barman's built-in supported algorithms (gzip, bzip2, lz4, xz, zstd, o= r pigz) to ensure future compatibility, performance, and reliability. ### Bug Fixes and Improvements =20 **Expanded S3 Compatibility:** We have improved error handling for non-comp= liant S3 object stores (such as certain MinIO configurations) during backup= deletion. Barman now correctly identifies error messages containing "conte= nt-MD5" to prevent unnecessary failures. =20 **Delta Restore Logic:** Fixed an issue where the destination directory was= being removed prior to a restore, ensuring delta restores now function cor= rectly. =20 **Mount Point Safety:** Resolved an issue where restore operations could fa= il with "rm execution failed" errors. Barman now avoids attempting to remov= e destination directories for PGDATA and tablespaces if they are mount poin= ts. =20 **macOS Compatibility:** Fixed a UnicodeDecodeError that occurred when chec= king for file encryption on macOS systems, ensuring graceful handling of un= decodable bytes. =20 ### Links =20 **Website:** https://pgbarman.org/ =20 **Download:** https://www.enterprisedb.com/software-downloads-postgres#barm= an =20 **Documentation:** https://docs.pgbarman.org/ =20 **Release Notes:** https://docs.pgbarman.org/release/3.17.0/releases/index.= html =20 **Support:** https://pgbarman.org/support/ =20 ### About Barman =20 Barman is distributed under the GNU GPL 3 license and maintained by Enterpr= iseDB (EDB). --===============7662754628317864201== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Barman 3.17 Released
 

Barman 3.17 Released

We are pleased to announce the release of B= arman 3.17.0.

Barman (Backup and Recover= y Manager) is an open-source administration tool for remote backups and dis= aster recovery of PostgreSQL servers in business-critical environments. It = relies on PostgreSQL=E2=80=99s point-in-time recovery technology, allowing = DBAs to manage a complete catalog of backups and the recovery phase of mult= iple remote servers from one location.

This release focuses on operational flexibi= lity for disabled servers, compliance improvements for S3 storage, and impo= rtant deprecation notices regarding compression.

Release Highlights

Operations on Inactive Servers
Barman 3.17 introduces the ability to perform read and recovery operations = on servers that have been manually disabled or marked inactive. This allows= administrators to query the catalog, list files, and perform restores (inc= luding get-wal) even if the specific server configuration is disabled to pr= event new backup execution. This provides a safer environment for restoring= data from servers that may have configuration conflicts.

S3 Object Lock Support
To support governance and compliance retention policies, the barman-cloud-b= ackup-delete command now includes a --check-object-lock option. This preven= ts the accidental deletion of objects in AWS S3 that are protected by Objec= t Lock, aborting the operation if locked objects are detected.

Custom SSH Ports for Remote Restore=
The barman restore command now accepts a --recovery-option-port flag. This = allows users to specify a custom SSH port for the barman-wal-restore comman= d, facilitating remote restores in environments with non-standard port conf= igurations.

Important Notices

Deprecation of Custom Compression: The custom compression option (and related filters) is now depreca= ted. We strongly advise users to migrate to one of Barman's built-in suppor= ted algorithms (gzip, bzip2, lz4, xz, zstd, or pigz) to ensure future compa= tibility, performance, and reliability.

Bug Fixes and Improvements

Expanded S3 Compatibility:= We have improved error handling for non-compliant S3 object stores (such a= s certain MinIO configurations) during backup deletion. Barman now correctl= y identifies error messages containing "content-MD5" to prevent unnecessary= failures.
Delta Restore Logic: Fixed an issue where the destination = directory was being removed prior to a restore, ensuring delta restores now= function correctly.
Mount Point Safety: Resolved an issue where restore operat= ions could fail with "rm execution failed" errors. Barman now avoids attemp= ting to remove destination directories for PGDATA and tablespaces if they a= re mount points.
macOS Compatibility: Fixed a UnicodeDecodeError that occur= red when checking for file encryption on macOS systems, ensuring graceful h= andling of undecodable bytes.

Links

Website: https://pgbarman.= org/
Download: https://www.enterprisedb.com/software-downloads-= postgres#barman
Documentation: https://docs.pgbarman.org/
Release Notes: https://docs.pgbarman.org/release/3.17.0/re= leases/index.html
Support: https://pgbarman.org/support/

About Barman

Barman is distributed under the GNU GPL 3 l= icense and maintained by EnterpriseDB (EDB).
This email was sent to you from EDB. It was delivered on their behalf by the PostgreSQL project. Any questions about the content of the message shou= ld be sent to EDB.

You were sent this email as a subscriber of the pgsql-announce mai= linglist, for the content tag Related Open Source. To unsubscribe from further emails, or change which emails you want to receive, please click th= e personal unsubscribe link that you can find in the headers of this email, or visit https://lists.postgresql.org/unsubscribe/.
 
--===============7662754628317864201==--