Recent content by EvertM

Thank you for the fast reply :) We're not migrating between nodes, and we do not use HA at the moment.

Hi all, We have a cluster of 3 PVE nodes, all currently running PVE8. I would like to upgrade them all to PVE9 with minimal downtime. This would mean we'd be running a cluster with both PVE8 & PVE9 nodes for some days. Will this work? Is it as stable as a cluster with only PVE8 or only PVE9...

Here you go: (I assume you meant pveproxy-ssl.pem instead of pve-ssl.pem?) openssl x509 -in /etc/pve/local/pveproxy-ssl.pem -noout -text | grep "Algorithm" Signature Algorithm: sha256WithRSAEncryption Public Key Algorithm: id-ecPublicKey Signature Algorithm...

Hi all, Can someone explain the math here? This is part of the output of the pve8to9 script. INFO: Check node certificate's RSA key size PASS: Certificate 'pve-root-ca.pem' passed Debian Busters (and newer) security level for TLS connections (4096 >= 2048) PASS: Certificate 'pve-ssl.pem'...

Hi, I can see this happening with regular files (editing a text file without changing mtime), but is this even possible with backups of LXC/VM's?

Hi all, We have a bunch of VMs that we back up twice a day, to 2 different destinations: once to PBS and once to NFS. I had expected the dirty-bitmap to become invalid because of the alternating backup destinations, but apparently, that's not an issue because one uses vzdump and the other PBS...

Are you still collecting? I've limited the query to the last month with (journalctl -u pveproxy -u pvedaemon --since "1 month ago" | grep 'disabling inotify' | wc -l) server 1: count: 252 pveversion: pve-manager/8.3.2/3e76eec21c4a14a7 (running kernel: 6.8.12-6-pve) server 2: count: 1...

When I saw your comment I thought: 'Surely he/she/they/it must be joking, but nope... It appears password are indeed stored in plain text!

Hi, Can .pxarexclude be a symbolic link to another file? It would be much easier to update if I only had to edit one file instead of updating every single one.

That's what I thought, yeah... So perhaps 'INFO: processed 500.00 GiB in 1776 seconds (288.3 MiB/s)' would be a more accurate wording?

INFO: Starting Backup of VM 333 (qemu) INFO: Backup started at 2024-08-07 08:10:00 INFO: status = running INFO: VM Name: some.vm INFO: include disk 'scsi0' 'pool3:vm-333-disk-0' 500G INFO: backup mode: snapshot INFO: ionice priority: 7 INFO: skip unused drive 'local-zfs:vm-333-disk-0' (not...

I actually thought the rootfs of that box was zfs, but upon closer inspection it turns out to be Btrfs‍.

Reviving an old post here, but I'm seeing the same issue: those last 3 graphs are empty. I'm on PBS 3.2-7, installed on top of Debian.

That's because /etc/pve is a fuse, and those are excluded from getting indexed, unless you've modified /etc/updatedb.conf

I have a question about the 'Repeat missed' feature for scheduled backups in Proxmox: We have backup jobs scheduled to two different destinations. I understand that Proxmox runs only one backup job at a time. If the backup to destination 1 is running, the job to destination 2 will be skipped...