like many other sites and pieces of public infrastructure, ours is getting hammered by AI scrapers/bots as well. we try our best to implement counter measures, but it's a constant game of whack-a-mole.
OK, but the verify jobs are read-only jobs, they don't create any snapshot etc, so why does it prevent creation of a snapshot an only one but all? As you can see in the attached job logs, the sync job does its job for the other snapshots without...
Hi,
Is it normal to get bellow error in a Sync (pull) job when also a Verify job running on the same datastore?
2026-05-16T09:00:14+03:00: [vm/164]: sync group vm/164 failed - 2026-05-15T22:00:43Z: while creating locked snapshot 'BackupDir {...
Hi!
You can configure these with the environment variables PBS_RESTORE_FETCH_CONCURRENCY for the amount of parallel chunk fetches and PBS_RESTORE_MAX_THREADS for the maximum amount of threads. You should be able to use these in front of the...
Hi,
When using "qmrestore" for backup restore tests it uses 4 threads by default: "using up to 4 threads .... fetching up to 16 chunks in parallel". So how can I configure these values? I want to decrease it for testing (to see if it will affect...
There is a new QEMU 11.0 package available in the pve-test and pve-no-subscription repositories for Proxmox VE 9.
After internally testing QEMU 11.0 for over two weeks and having this version available on the pve-test repository for over a week...
For reference, patches have been submitted to the developer mailing list: https://lore.proxmox.com/pbs-devel/20260430121015.528664-1-c.ebner@proxmox.com/T/#t
@dcsapak
Maybe related to the following issue?
https://forum.proxmox.com/threads/confusingly-different-sync-durations.183039/
https://lore.proxmox.com/pbs-devel/20260427120543.2692503-1-d.csapak@proxmox.com/T/#u1111
P.S. Chris replied while I...
Hi,
thanks for the report. There was a recent fix for the sync and verify task logs, but this did not cover other task views. Will send a patch for this shortly.
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...
Hi,
It seems there is some calculation error in GC job status modal:
As you can see in this screen shot it shows duration as +10 hours. But the jobs logs and the summary page shows the real duration correctly as ~2 hours...
Thanks, based on the information at hand I've send a tentative fix to the developer mailing list: https://lore.proxmox.com/pbs-devel/20260422073351.181581-1-c.ebner@proxmox.com/T/
Sure, here it is:
root@pbs1:~# apt-cache policy proxmox-backup-server
proxmox-backup-server:
Installed: 4.1.7-2
Candidate: 4.1.7-2
Version table:
*** 4.1.7-2 500
500 http://download.proxmox.com/debian/pbs...
It seems this fixed the problem, thanks :) I could not find any meaningful result for this error on Google search. Everything seems to working now.
root@pbs1:~# hexdump /var/lib/proxmox-backup/s3-statistics/ulakfkm-default-bucket-ulakfkm.shmem |...
Here it is:
root@pbs1:~# hexdump /var/lib/proxmox-backup/s3-statistics/ulakfkm-default-bucket-ulakfkm.shmem | head -n 1
0000000 0000 0000 0000 0000 0000 0000 0000 0000
Last sync job from local datastore to s3 backed datastore failed with a strange error:
detected wrong types in mmaped files: incorrect magic number for request counters detected
I see the same error in all PBS GUI sections about this...