Proxmox Backup Server 2.1 released!

martin

martin

Proxmox Staff Member
Staff member
Apr 28, 2005
754
1,740
223
We are happy to announce version 2.1 of our Proxmox Backup Server! It's based on Debian 11.1 (codename "Bullseye"), but using the newer Linux kernel 5.13, and including OpenZFS 2.1.

We have improved the backup management now supporting flexible traffic-control bandwidth limits; this allows you to set limits for incoming and outgoing traffic from a set of networks. Also ‘group-filter’ for sync jobs and tape-backup jobs, and protected backups are possible.

Countless bugfixes and smaller improvements are included as well, see the full release notes for details.

A big THANK YOU to our community! We are really grateful for all the support and feedback, testing, bug reporting and patch submitting.

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

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

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 2.0 to 2.1 with apt?
A: Yes, just update via GUI or run "apt update && apt dist-upgrade"

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

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 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: Rainerle, trebuh, DerDanilo and 6 others
givan said:
One question - we're currently running PBS 2.0 with PVE 6.4-6, can we upgrade to PBS 2.1 and still run PVE 6.4-6?
Click to expand...
The Server part of Proxmox Backup 2.1 is still compatible with the 1.x clients, so yes, you can update your PBS 2.x to 2.1 and PVE 6.4 will still be able to back up or restore.
New features (like protection flag) may not be understood by old clients though, but that's expected and does not break things.

For the sake of completeness: a co-hosted PVE and PBS (on the same host installed without VM/CT separation) is only compatible when their Debian base release matches (PVE 6.x with PBS 1.x, bot Debian Buster or PVE 7.x and PBS 2.x, both Debian Bullseye).
 
Last edited:
  • Like
Reactions: DerDanilo, flames, vesalius and 1 other person
Hi!

Why doesn't 2.0 see the update?

root@Back-P1:~# apt update && apt dist-upgrade
Hit:1 http://security.debian.org bullseye-security InRelease
Hit:2 http://ftp.ru.debian.org/debian bullseye InRelease
Hit:3 http://ftp.ru.debian.org/debian bullseye-updates InRelease
Hit:4 http://download.proxmox.com/debian/pbs buster InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
 
I am also having a problem updating to v2.1, currently on v2.0-4.

root@pbs:~# apt update && apt dist-upgrade
Hit:1 http://ftp.ca.debian.org/debian bullseye InRelease
Hit:2 http://ftp.ca.debian.org/debian bullseye-updates InRelease
Hit:3 http://security.debian.org bullseye-security InRelease
Ign:4 https://enterprise.proxmox.com/debian/pbs bullseye InRelease
Ign:5 https://enterprise.proxmox.com/debian/pbs bullseye Release
Ign:6 https://enterprise.proxmox.com/debian/pbs bullseye/pbs-enterprise all Packages
Ign:7 https://enterprise.proxmox.com/debian/pbs bullseye/pbs-enterprise amd64 Packages
Ign:8 https://enterprise.proxmox.com/debian/pbs bullseye/pbs-enterprise Translation-en
Ign:9 https://enterprise.proxmox.com/debian/pbs bullseye/pbs-enterprise Translation-en_US
Ign:6 https://enterprise.proxmox.com/debian/pbs bullseye/pbs-enterprise all Packages
Ign:7 https://enterprise.proxmox.com/debian/pbs bullseye/pbs-enterprise amd64 Packages
Ign:8 https://enterprise.proxmox.com/debian/pbs bullseye/pbs-enterprise Translation-en
Ign:9 https://enterprise.proxmox.com/debian/pbs bullseye/pbs-enterprise Translation-en_US
Ign:6 https://enterprise.proxmox.com/debian/pbs bullseye/pbs-enterprise all Packages
Ign:7 https://enterprise.proxmox.com/debian/pbs bullseye/pbs-enterprise amd64 Packages
Ign:8 https://enterprise.proxmox.com/debian/pbs bullseye/pbs-enterprise Translation-en
Ign:9 https://enterprise.proxmox.com/debian/pbs bullseye/pbs-enterprise Translation-en_US
Ign:6 https://enterprise.proxmox.com/debian/pbs bullseye/pbs-enterprise all Packages
Ign:7 https://enterprise.proxmox.com/debian/pbs bullseye/pbs-enterprise amd64 Packages
Ign:8 https://enterprise.proxmox.com/debian/pbs bullseye/pbs-enterprise Translation-en
Ign:9 https://enterprise.proxmox.com/debian/pbs bullseye/pbs-enterprise Translation-en_US
Ign:6 https://enterprise.proxmox.com/debian/pbs bullseye/pbs-enterprise all Packages
Ign:7 https://enterprise.proxmox.com/debian/pbs bullseye/pbs-enterprise amd64 Packages
Ign:8 https://enterprise.proxmox.com/debian/pbs bullseye/pbs-enterprise Translation-en
Ign:9 https://enterprise.proxmox.com/debian/pbs bullseye/pbs-enterprise Translation-en_US
Ign:6 https://enterprise.proxmox.com/debian/pbs bullseye/pbs-enterprise all Packages
Ign:7 https://enterprise.proxmox.com/debian/pbs bullseye/pbs-enterprise amd64 Packages
Ign:8 https://enterprise.proxmox.com/debian/pbs bullseye/pbs-enterprise Translation-en
Ign:9 https://enterprise.proxmox.com/debian/pbs bullseye/pbs-enterprise Translation-en_US
Ign:6 https://enterprise.proxmox.com/debian/pbs bullseye/pbs-enterprise all Packages
Err:7 https://enterprise.proxmox.com/debian/pbs bullseye/pbs-enterprise amd64 Packages
401 Unauthorized [IP: 144.217.225.162 443]
Ign:8 https://enterprise.proxmox.com/debian/pbs bullseye/pbs-enterprise Translation-en
Ign:9 https://enterprise.proxmox.com/debian/pbs bullseye/pbs-enterprise Translation-en_US
Reading package lists... Done
E: Failed to fetch https://enterprise.proxmox.com/debian/pbs/dists/bullseye/pbs-enterprise/binary-amd64/Packages 401 Unauthorized [IP: 144.217.225.162 443]
E: Some index files failed to download. They have been ignored, or old ones used instead.



I believe the "E failed to fetch..." has to do with not paying for the subscription. some please correct me if I'm wrong

I also had to update my /etc/apt/sources.list.d/pbs-enterprise.list to include [Trusted=yes]
deb [trusted=yes] https://enterprise.proxmox.com/debian/pbs bullseye pbs-enterprise

nothing happens after this, i reboot the system/vm aswell and pbs is still running v2.0-4

more info: pbs is running in a proxmox vm.
 
chipbreak said:
do i change to the sources, to the same as ones i would use for proxmox?

deb http://ftp.debian.org/debian buster main contrib
deb http://ftp.debian.org/debian buster-updates main contrib
deb http://download.proxmox.com/debian/pve buster pve-no-subscription
Click to expand...


https://pbs.proxmox.com/docs/package-repositories.html


Note
You can disable this repository by commenting out the above line using a # (at the start of the line). This prevents error messages if you do not have a subscription key. Please configure the pbs-no-subscription repository in that case.
Click to expand...
 
  • Like
Reactions: chipbreak
  • Like
Reactions: Rainerle
I'm not sure if it's a coincidence or not, but since I've upgraded to this new version I am getting constant failures when trying to back up my VMs (scheduled or manually triggered). The failures are always due to "operation cancelled", but no one and/or nothing should be cancelling them. I just tried to do a manual backup this morning while the system was pretty idle and I ran into the same issue. Here is what things look like when it happens:

101: 2022-01-20 04:00:02 INFO: Starting Backup of VM 101 (qemu) 101: 2022-01-20 04:00:02 INFO: status = stopped 101: 2022-01-20 04:00:02 INFO: backup mode: stop 101: 2022-01-20 04:00:02 INFO: ionice priority: 7 101: 2022-01-20 04:00:02 INFO: VM Name: windows 101: 2022-01-20 04:00:02 INFO: include disk 'scsi0' 'local-zfs:vm-101-disk-1' 1000G 101: 2022-01-20 04:00:02 INFO: exclude disk 'scsi1' 'vault-zfs:vm-101-disk-0' (backup=no) 101: 2022-01-20 04:00:02 INFO: exclude disk 'scsi2' 'local-zfs:vm-101-disk-3' (backup=no) 101: 2022-01-20 04:00:02 INFO: include disk 'efidisk0' 'local-zfs:vm-101-disk-0' 1M 101: 2022-01-20 04:00:02 INFO: include disk 'tpmstate0' 'local-zfs:vm-101-disk-2' 4M 101: 2022-01-20 04:00:02 INFO: creating Proxmox Backup Server archive 'vm/101/2022-01-20T12:00:02Z' 101: 2022-01-20 04:00:02 INFO: starting kvm to execute backup task 101: 2022-01-20 04:00:10 INFO: attaching TPM drive to QEMU for backup 101: 2022-01-20 04:00:10 INFO: enabling encryption 101: 2022-01-20 04:00:10 INFO: started backup task '966d14ef-9865-4c1c-8841-1f32518cc7ce' 101: 2022-01-20 04:00:10 INFO: efidisk0: dirty-bitmap status: created new 101: 2022-01-20 04:00:10 INFO: scsi0: dirty-bitmap status: created new 101: 2022-01-20 04:00:10 INFO: tpmstate0-backup: dirty-bitmap status: created new 101: 2022-01-20 04:00:13 INFO: 0% (1.7 GiB of 1000.0 GiB) in 3s, read: 588.0 MiB/s, write: 341.3 MiB/s 101: 2022-01-20 04:00:33 INFO: 1% (10.8 GiB of 1000.0 GiB) in 23s, read: 464.2 MiB/s, write: 331.6 MiB/s 101: 2022-01-20 04:00:47 INFO: 2% (21.1 GiB of 1000.0 GiB) in 37s, read: 756.3 MiB/s, write: 246.0 MiB/s 101: 2022-01-20 04:01:07 INFO: 3% (30.7 GiB of 1000.0 GiB) in 57s, read: 491.4 MiB/s, write: 211.6 MiB/s 101: 2022-01-20 04:01:21 INFO: 4% (40.1 GiB of 1000.0 GiB) in 1m 11s, read: 682.3 MiB/s, write: 288.9 MiB/s 101: 2022-01-20 04:01:28 INFO: 4% (44.8 GiB of 1000.0 GiB) in 1m 18s, read: 689.7 MiB/s, write: 320.0 MiB/s 101: 2022-01-20 04:01:28 ERROR: job failed with err -125 - Operation canceled 101: 2022-01-20 04:01:28 INFO: aborting backup job 101: 2022-01-20 04:01:28 INFO: stopping kvm after backup task 101: 2022-01-20 04:01:29 ERROR: Backup of VM 101 failed - job failed with err -125 - Operation canceled

This is suspicious, I don't think these logs were ever present before:

101: 2022-01-20 04:00:10 INFO: efidisk0: dirty-bitmap status: created new 101: 2022-01-20 04:00:10 INFO: scsi0: dirty-bitmap status: created new

FWIW my other VM has the same problem (backup mode is different due to not using PCI-E passthrough):
100: 2022-01-20 03:00:01 INFO: Starting Backup of VM 100 (qemu) 100: 2022-01-20 03:00:01 INFO: status = running 100: 2022-01-20 03:00:01 INFO: VM Name: containers 100: 2022-01-20 03:00:01 INFO: include disk 'scsi0' 'local-zfs:vm-100-disk-1' 650G 100: 2022-01-20 03:00:01 INFO: include disk 'efidisk0' 'local-zfs:vm-100-disk-3' 1M 100: 2022-01-20 03:00:01 INFO: include disk 'tpmstate0' 'local-zfs:vm-100-disk-2' 4M 100: 2022-01-20 03:00:01 INFO: backup mode: snapshot 100: 2022-01-20 03:00:01 INFO: ionice priority: 7 100: 2022-01-20 03:00:01 INFO: skip unused drive 'local-zfs:vm-100-disk-0' (not included into backup) 100: 2022-01-20 03:00:01 INFO: creating Proxmox Backup Server archive 'vm/100/2022-01-20T11:00:01Z' 100: 2022-01-20 03:00:01 INFO: attaching TPM drive to QEMU for backup 100: 2022-01-20 03:00:01 INFO: issuing guest-agent 'fs-freeze' command 100: 2022-01-20 03:00:01 INFO: enabling encryption 100: 2022-01-20 03:00:01 INFO: issuing guest-agent 'fs-thaw' command 100: 2022-01-20 03:00:02 INFO: started backup task '852f0a82-20ae-40a9-8006-eed0703e5d74' 100: 2022-01-20 03:00:02 INFO: resuming VM again 100: 2022-01-20 03:00:02 INFO: efidisk0: dirty-bitmap status: created new 100: 2022-01-20 03:00:02 INFO: scsi0: dirty-bitmap status: created new 100: 2022-01-20 03:00:02 INFO: tpmstate0-backup: dirty-bitmap status: created new 100: 2022-01-20 03:00:05 INFO: 0% (4.9 GiB of 650.0 GiB) in 3s, read: 1.6 GiB/s, write: 57.3 MiB/s 100: 2022-01-20 03:00:08 INFO: 2% (15.9 GiB of 650.0 GiB) in 6s, read: 3.7 GiB/s, write: 56.0 MiB/s 100: 2022-01-20 03:00:11 INFO: 3% (24.3 GiB of 650.0 GiB) in 9s, read: 2.8 GiB/s, write: 8.0 MiB/s 100: 2022-01-20 03:00:14 INFO: 4% (31.3 GiB of 650.0 GiB) in 12s, read: 2.3 GiB/s, write: 25.3 MiB/s 100: 2022-01-20 03:00:17 INFO: 6% (39.2 GiB of 650.0 GiB) in 15s, read: 2.6 GiB/s, write: 117.3 MiB/s 100: 2022-01-20 03:00:25 INFO: 7% (45.9 GiB of 650.0 GiB) in 23s, read: 865.5 MiB/s, write: 100.0 MiB/s 100: 2022-01-20 03:00:32 INFO: 8% (53.4 GiB of 650.0 GiB) in 30s, read: 1.1 GiB/s, write: 269.7 MiB/s 100: 2022-01-20 03:00:38 INFO: 9% (59.0 GiB of 650.0 GiB) in 36s, read: 950.0 MiB/s, write: 68.7 MiB/s 100: 2022-01-20 03:00:42 INFO: 10% (66.1 GiB of 650.0 GiB) in 40s, read: 1.8 GiB/s, write: 35.0 MiB/s 100: 2022-01-20 03:00:45 INFO: 11% (72.7 GiB of 650.0 GiB) in 43s, read: 2.2 GiB/s, write: 33.3 MiB/s 100: 2022-01-20 03:00:57 INFO: 12% (78.2 GiB of 650.0 GiB) in 55s, read: 465.7 MiB/s, write: 24.3 MiB/s 100: 2022-01-20 03:01:03 INFO: 13% (84.9 GiB of 650.0 GiB) in 1m 1s, read: 1.1 GiB/s, write: 14.7 MiB/s 100: 2022-01-20 03:01:17 INFO: 14% (91.4 GiB of 650.0 GiB) in 1m 15s, read: 476.3 MiB/s, write: 6.9 MiB/s 100: 2022-01-20 03:01:30 INFO: 15% (97.5 GiB of 650.0 GiB) in 1m 28s, read: 482.2 MiB/s, write: 18.2 MiB/s 100: 2022-01-20 03:01:39 INFO: 16% (104.4 GiB of 650.0 GiB) in 1m 37s, read: 784.4 MiB/s, write: 58.7 MiB/s 100: 2022-01-20 03:01:42 INFO: 17% (111.4 GiB of 650.0 GiB) in 1m 40s, read: 2.3 GiB/s, write: 158.7 MiB/s 100: 2022-01-20 03:01:46 INFO: 18% (118.2 GiB of 650.0 GiB) in 1m 44s, read: 1.7 GiB/s, write: 153.0 MiB/s 100: 2022-01-20 03:01:49 INFO: 19% (124.4 GiB of 650.0 GiB) in 1m 47s, read: 2.1 GiB/s, write: 193.3 MiB/s 100: 2022-01-20 03:01:56 INFO: 20% (130.2 GiB of 650.0 GiB) in 1m 54s, read: 849.7 MiB/s, write: 69.1 MiB/s 100: 2022-01-20 03:02:12 INFO: 21% (137.4 GiB of 650.0 GiB) in 2m 10s, read: 461.8 MiB/s, write: 5.0 MiB/s 100: 2022-01-20 03:02:24 INFO: 22% (143.2 GiB of 650.0 GiB) in 2m 22s, read: 495.7 MiB/s, write: 1.0 MiB/s 100: 2022-01-20 03:02:40 INFO: 23% (149.6 GiB of 650.0 GiB) in 2m 38s, read: 409.8 MiB/s, write: 1.2 MiB/s 100: 2022-01-20 03:02:50 INFO: 24% (156.4 GiB of 650.0 GiB) in 2m 48s, read: 701.6 MiB/s, write: 16.8 MiB/s 100: 2022-01-20 03:02:53 INFO: 25% (166.9 GiB of 650.0 GiB) in 2m 51s, read: 3.5 GiB/s, write: 60.0 MiB/s 100: 2022-01-20 03:02:56 INFO: 27% (177.0 GiB of 650.0 GiB) in 2m 54s, read: 3.4 GiB/s, write: 46.7 MiB/s 100: 2022-01-20 03:02:59 INFO: 29% (189.4 GiB of 650.0 GiB) in 2m 57s, read: 4.1 GiB/s, write: 16.0 MiB/s 100: 2022-01-20 03:03:02 INFO: 30% (201.2 GiB of 650.0 GiB) in 3m, read: 3.9 GiB/s, write: 13.3 MiB/s 100: 2022-01-20 03:03:05 INFO: 32% (209.9 GiB of 650.0 GiB) in 3m 3s, read: 2.9 GiB/s, write: 24.0 MiB/s 100: 2022-01-20 03:03:08 INFO: 33% (216.1 GiB of 650.0 GiB) in 3m 6s, read: 2.1 GiB/s, write: 176.0 MiB/s 100: 2022-01-20 03:03:11 INFO: 34% (227.0 GiB of 650.0 GiB) in 3m 9s, read: 3.6 GiB/s, write: 133.3 MiB/s 100: 2022-01-20 03:03:14 INFO: 36% (237.0 GiB of 650.0 GiB) in 3m 12s, read: 3.3 GiB/s, write: 153.3 MiB/s 100: 2022-01-20 03:03:17 INFO: 38% (248.7 GiB of 650.0 GiB) in 3m 15s, read: 3.9 GiB/s, write: 30.7 MiB/s 100: 2022-01-20 03:03:20 INFO: 39% (256.1 GiB of 650.0 GiB) in 3m 18s, read: 2.5 GiB/s, write: 0 B/s 100: 2022-01-20 03:03:23 INFO: 40% (263.9 GiB of 650.0 GiB) in 3m 21s, read: 2.6 GiB/s, write: 26.7 MiB/s 100: 2022-01-20 03:03:26 INFO: 41% (269.2 GiB of 650.0 GiB) in 3m 24s, read: 1.8 GiB/s, write: 70.7 MiB/s 100: 2022-01-20 03:03:29 INFO: 42% (273.0 GiB of 650.0 GiB) in 3m 27s, read: 1.3 GiB/s, write: 42.7 MiB/s 100: 2022-01-20 03:03:42 INFO: 43% (280.1 GiB of 650.0 GiB) in 3m 40s, read: 553.2 MiB/s, write: 630.2 KiB/s 100: 2022-01-20 03:03:59 INFO: 44% (286.2 GiB of 650.0 GiB) in 3m 57s, read: 367.5 MiB/s, write: 3.1 MiB/s 100: 2022-01-20 03:04:20 INFO: 45% (292.6 GiB of 650.0 GiB) in 4m 18s, read: 314.5 MiB/s, write: 2.1 MiB/s 100: 2022-01-20 03:04:27 INFO: 46% (299.4 GiB of 650.0 GiB) in 4m 25s, read: 991.4 MiB/s, write: 121.1 MiB/s 100: 2022-01-20 03:04:33 INFO: 47% (305.6 GiB of 650.0 GiB) in 4m 31s, read: 1.0 GiB/s, write: 107.3 MiB/s 100: 2022-01-20 03:04:40 INFO: 48% (312.6 GiB of 650.0 GiB) in 4m 38s, read: 1.0 GiB/s, write: 33.7 MiB/s 100: 2022-01-20 03:04:46 INFO: 49% (319.3 GiB of 650.0 GiB) in 4m 44s, read: 1.1 GiB/s, write: 108.0 MiB/s 100: 2022-01-20 03:04:55 INFO: 50% (325.1 GiB of 650.0 GiB) in 4m 53s, read: 659.1 MiB/s, write: 9.3 MiB/s 100: 2022-01-20 03:05:11 INFO: 51% (332.3 GiB of 650.0 GiB) in 5m 9s, read: 460.5 MiB/s, write: 7.8 MiB/s 100: 2022-01-20 03:05:29 INFO: 52% (338.0 GiB of 650.0 GiB) in 5m 27s, read: 326.0 MiB/s, write: 6.9 MiB/s 100: 2022-01-20 03:05:48 INFO: 53% (344.5 GiB of 650.0 GiB) in 5m 46s, read: 349.7 MiB/s, write: 5.3 MiB/s 100: 2022-01-20 03:06:05 INFO: 54% (352.2 GiB of 650.0 GiB) in 6m 3s, read: 462.4 MiB/s, write: 6.8 MiB/s 100: 2022-01-20 03:06:13 INFO: 55% (357.6 GiB of 650.0 GiB) in 6m 11s, read: 686.5 MiB/s, write: 16.5 MiB/s 100: 2022-01-20 03:06:17 INFO: 55% (358.5 GiB of 650.0 GiB) in 6m 15s, read: 236.0 MiB/s, write: 0 B/s 100: 2022-01-20 03:06:17 ERROR: job failed with err -125 - Operation canceled 100: 2022-01-20 03:06:17 INFO: aborting backup job 100: 2022-01-20 03:06:17 INFO: resuming VM again 100: 2022-01-20 03:06:17 ERROR: Backup of VM 100 failed - job failed with err -125 - Operation canceled

Is anyone aware of why backups would stop working with these cancellation failures on the new version?
 
Last edited:
Sorry, please ignore my previous post. I just found a bunch of corruption in my ZFS pool :) Will post back here if it still happens after recovering from that. I'm pretty sure there's no issue with PVE or PBS at this point.
 
So, is there a way to upgrade from 2.0-4 to 2.1 ?
"""
Q: Can I dist-upgrade Proxmox Backup Server 2.0 to 2.1 with apt?
A: Yes, just update via GUI or run "apt update && apt dist-upgrade"
"""
Doesn't do the job.

*EDIT* - Found the problem... the "no-subscription" repository wasn't added.
*Suggestion* - Maybe the "no-subscription" repository should exist by default on fresh PBS & PVE installs, and be replaced by the enterprise repository when a license is added.
 
Last edited:
onepamopa said:
*Suggestion* - Maybe the "no-subscription" repository should exist by default on fresh PBS & PVE installs, and be replaced by the enterprise repository when a license is added.
Click to expand...

The default settings are best for paying subscribers.

If you do not want to subscribe, you can do the change via GUI with two clicks.
 
Hi Team @tom

Something i've noticed from v1 of PBS upto current 2.1.5 is that the UI doesn't allow to create or edit vlans on a bond.

ive manually created them from the command line but nothing works in the UI.

Just an FYI in case no one has reported this.

""Cheers
G
 
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
Back