Search results

Ahhh, good catch - I had no idea what I was looking at... Javascript isn't my strong point :D

Ahhhh - gotcha! I did have the Notification mode set to 'Auto'. I changed this to "Notification system" and I'll see what happens after the backups overnight. The message I got was from the mail subsystem - so probably via the local postfix service. As for the checkbox, it shows as: Install...

No rush - I've been experimenting with PBS over the weekend, and this is the first non-pve host that I'm playing with. I'm guessing most people haven't hit this yet - and its really not critical for me, so it certainly isn't a breaking thing for me (and I guess nobody else as I couldn't find...

matcher: default-matcher comment Route all notifications to mail-to-root mode all target <mailserver with . changed to _> sendmail: mail-to-root comment Send mails to root@pam's email address disable true mailto-user root@pam smtp: <mailserver with . changed to _> from-address...

Yep - I can confirm that using the IP address instead of fqdn seems to function. I'm wondering if the FQDN is being resolved as an IPv6 address and is somehow confusing the : in the resulting repository string? However, I tried both IPv4 and IPv6 addresses - enclosing the IPv6 address in square...

Wait, I just realised you said client version 3.4.2-1... Looking here, I only see 3.4.1 - which I'm currently using. http://download.proxmox.com/debian/pbs-client/dists/bookworm/main/binary-amd64/ Should I get an update to 3.4.2 somewhere? EDIT: I did find the 3.4.2 client here...

Gotcha - I just tried with the `root@pam` account, that did prompt for a password - but that still core dumped. EDIT: I did try to send you a DM with the full datastore, repository and namespace strings to not have them archived online forever, but seems I'm not allowed to send DMs to you :) I...

Hmmmm - stupid question - when I provide the repository via --repository and not the env, it gives me an error: Error: error building client for repository <repository> - API token secret must be provided! I can't seem to figure out a way to get the client to prompt for this secret. Setting...

Interesting. Would kernel version matter? $ cat /proc/version Linux version 6.15.2-200.fc42.x86_64 (mockbuild@68257c1a2c9d417aaa957cc59746e9d9) (gcc (GCC) 15.1.1 20250521 (Red Hat 15.1.1-2), GNU ld version 2.44-3.fc42) #1 SMP PREEMPT_DYNAMIC Tue Jun 10 15:17:23 UTC 2025 Just about to update...

Thanks - happy to test a static binary of `proxmox-backup-client` and `pxar` if you can provide one somewhere as a result of that patch.

I've tried extracting the proxmox-backup-client-static deb and copying the files to a Fedora 42 machine. A number of functions seem to fail with an error of "Floating point exception (core dumped)". ie: [root@<$hostname> bin]# proxmox-backup-client task list Floating point exception (core...

I've just set up the SMTP notifications on PVE - and the test email works fine. When the system itself starts to send notifcations via the SMTP path, the mail server replies with: <email@host.com: host mail.server[<mail server ip>] said: 530 5.7.0 Must issue a STARTTLS command first (in...

@t.lamprecht - I'm just wondering if anything became of this.... I'm just looking through all this again because PBS and PDM both need the same 'hack' for me to get the nsupdate DNS method working for ACME. It's been a bit of silence for quite some time - and its getting more difficult to keep...

I have a feeling that its the way PVE has snapshotted / backed up the VM... ie when the filesystem is still in use. It's obviously mostly in tact, as I can browse the files in PVE's "File Restore" - but likely because it isn't cleanly unmounted. XFS would normally check the fs on mounting next...

I guess it depends on the filesystem that the VM guest is using. In this case, something about how the backup functions causes the mount to fail. The block device is still there and available, but the filesystem can't be mounted.

Yeah - I mean, it makes sense that it would be read-only image - however if we can't mount it at all, then it means recovering an individual file via the PBS client isn't really possible. I did note that the "File Restore" function in PVE seems to allow me to browse the image though: This...

Interestingly, I'm trying this out with the PVE integration... When I'm trying to mount a snapshot of a VM on the PBS server to browse the backup, I'm getting: root@pbs:/mnt# mount -o ro /dev/loop0p2 /mnt/tmp/ mount: /mnt/tmp: cannot mount /dev/loop0p2 read-only. dmesg(1) may have more...

Done: https://bugzilla.proxmox.com/show_bug.cgi?id=6473

So, here's what I've come up with so far...... I hooked into udev via /etc/udev/rules.d/local.rules as: KERNEL=="sda", ACTION=="add", ENV{SYSTEMD_WANTS}+="backup_to_usb.service" KERNEL=="sdb", ACTION=="add", ENV{SYSTEMD_WANTS}+="backup_to_usb.service" That fires off the following systemd...

Interestingly, I came across this thread hunting for this type of feature. I currently use a backup system that I've built over 20+ years of use that uses rsync + snapshots + btrfs that also backs up the latest VM contents to an external disk when inserted / hotplugged. This uses LUKS etc as...