I tried this before but hit a wall, I don't think the Synology kernel supports this, see below for reference
https://github.com/bcleonard/proxmox-qdevice/issues/10#issuecomment-2094267851
https://github.com/bcleonard/proxmox-qdevice/issues/2
Ah ha! Thanks for spotting that. You are right of course.
This fixed it:
root@nas:~# chmod 0755 /volume1/pbs
root@nas:~# chown 34:34 /volume1/pbs
root@pbs:~# proxmox-backup-client benchmark --repository syno-pbs
Password for "root@pam"...
My datastore is mounted via NFS, I don't have a /host dir in there at all (?)
root@pbs:/# find / -type d -name host
/usr/lib/modules/6.8.12-8-pve/kernel/drivers/ufs/host
/usr/lib/modules/6.8.12-8-pve/kernel/drivers/memstick/host...
This is what I see...
root@pbs:~# journalctl -f
Mar 31 11:45:51 pbs systemd[1210]: Listening on gpg-agent-extra.socket - GnuPG cryptographic agent and passphrase cache (restricted).
Mar 31 11:45:51 pbs systemd[1210]: Listening on...
This:
Linux pbs 6.8.12-9-pve #1 SMP PREEMPT_DYNAMIC PMX 6.8.12-9 (2025-03-16T19:18Z) x86_64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual...
Thank you for trying to help. No it is not in an LXC - I'm running it from a root shell on my PBS directly, which is a full Debian bookworm VM installed from the official PBS ISO, running on Synology VMM.
Can anyone help me figure out how to benchmark with the --repository flag? No matter what I try, it doesn't work...
https://pbs.proxmox.com/docs/backup-client.html#benchmarking
# whoami
root
# proxmox-backup-client benchmark --repository...
Anything new here in Mar 2025? I am facing the same issue. Only 1 VM that has GPU passthrough enabled, but it keeps failing to back up.
edit: In my case it was caused by a failure of PCI passthru, so the VM would not even start. Not actually a...
I'm still a little confused about how to properly configure the verification jobs. I had posted before about yellow warning exclamation marks appearing next to everything in my repo before, but they came back. So I added a full verify job.
Does...
So... if I already have a backup job for "all" targets (eg below), I should delete that and create a new job only for the specific VMs that i want backed up? Because it doesn't allow me to de-select just a single VM...
I know we can exclude an individual disk from getting backed up to PBS by unchecking the "Backup" checkbox in the Hardware tab...
What I was wondering is: is there a way to completely exclude ALL disks (aka entire VM) from being backed up? (even...
Everything is green again, thank you
I still wonder how the condition happened in the first place. Maybe somehow the PBS was shut down at the scheduled time of the Full Verify task? But, wouldn't it run automatically the next day if it missed...