Proxmox Backup Server 4.0 released!

t.lamprecht

t.lamprecht

Proxmox Staff Member
Staff member
Jul 28, 2015
6,649
4,324
315
South Tyrol/Italy
shop.proxmox.com
We are pleased to announce the first stable release of Proxmox Backup Server 4.0 - immediately available for download!

The new version is based on the great Debian 13 "Trixie" but we're using a newer Linux kernel 6.14.8-2 as stable default in Proxmox Backup Server, including ZFS 2.3.3.

We're incredibly proud of the hard work that has gone into this release and can't wait for you to experience it.

Some of the exciting new features we've packed into Proxmox Backup Server 4.0:
  • S3-compatible object stores as backup storage backend (technology preview).
  • ZFS 2.3 with RAID-Z expansion.
  • Automatically trigger sync jobs when a removable datastore is mounted.
  • and more...

Beyond these major additions, we've also implemented numerous performance enhancements and bug fixes to make your experience even smoother. For a full list of changes, check out our release notes.

Release notes
https://pbs.proxmox.com/wiki/Roadmap

Press release
https://www.proxmox.com/en/news/press-releases

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

There has been a lot of feedback from our community members and customers, and many of you reported issues, submitted patches, and were involved in testing - THANK YOU for your support!

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

Q: Can I upgrade an 4.0 beta installation to the stable 4.0 via apt?
A: Yes, upgrading from beta to stable installation is possible via apt. We recommend switching to the pbs-enterprise repository on upgrade for the most stable experience.

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: Why is Proxmox Backup Server 4.0 released ahead of the stable Debian 13 release?
A: Debian 13 is scheduled for its stable release this Saturday, August 9. Its core components have been stabilized since it entered the "hard freeze" phase on May 15. Following extensive integration testing and valuable feedback during the Proxmox Backup Server 4.0 beta, we are confident in the stability of this release. Since our core packages are either maintained directly by the Proxmox team or are already locked by Debian's strict freeze policy, there is no technical reason to postpone our release.

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 8.4 or Proxmox VE 9.0.

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 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: 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 feature updates?
A: Check the roadmap, forum, the mailing list, and/or subscribe to our newsletter.
 
  • Like
Reactions: _gabriel, RobFantini, Neobin and 21 others
One nitpick: the upgrade guide points people to the pbs-test repository. Maybe show the enterprise and no-subscription repository sources instead (as you did for PVE 9.0), now that it is released? Great work nonetheless!

EDIT: Minor observation: pbs3to4 does not take into account that proxmox-backup might not be installed (and PBS runs in a PVE container) and does not look for proxmox-backup-server. But the upgrade went smoothly anyway, thanks!
 
Last edited:
  • Like
Reactions: endurance, broth-itk, Johannes S and 2 others
Would really be useful if you could get the team working on the backup agents for Windows OS's at the very least. I can't use PBS because of this. It's been on your roadmap for a long time.

Thanks!

1000015630.png
 
leesteken said:
One nitpick: the upgrade guide points people to the pbs-test repository. Maybe show the enterprise and no-subscription repository sources instead (as you did for PVE 9.0), now that it is released? Great work nonetheless!
Click to expand...
Thanks again for the keen eye! - Should be fixed now!
 
  • Like
Reactions: leesteken and Chris
leesteken said:
EDIT: Minor observation: pbs3to4 does not take into account that proxmox-backup might not be installed (and PBS runs in a PVE container) and does not look for proxmox-backup-server. But the upgrade went smoothly anyway, thanks!
Click to expand...

Might it make sense to add a hint to the upgrade document? I would not ask to patch the pbs3to4 script in order to check if its installed in a container.
Can't tell how many users are having PBS in a container. In my environment there are dozens ;-)
 
  • Like
Reactions: sbellon
broth-itk said:
Might it make sense to add a hint to the upgrade document? I would not ask to patch the pbs3to4 script in order to check if its installed in a container.
Can't tell how many users are having PBS in a container. In my environment there are dozens ;-)
Click to expand...
While we do not recommend it as best possible option, we actually do support that use case, so would make sense to make pbs2to3 detect this situation and handle it more gracefully.
 
  • Like
Reactions: broth-itk
I have just installed PBS4

Installed tailscale and now im keep on geting network issues.

Anyone else having this issue?

could not deserialize ip link output (400) and the webpage stops working


Aug 06 16:49:35 pbs systemd[1]: Finished networking.service - Network initialization.
Aug 06 16:49:35 pbs systemd[1]: Reached target network.target - Network.
Aug 06 16:49:35 pbs systemd[1]: Reached target network-online.target - Network is Online.
Aug 06 16:49:35 pbs systemd[1]: Starting postfix.service - Postfix Mail Transport Agent (main/default instance)...
Aug 06 16:49:35 pbs systemd[1]: Starting proxmox-backup.service - Proxmox Backup API Server...
Aug 06 16:49:35 pbs systemd[1]: Starting rpc-statd-notify.service - Notify NFS peers of a restart...
Aug 06 16:49:35 pbs systemd[1]: Starting ssh.service - OpenBSD Secure Shell server...
Aug 06 16:49:35 pbs systemd[1]: Starting systemd-user-sessions.service - Permit User Sessions...
Aug 06 16:49:35 pbs systemd[1]: Started rpc-statd-notify.service - Notify NFS peers of a restart.
Aug 06 16:49:35 pbs sm-notify[635]: Version 2.8.3 starting
Aug 06 16:49:35 pbs systemd[1]: Finished systemd-user-sessions.service - Permit User Sessions.
Aug 06 16:49:35 pbs systemd[1]: Started getty@tty1.service - Getty on tty1.
Aug 06 16:49:35 pbs systemd[1]: Reached target getty.target - Login Prompts.
Aug 06 16:49:35 pbs sshd[643]: Server listening on 0.0.0.0 port 22.
Aug 06 16:49:35 pbs sshd[643]: Server listening on :: port 22.
Aug 06 16:49:35 pbs systemd[1]: Started ssh.service - OpenBSD Secure Shell server.
Aug 06 16:49:35 pbs proxmox-backup-api[634]: catching shutdown signal
Aug 06 16:49:35 pbs proxmox-backup-api[634]: catching reload signal
Aug 06 16:49:35 pbs systemd[1]: Started proxmox-backup.service - Proxmox Backup API Server.
Aug 06 16:49:35 pbs systemd[1]: Starting proxmox-backup-proxy.service - Proxmox Backup API Proxy Server...
Aug 06 16:49:35 pbs proxmox-backup-proxy[657]: applied rrd journal (137 entries in 0.009 seconds)
Aug 06 16:49:35 pbs proxmox-backup-proxy[657]: catching shutdown signal
Aug 06 16:49:35 pbs proxmox-backup-proxy[657]: catching reload signal
Aug 06 16:49:35 pbs systemd[1]: Started proxmox-backup-proxy.service - Proxmox Backup API Proxy Server.
Aug 06 16:49:35 pbs systemd[1]: Started removable-device-attach@08156347-a143-4b79-8c74-e7a243a15c95.service - Try to mount the removable device of a datastore with uuid '08156347-a143-4b79-8c74-e7a243a15c95'..
Aug 06 16:49:35 pbs systemd[1]: Started removable-device-attach@2968-268B.service - Try to mount the removable device of a datastore with uuid '2968-268B'..
Aug 06 16:49:35 pbs proxmox-backup-proxy[657]: get_network_interfaces failed - could not deserialize ip link output
Aug 06 16:49:35 pbs systemd[1]: Started removable-device-attach@55cba4a8-502b-45aa-b45f-582fb2edee01.service - Try to mount the removable device of a datastore with uuid '55cba4a8-502b-45aa-b45f-582fb2edee01'..
Aug 06 16:49:35 pbs proxmox-backup-proxy[657]: rrd journal successfully committed (15 files in 0.011 seconds)
Aug 06 16:49:35 pbs systemd[1]: Started removable-device-attach@fKsN5U-OBfK-QJ3W-l9Dw-Ywr3-513l-6en3N9.service - Try to mount the removable device of a datastore with uuid 'fKsN5U-OBfK-QJ3W-l9Dw-Ywr3-513l-6en3N9'..
Aug 06 16:49:35 pbs tailscaled[482]: control: lite map update error after 249ms: initial fetch failed 409: superseded by another update
Aug 06 16:49:35 pbs tailscaled[482]: REQ-2025080615493592d2e9dd4214012d
Aug 06 16:49:35 pbs systemd[1]: removable-device-attach@08156347-a143-4b79-8c74-e7a243a15c95.service: Deactivated successfully.
Aug 06 16:49:35 pbs systemd[1]: removable-device-attach@2968-268B.service: Deactivated successfully.
Aug 06 16:49:35 pbs systemd[1]: removable-device-attach@55cba4a8-502b-45aa-b45f-582fb2edee01.service: Deactivated successfully.
Aug 06 16:49:35 pbs systemd[1]: removable-device-attach@fKsN5U-OBfK-QJ3W-l9Dw-Ywr3-513l-6en3N9.service: Deactivated successfully.
Aug 06 16:49:35 pbs postfix[775]: postfix/postlog: warning: /var/spool/postfix/etc/localtime and /etc/localtime differ
Aug 06 16:49:35 pbs postfix/postfix-script[775]: warning: /var/spool/postfix/etc/localtime and /etc/localtime differ
Aug 06 16:49:35 pbs postfix[781]: postfix/postlog: warning: /var/spool/postfix/etc/resolv.conf and /etc/resolv.conf differ
Aug 06 16:49:35 pbs postfix/postfix-script[781]: warning: /var/spool/postfix/etc/resolv.conf and /etc/resolv.conf differ
Aug 06 16:49:35 pbs postfix/master[799]: daemon started -- version 3.10.3, configuration /etc/postfix
Aug 06 16:49:35 pbs systemd[1]: Started postfix.service - Postfix Mail Transport Agent (main/default instance).
Aug 06 16:49:35 pbs systemd[1]: Reached target multi-user.target - Multi-User System.
Aug 06 16:49:35 pbs systemd[1]: Reached target graphical.target - Graphical Interface.
Aug 06 16:49:35 pbs systemd[1]: Startup finished in 2.179s (kernel) + 3.628s (userspace) = 5.808s.
Aug 06 16:49:36 pbs tailscaled[482]: health(warnable=not-in-map-poll): ok
Aug 06 16:49:36 pbs tailscaled[482]: control: netmap: got new dial plan from control
Aug 06 16:49:36 pbs tailscaled[482]: active login: wii747@github
Aug 06 16:49:36 pbs tailscaled[482]: Switching ipn state NoState -> Starting (WantRunning=true, nm=true)
Aug 06 16:49:36 pbs tailscaled[482]: magicsock: SetPrivateKey called (init)
Aug 06 16:49:36 pbs tailscaled[482]: wgengine: Reconfig: configuring userspace WireGuard config (with 0/13 peers)
Aug 06 16:49:36 pbs tailscaled[482]: wgengine: Reconfig: configuring router
Aug 06 16:49:36 pbs tailscaled[482]: portmapper: UPnP meta changed: [{Location:http://192.168.70.1:2189/rootDesc.xml Server:FreeBSD/15.0-CURRENT UPnP/1.1 MiniUPnPd/2.3.7 USN:uuid:5b3b3378-790a-ba1f-a373-d176e02a568::urn:schemas-upnp-org:device:InternetGatewayDevice:1}]
Aug 06 16:49:36 pbs tailscaled[482]: magicsock: home DERP changing from derp-0 [0ms] to derp-8 [3ms]
Aug 06 16:49:36 pbs tailscaled[482]: magicsock: home is now derp-8 (lhr)
Aug 06 16:49:36 pbs tailscaled[482]: magicsock: adding connection to derp-8 for home-keep-alive
Aug 06 16:49:36 pbs tailscaled[482]: magicsock: 1 active derp conns: derp-8=cr0s,wr0s
Aug 06 16:49:36 pbs tailscaled[482]: magicsock: endpoints changed: 94.23.154.130:41645 (portmap), 192.168.70.12:41641 (local)
Aug 06 16:49:36 pbs tailscaled[482]: control: NetInfo: NetInfo{varies=false hairpin= ipv6=false ipv6os=true udp=true icmpv4=false derp=#8 portmap=active-UMC link="" firewallmode="ipt-default"}
Aug 06 16:49:36 pbs tailscaled[482]: derphttp.Client.Connect: connecting to derp-8 (lhr)
Aug 06 16:49:36 pbs tailscaled[482]: health(warnable=no-derp-connection): ok
Aug 06 16:49:36 pbs tailscaled[482]: health(warnable=no-derp-connection): ok
Aug 06 16:49:36 pbs tailscaled[482]: magicsock: derp-8 connected; connGen=1
Aug 06 16:49:36 pbs tailscaled[482]: health(warnable=no-derp-connection): ok
Aug 06 16:49:36 pbs tailscaled[482]: [RATELIMIT] format("health(warnable=%s): ok")
Aug 06 16:49:36 pbs tailscaled[482]: wgengine: Reconfig: user dialer
Aug 06 16:49:36 pbs tailscaled[482]: tsdial: bart table size: 16
Aug 06 16:49:36 pbs tailscaled[482]: wgengine: Reconfig: configuring DNS
Aug 06 16:49:36 pbs tailscaled[482]: dns: Resolvercfg: {Routes:{.:[https://dns.nextdns.io/xxxx?device_...zz&device_model=linux&device_ip=100.112.216.3] ts.net.:[XXXXX:8007::53]} Hosts:14 LocalDomains:[tailXXXXXe.ts.net.]+65arpa}
Aug 06 16:49:36 pbs tailscaled[482]: dns: OScfg: {Nameservers:[100.100.100.100] SearchDomains:[tailxxxxe.ts.net.] }
Aug 06 16:49:36 pbs tailscaled[482]: peerapi: serving on http://100.112.xxxx.3:45039
Aug 06 16:49:36 pbs tailscaled[482]: peerapi: serving on http://[fd7a:115c:a1e0::XXXXX:XXXXXX]:55559
Aug 06 16:49:36 pbs tailscaled[482]: offline auto-update: stopping update checks
Aug 06 16:49:36 pbs tailscaled[482]: Switching ipn state Starting -> Running (WantRunning=true, nm=true)
Aug 06 16:49:39 pbs chronyd[528]: Selected source 85.199.214.101 (2.debian.pool.ntp.org)
Aug 06 16:49:39 pbs chronyd[528]: System clock TAI offset set to 37 seconds
Aug 06 16:49:45 pbs proxmox-backup-proxy[657]: get_network_interfaces failed - could not deserialize ip link output
Aug 06 16:49:55 pbs proxmox-backup-proxy[657]: get_network_interfaces failed - could not deserialize ip link output
Aug 06 16:50:05 pbs proxmox-backup-proxy[657]: get_network_interfaces failed - could not deserialize ip link output
Aug 06 16:50:15 pbs proxmox-backup-proxy[657]: get_network_interfaces failed - could not deserialize ip link output
Aug 06 16:50:25 pbs proxmox-backup-proxy[657]: get_network_interfaces failed - could not deserialize ip link output
Aug 06 16:50:35 pbs proxmox-backup-proxy[657]: get_network_interfaces failed - could not deserialize ip link output
Aug 06 16:50:45 pbs proxmox-backup-proxy[657]: get_network_interfaces failed - could not deserialize ip link output
Aug 06 16:50:55 pbs proxmox-backup-proxy[657]: get_network_interfaces failed - could not deserialize ip link output
Aug 06 16:51:05 pbs proxmox-backup-proxy[657]: get_network_interfaces failed - could not deserialize ip link output
Aug 06 16:51:15 pbs proxmox-backup-proxy[657]: get_network_interfaces failed - could not deserialize ip link output
Aug 06 16:51:25 pbs proxmox-backup-proxy[657]: get_network_interfaces failed - could not deserialize ip link output
Aug 06 16:51:35 pbs proxmox-backup-proxy[657]: get_network_interfaces failed - could not deserialize ip link output
Aug 06 16:51:45 pbs proxmox-backup-proxy[657]: get_network_interfaces failed - could not deserialize ip link output
Aug 06 16:51:55 pbs proxmox-backup-proxy[657]: get_network_interfaces failed - could not deserialize ip link output
Aug 06 16:52:05 pbs proxmox-backup-proxy[657]: get_network_interfaces failed - could not deserialize ip link output
Aug 06 16:52:15 pbs systemd[1]: Unmounting efi.mount - EFI System Partition Automount...
Aug 06 16:52:15 pbs systemd[1]: efi.mount: Deactivated successfully.
Aug 06 16:52:15 pbs systemd[1]: Unmounted efi.mount - EFI System Partition Automount.
 
  • Like
Reactions: Johannes S
Chris said:
Yes PVE 8.x is compatible as client for PBS 4.0

What exactly do you mean here? If it is co-installed you cannot upgrade just PBS to 4.0 while staying on PVE 8.x. If PBS is running in a VM, than you can upgrade the PBS instance within the VM just fine.
Click to expand...
Yes PBS is in a VM on a 8x node.
So I can upgrade PBS to 4 and wait a little for PVE (with a little snapshot just in case)

COOL :)
Thanks
 
Stoiko Ivanov said:
Thanks again for the keen eye! - Should be fixed now!
Click to expand...
Just a heads up, there are some references to pve filenames rather than pbs filenames in the repository sections - under both codeblock sections, listing: /etc/apt/sources.list.d/pve-enterprise.list & /etc/apt/sources-list.d/pve-install-repo.list
 
  • Like
Reactions: Stoiko Ivanov
dCkO said:
Just a heads up, there are some references to pve filenames rather than pbs filenames in the repository sections - under both codeblock sections, listing: /etc/apt/sources.list.d/pve-enterprise.list & /etc/apt/sources-list.d/pve-install-repo.list
Click to expand...
Thanks for the report! fixed that (and looked in the page for other mentions of pve this time)
 
Pre-upgrade, pbs3to4 reports a notice about systemd-boot. Post-upgrade, it does not throw a Warning that it should be removed as it does on pve8to9. Assumption, per the guide, removal is valid?
 
  • Like
Reactions: dCkO
Getting the following when running pbs3to4 --full

Code: 
: pbs3to4 --full
= CHECKING VERSION INFORMATION FOR PBS PACKAGES =

INFO: Checking for package updates..
PASS: all packages up-to-date
INFO: Checking proxmox backup server package version..
FAIL: could not match the 'proxmox-backup' package version, is it installed?
INFO: Check running kernel version..
PASS: running kernel '6.14.8-2-pve' is considered suitable for upgrade.

= MISCELLANEOUS CHECKS =

INFO: Checking PBS daemon services..
PASS: systemd unit 'proxmox-backup.service' is in state 'active'
PASS: systemd unit 'proxmox-backup-proxy.service' is in state 'active'
INFO: Checking for supported & active NTP service..
WARN: No (active) time synchronisation daemon (NTP) detected, but synchronized systems are important!
INFO: Checking for package repository suite mismatches..
PASS: found no suite mismatch
INFO: Checking bootloader configuration...
WARN: System booted in uefi mode but grub-efi-amd64 meta-package not installed, new grub versions will not be installed to /boot/efi!
             Install grub-efi-amd64.
SKIP: could not get dkms status

= SUMMARY =

TOTAL:     9
PASSED:    5
SKIPPED:   1
NOTICE:    0
WARNINGS:  2
FAILURES:  1

ATTENTION: Please check the output for detailed information!
Try to solve the problems one at a time and rerun this checklist tool again.

Thoughts on the error message below?
Code: 
FAIL: could not match the 'proxmox-backup' package version, is it installed?

Code: 
: proxmox-backup-manager versions
proxmox-backup-server 3.4.4-1 running version: 3.4.4

I upgraded Proxmox to version 9 recently. PBS is running on an LXC.
 
seelk said:
Getting the following when running pbs3to4 --full

Code: 
: pbs3to4 --full
= CHECKING VERSION INFORMATION FOR PBS PACKAGES =

INFO: Checking for package updates..
PASS: all packages up-to-date
INFO: Checking proxmox backup server package version..
FAIL: could not match the 'proxmox-backup' package version, is it installed?
INFO: Check running kernel version..
PASS: running kernel '6.14.8-2-pve' is considered suitable for upgrade.

= MISCELLANEOUS CHECKS =

INFO: Checking PBS daemon services..
PASS: systemd unit 'proxmox-backup.service' is in state 'active'
PASS: systemd unit 'proxmox-backup-proxy.service' is in state 'active'
INFO: Checking for supported & active NTP service..
WARN: No (active) time synchronisation daemon (NTP) detected, but synchronized systems are important!
INFO: Checking for package repository suite mismatches..
PASS: found no suite mismatch
INFO: Checking bootloader configuration...
WARN: System booted in uefi mode but grub-efi-amd64 meta-package not installed, new grub versions will not be installed to /boot/efi!
             Install grub-efi-amd64.
SKIP: could not get dkms status

= SUMMARY =

TOTAL:     9
PASSED:    5
SKIPPED:   1
NOTICE:    0
WARNINGS:  2
FAILURES:  1

ATTENTION: Please check the output for detailed information!
Try to solve the problems one at a time and rerun this checklist tool again.

Thoughts on the error message below?
Code: 
FAIL: could not match the 'proxmox-backup' package version, is it installed?

Code: 
: proxmox-backup-manager versions
proxmox-backup-server 3.4.4-1 running version: 3.4.4

I upgraded Proxmox to version 9 recently. PBS is running on an LXC.
Click to expand...
Just Google that error to see that it's not mandatory since you're using pve kernel, I ignored that error, upgraded without issues, only problem now is that tailscale break things but bug is already fixed as per few posts above.

Here's answer to you error Post in thread 'error message: proxmox-backup not correctly installed' https://forum.proxmox.com/threads/e...up-not-correctly-installed.104736/post-483898
 
Last edited:
  • Like
Reactions: dgsnb
You must log in or register to reply here.
Top Bottom