senn-techProxmox Backup Server 4.2: S3 Object Storage and Parallel Sync Jobs
Proxmox Backup Server 4.2 (April 30, 2026) is on paper a maintenance and feature update — but it brings two innovations that change backup practice significantly: S3-compatible object storage as a backend and parallel sync jobs.
S3 as Backend
Previously, PBS datastores lived on local block or file storage. With 4.2, S3-compatible object storage can now be officially integrated as a target — including a built-in bandwidth counter to detect unexpected cost spikes in the cloud early. This makes offsite copies more flexible: those who don’t want to deploy a second storage box can offload them to an S3 bucket without sacrificing PBS-native deduplication and encryption.
Parallel Sync Jobs
Replication between PBS instances now uses multiple worker threads and processes multiple backup groups simultaneously. On large datastores with many VMs, this noticeably shortens sync windows. Additionally, server-side encryption secures replication traffic over untrusted networks.
Further Polished
- Namespaces can now be reorganized safely without breaking catalog consistency.
- Built on Debian 13.4 „Trixie" with Kernel 7.0 as standard and ZFS 2.4.
- Updated packages, broader hardware support, and security fixes.
How This Fits Into the Strategy
PBS is the cornerstone of our 3-2-1 backup strategy: local, deduplicated backup on the cluster, plus an immutable offsite copy. The new S3 backend makes exactly this offsite copy more accessible without disturbing the proven workflow of verify, prune, and garbage collection. Likewise, the TrueNAS file server attaches to the same chain.
Conclusion
4.2 is a quiet but weighty update: S3 backend and parallel syncs solve two concrete bottlenecks — offsite flexibility and sync duration. Anyone running PBS productively should plan this update; migration is non-critical, and the benefit is immediate.
Further Reading
What does the new S3-compatible backend in PBS 4.2 give us concretely?+
Previously PBS datastores lived only on local block or file storage. With 4.2, S3-compatible object storage can be officially integrated as a target, making the offsite copy more flexible: those who don’t want to deploy a second storage box offload it to an S3 bucket. A built-in bandwidth counter warns early of unexpected cost spikes, and PBS-native deduplication and encryption are preserved.
Is the 4.2 upgrade worthwhile for existing PBS installations?+
Yes. Anyone running PBS productively should plan the update, since migration is non-critical and the benefit is immediate. Parallel sync jobs use multiple worker threads and process several backup groups simultaneously, which noticeably shortens sync windows on large datastores. On top comes server-side encryption of replication, securing traffic even over untrusted networks.
How does PBS 4.2 fit into a 3-2-1 backup strategy?+
PBS is the cornerstone of our 3-2-1 strategy: local, deduplicated backup on the cluster plus an immutable offsite copy. The new S3 backend makes exactly that offsite copy more accessible without disturbing the proven workflow of verify, prune, and garbage collection. The strategy stays intact, and the offsite copy can optionally be realized on S3 instead of a storage box.