Proxmox Backup Server 4.2 released!

t.lamprecht

t.lamprecht

Proxmox Staff Member
Staff member
Jul 28, 2015
6,822
5,117
315
South Tyrol/Italy
shop.proxmox.com
We're pleased to announce the release of Proxmox Backup Server 4.2.

This version is based on Debian 13.4 ("Trixie"), uses Linux kernel 7.0 as the new stable default for improved hardware support, and comes with ZFS 2.4 for reliable, enterprise-grade storage.

Here are the highlights
  • Move groups and namespaces within a datastore for easier backup reorganization
  • Server-side encryption/decryption for sync jobs
  • Improved sync performance with concurrent group processing ("worker-threads")
  • S3-compatible object stores supported as backup storage backend, with request statistics and notifications
  • Numerous performance, usability, and backend improvements across the stack
  • and much more...
You can find all details in the full release notes, and as always, we're really looking forward to your feedback and experiences with Proxmox Backup Server 4.2!

Release notes
https://pbs.proxmox.com/wiki/Roadmap#Proxmox_Backup_Server_4.2

Press release
https://www.proxmox.com/en/about/company-details/press-releases/proxmox-backup-server-4-2

Download
https://www.proxmox.com/en/downloads
Alternate ISO download:
https://enterprise.proxmox.com/iso

Documentation
https://pbs.proxmox.com/docs

Community Forum
https://forum.proxmox.com

Bugtracker
https://bugzilla.proxmox.com

Source code
https://git.proxmox.com

Thanks for your contributions, ideas, and support — with your insights, we've introduced meaningful updates to enhance your experience.

FAQ
Q: Can I upgrade the latest Proxmox Backup Server 3.x to 4.2 with apt?
A: Yes, please follow the upgrade instructions on https://pbs.proxmox.com/wiki/Upgrade_from_3_to_4

Q: How does this integrate into Proxmox Virtual Environment?
A: Just add a Proxmox Backup Server datastore as a new storage target in your Proxmox VE. Make sure that you run the latest Proxmox VE 9.x

Q: Is Proxmox Backup Server still compatible with older clients or Proxmox VE releases?
A: We are actively testing the compatibility of all the major versions currently supported, including the previous one. This means that you can safely back up from Proxmox VE 8 to Proxmox Backup Server 4, or from Proxmox VE 9 to Proxmox Backup Server 3. However, full compatibility with major client versions that are two or more releases apart, like for example Proxmox VE 7 based on Debian 11 Bullseye and Proxmox Backup Server 4 based on Debian 13 Trixie, is supported on a best-effort basis only.

Q: How long will Proxmox Backup Server 3.4 receive bug fixes and security support?
A: Proxmox Backup Server 3.4 will receive security updates and critical bug fixes until August 2026. This support window provides an overlap of approximately one year after the release of Proxmox Backup Server 4, giving users ample time to plan their upgrade to the new major version.
For more information on the support lifecycle of Proxmox Backup Server releases, please visit:
https://pbs.proxmox.com/docs/faq.html#how-long-will-my-proxmox-backup-server-version-be-supported

Q: How do I install the proxmox-backup-client on my Debian or Ubuntu server?
A: We provide a "Proxmox Backup Client-only Repository". See https://pbs.proxmox.com/docs/installation.html#client-installation
For Debian derivatives we recommend installing the proxmox-backup-client-static package to avoid issues with different system library versions.

Q: What will happen with the existing backup tool (vzdump) in Proxmox Virtual Environment?
A: You can still use vzdump. The new backup is an additional, but very powerful way to back up and restore your VMs and containers.

Q: Is there any recommended server hardware for the Proxmox Backup Server?
A: We recommend enterprise-grade server hardware components, with fast local SSD/NVMe storage. Access and response times from rotating drives will slow down all backup server operations. See https://pbs.proxmox.com/docs/installation.html#recommended-server-system-requirements

Q: Can I install Proxmox Backup Server on Debian, in a VM, as LXC or alongside with Proxmox VE?
A: Yes, but all this is not the recommended setup (expert use only).

Q: Where can I get more information about upcoming features?
A: Follow the announcement forum and pbs-devel mailing list https://lists.proxmox.com/postorius/lists/pbs-devel.lists.proxmox.com/ and subscribe to our newsletter https://www.proxmox.com/news and see https://pbs.proxmox.com/wiki/Roadmap.
 
  • Like
Reactions: news, green72, MickyF and 18 others
Is it possible to have th proxmox-backup-client-static in the latest version? Great job
 
Dark26 said:
Is it possible to have th proxmox-backup-client-static in the latest version?
Click to expand...

Do you mean the dedicated pbs-client repo? It was indeed lagging behind, but the CDN sync there should be finished now.
 
  • Like
Reactions: Johannes S
t.lamprecht said:
Do you mean the dedicated pbs-client repo? It was indeed lagging behind, but the CDN sync there should be finished now.
Click to expand...
exactly.

Code: 
proxmox-backup-client-static_4.2.0-1_amd64.deb     28-Apr-2026 22:16             9296220

evrything is fine. thanks for the update.
 
Great work moving s3 across the finish line. Now the next (really important) step there is immutability. So far I'm holding out for that to get done rather than start using Veeam for our Proxmox systems but that's literally the level of tradeoff we're having to consider.

Another piece (for both PBS and PDM) is fixing authentication and authorization to the point where it's at the same level as PVE. Right now forcing the users to login, then wait for an admin to assign them to a group, then log back in is a management chore and a half - tolerable for PBS but causing PBM to be a nonstarter. My (possibly wrong) understanding is that PBS and PDM share much of their auth code so fixing one fixes both.
 
mikeely said:
Great work moving s3 across the finish line. Now the next (really important) step there is immutability. So far I'm holding out for that to get done rather than start using Veeam for our Proxmox systems but that's literally the level of tradeoff we're having to consider.
Click to expand...

Are you aware that you can already implement kind of immutability with an offsite PBS and pull-syncs? For this to work you don't even need to open any ports on the offsite PBS firewall as long as it can reach the port 8007 on your local PBS: https://pbs.proxmox.com/docs/storage.html#ransomware-protection-recovery
Basically you use a combination of said firewall rules and read-only access API tokens.
And if somehow an bad actor manages to get root/admin access to your veeam server he can also modify your "immutable" repository, in that regard there is no difference between Veeam or PBS.
 
  • Like
Reactions: UdoB
Johannes S said:
And if somehow an bad actor manages to get root/admin access to your veeam server he can also modify your "immutable" repository, in that regard there is no difference between Veeam or PBS.
Click to expand...
I was specifically talking about S3 immutability specifically, which you did not address.
To your point, if an attacker is in backend systems long enough to modify the retention policy in Veeam, wait for the retention to expire, and then delete stuff... yeah. At that point no amount of resilient design is going to overcome such an epic failure in monitoring, configuration management, etc. The same attacker would just as easily pwn the offsite PBS, so either way the data is gone.
 
You must log in or register to reply here.
Top Bottom
Back