Proxmox Backup Server 2.0 released!

martin

martin

Proxmox Staff Member
Staff member
Apr 28, 2005
754
1,741
223
We are excited to announce the next major release v2.0 of Proxmox Backup Server! This version is based on Debian 11 (codename "Bullseye"), but using the newer Linux kernel 5.11, and including OpenZFS 2.0.

Highlights
  • Tape Backup is stable and supported
  • Support for OpenID Connect providing Single Sign-On (SSO)
  • Full integration of Let's Encrypt/ACME in the front- and backend
  • Management of APT repositories via GUI: ability to enable and disable repositories
  • Single file-restore support for VMs that use ZFS, or LVM internally - accessible from GUI
  • ExtJS JavaScript framework to the latest GPL release 7.0
  • Improved Proxmox installer with improved ISO detection, switch_root instead of chroot, zstd compression
  • Live-restore feature allows for starting a VM, as soon as the restore starts (with Proxmox VE)
Countless bugfixes and smaller improvements are included as well, see the full release notes for details.

Thanks to all of you who were testing, bug reporting, and patch submitting. It helps a lot to get all the support and feedback!

Release notes
https://pbs.proxmox.com/wiki/index.php/Roadmap#Proxmox_Backup_Server_2.0

Press release
https://www.proxmox.com/en/news/press-releases/proxmox-backup-server-2-0-available

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

HELP & SUPPORT

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

Community Forum
https://forum.proxmox.com

Bugtracker
https://bugzilla.proxmox.com

Source Code
https://git.proxmox.com

FREQUENTLY ASKED QUESTIONS

Q: Can I dist-upgrade Proxmox Backup Server 1.1 to 2.x with apt?
A: Please follow the upgrade instructions on https://pbs.proxmox.com/wiki/index.php/Upgrade_from_1.1_to_2.x

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 7.0.

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

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 backup 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 on https://forum.proxmox.com/forums/announcements.7/ and pbs-devel mailing list https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel, and subscribe to our newsletter https://www.proxmox.com/news.

__________________
Best regards,

Martin Maurer
 
  • Like
Reactions: franko5, World Tech, Tacioandrade and 13 others
Works great!

One more for those with a similar set up:

Q: Can I upgrade without rebooting if I'm already running PVE7 bullseye on the same machine?
A: No. I tried restarting the services manually but it wouldn't work until I did a full reboot.
 
  • Like
Reactions: World Tech
Only this line made me loose my connection (no proper reading, I have no tapedrive :oops:).

systemctl stop proxmox-backup-proxy.service proxmox-backup.service

After reboot update went flawlessly.
 
  • Like
Reactions: World Tech
lukyjay said:
Q: Can I upgrade without rebooting if I'm already running PVE7 bullseye on the same machine?
A: No. I tried restarting the services manually but it wouldn't work until I did a full reboot.
Click to expand...
worked here in one of my test-setups - if you like to investigate that - please open a new thread (and ping me with @Stoiko Ivanov )
 
  • Like
Reactions: World Tech
birdy said:
Only this line made me loose my connection (no proper reading, I have no tapedrive :oops:).

systemctl stop proxmox-backup-proxy.service proxmox-backup.service
Click to expand...
Yeah, that will stop active tasks and the whole API daemon, so only execute it if no important task is running.
Also, as mentioned, it is only necessary if tape backup is set up and tape-related jobs could run, since the (tape) lock file paths had to change. An API daemon stop then ensures that no unsynchronized tape-device access can happen.
 
Last edited:
  • Like
Reactions: Tmanok
Just upgraded my small PBS box for SOHO use (installed since v0.8, WD Reds w/ some TB's, no ZFS). Went relatively fast and flawlessy, no issues. Many thanks for this major update! Keep this great piece of software running!
 
  • Like
Reactions: Tmanok and t.lamprecht
Also, on my upgraded server the kernel version is 5.10. I think is the regular bullseye kernel and not a proxmox (5.11) one.
Is it normal?

The original install came from a template of my dedicated server provider (Scaleway) and I don't know how is it build (Proxmox ISO, Debian ISO + Proxmox Repo...).
 
cyp said:
Thanks a lot for this release.

To upgrade my my server I needed to add bullseye repositories key
Click to expand...
That means you did not have the latest PBS 1.1 updates installed before starting the upgrade, as the proxmox-archive-keyring package ships the bullseye key since December 2020.

cyp said:
Also, on my upgraded server the kernel version is 5.10. I think is the regular bullseye kernel and not a proxmox (5.11) one.
Is it normal?
Click to expand...
This is an indication that you did not configured a Proxmox Backup Server repository, but rather just Debian ones?
 
  • Like
Reactions: Tmanok and Stoiko Ivanov
t.lamprecht said:
That means you did not have the latest PBS 1.1 updates installed before starting the upgrade, as the proxmox-archive-keyring package ships the bullseye key since December 2020.


This is an indication that you did not configured a Proxmox Backup Server repository, but rather just Debian ones?
Click to expand...

I have the Proxmox Backup Server repository and Proxmox services has been upgraded to 2.0 and working fine.
I just have a closer look and the Proxmox kernel is available when I do an apt search, seems it was just not installed during upgrade.
I will try to install it and reboot.
Maybe it's come from the original "Scaleway" install, I didn't remember which kernel has been used before upgrade.
 
( I run PBS as a vm in VMware ESXi 6.7)
Did the upgrade from 1.1-1 to 2.0-1 according to the wiki steps.
Not succesfull....errors! Please help needed...


● proxmox-backup.service - Proxmox Backup API Server
Loaded: loaded (/lib/systemd/system/proxmox-backup.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2021-07-13 19:46:59 CEST; 54s ago
Process: 924 ExecStart=/usr/lib/x86_64-linux-gnu/proxmox-backup/proxmox-backup-api (code=exited, status=127)
Main PID: 924 (code=exited, status=127)
CPU: 1ms

Jul 13 19:46:59 pbs.lan systemd[1]: Stopped Proxmox Backup API Server.
Jul 13 19:46:59 pbs.lan systemd[1]: proxmox-backup.service: Start request repeated too quickly.
Jul 13 19:46:59 pbs.lan systemd[1]: proxmox-backup.service: Failed with result 'exit-code'.
Jul 13 19:46:59 pbs.lan systemd[1]: Failed to start Proxmox Backup API Server.
Jul 13 19:46:59 pbs.lan systemd[1]: proxmox-backup.service: Start request repeated too quickly.
Jul 13 19:46:59 pbs.lan systemd[1]: proxmox-backup.service: Failed with result 'exit-code'.
Jul 13 19:46:59 pbs.lan systemd[1]: Failed to start Proxmox Backup API Server.
Jul 13 19:46:59 pbs.lan systemd[1]: proxmox-backup.service: Start request repeated too quickly.
Jul 13 19:46:59 pbs.lan systemd[1]: proxmox-backup.service: Failed with result 'exit-code'.
Jul 13 19:46:59 pbs.lan systemd[1]: Failed to start Proxmox Backup API Server.

● proxmox-backup-proxy.service - Proxmox Backup API Proxy Server
Loaded: loaded (/lib/systemd/system/proxmox-backup-proxy.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2021-07-13 19:50:46 CEST; 5s ago
Process: 1189 ExecStart=/usr/lib/x86_64-linux-gnu/proxmox-backup/proxmox-backup-proxy (code=exited, status=127)
Main PID: 1189 (code=exited, status=127)
CPU: 2ms

Jul 13 19:50:46 pbs.lan systemd[1]: proxmox-backup-proxy.service: Scheduled restart job, restart counter is at 5.
Jul 13 19:50:46 pbs.lan systemd[1]: Stopped Proxmox Backup API Proxy Server.
Jul 13 19:50:46 pbs.lan systemd[1]: proxmox-backup-proxy.service: Start request repeated too quickly.
Jul 13 19:50:46 pbs.lan systemd[1]: proxmox-backup-proxy.service: Failed with result 'exit-code'.
Jul 13 19:50:46 pbs.lan systemd[1]: Failed to start Proxmox Backup API Proxy Server.
 
The real log messages for the cause of the failing service start are further behind in the journal, can you execute:
Bash: 
journalctl -b -u proxmox-backup.service -u proxmox-backup-proxy.service
scroll to the time of the update and post the output from there (i.e., the lines shortly before "Start request repeated too quickly" starts to appear).

Please post also the output of: proxmox-backup-manager versions --verbose
 
t.lamprecht said:
The real log messages for the cause of the failing service start are further behind in the journal, can you execute:
Bash: 
journalctl -b -u proxmox-backup.service -u proxmox-backup-proxy.service
scroll to the time of the update and post the output from there (i.e., the lines shortly before "Start request repeated too quickly" starts to appear).

Please post also the output of: proxmox-backup-manager versions --verbose
Click to expand...
I'm sorry, just did a "fresh" installation of PBS 2.0-1.
Thanks for your help, and all the good work you guys do!
 
t.lamprecht said:
This is an indication that you did not configured a Proxmox Backup Server repository, but rather just Debian ones?
Click to expand...

I got the same problem.

These is /etc/apt/sources.list

Code: 
deb http://ftp.debian.org/debian bullseye main contrib
deb http://ftp.debian.org/debian bullseye-updates main contrib

# security updates
deb http://security.debian.org/debian-security bullseye-security main contrib



## Dotdeb Packages
##deb http://packages.dotdeb.org bullseye all
##deb-src http://packages.dotdeb.org bullseye all

deb http://download.proxmox.com/debian/pbs bullseye pbs-no-subscription

Code: 
uname -a
Linux pb1 5.10.0-7-amd64 #1 SMP Debian 5.10.40-1 (2021-05-28) x86_64 GNU/Linux


Edit: In order of keeping this thread clean, I created a new thread (https://forum.proxmox.com/threads/wrong-kernel-after-upgrade.92549/)
 
Last edited:
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom