Recent content by mgabriel

First, I assume the zfs special device and cache device should speed up the hdd pool, correct? It doesn't make sense to have a special device or cache pool for the nvme devices. Second, do you want to passthrough the hdd devices or not? You wrote that passthrough is recommended by the software...

Why don't you install apcupsd or nut directly on one node and use this node as network server? The other node gets the status of the first node if the UPS fails and both can trigger their shutdown. Or is there anything I missed?

Ah, so you're talking about a nested virtualization with a virtual Proxmox. Best would be to file a festure request at https://bugzilla.proxmox.com/.

It's probably even easier by using a backup hook script that checks, if this mountpoint is the one you expect. Two examples: You could mark the disk with a touch /mnt/backuphdd/backup-disk-marker and only if that file exists, do your backups or try to mount the disk first and check again...

Yes. What SMART values would you expect from a virtual device?

Den hast du vermutlich im PBS gesehen. Da ergeben entfernbare Medien durchaus Sinn, bei einem Proxmox VE eher nicht im Regelfall. Wenn du Backups darauf sicherst und deshalb die Platte regelmäßig tauschen möchtest, schau dir mal die Backup Hook Scripts an, die können ein Medium automatisch vor...

Thanks for reporting - at least you found the cause. :)

If this was a debian 12 with a Kernel 6.1, it uses some older Broadcom modules to power your NICs than the Proxmox Kernel 6.8 or newer. Proxmox upgraded from Kernel 6.5 to 6.8 with Proxmox VE 8.2 - if this happened after an update, this may be your problem. But the errors we've seen most is that...

You may want to read the part in the official documentation here: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#sysadmin_certificate_management Basically you can use a ACEM/Let's Encrypt certificate or you can buy a commercial one and upload it.

I'm not sure if I understood you correctly. You'd normally connect to https://<serveraddress>:8006 and you're right, you will get a certificate warning as Proxmox VE uses a self-signed certificate that can't be validated by your browser. You can replace the certificate later if you wish.

Das Log wird über stderr ausgegeben, daher wird ein proxmox-backup-client [...] 2> backup.log auch etwas in die Log-Datei schreiben. ;-)

please post your `/etc/network/interfaces`. Besides a configuration issue, it may also be a timing problem that some NIC isn't ready while it already should be. As a workaround, you can try to add some `pre-up sleep 5` (5 = seconds, increase if necessary) to the configuration of your physical NICs.

I'd recommend using zvols over datasets as you have several advantages like better performance and zfs snapshots.

Du könntest das Re-Verify Setting sehr hoch stellen: Standardmäßig steht es bei 30 Tagen, so dass frühere Backups alle 30 Tage einmal überprüft werden. Stellst du das auf 90, 180, 365 Tage, werden die alten Backups seltener geprüft. Falls du darunter ein Filesystem wie ZFS verwendest, was ein...

You can set the number of Proxmox VE worker threads under Datacenter -> Options from 4 to the setting you like. If you use too many workers doing the same things, you may run into some locks where your tasks may timeout.