Recent content by fabian

the question is phrased the wrong way round - anybody can write integrations for other backup targets for Proxmox ;) please ask Netbackup whether they support Proxmox guest backups..

you can regenerate it with pvecm updatecerts -f, but IIRC the only thing the self-signed CA and cert is used for if you have a custom/ACME cert is pinning SPICE connections..

https://bugzilla.proxmox.com/show_bug.cgi?id=4275 but like @_gabriel said, you can allocate the target disks, and then restore into them (via a pipe, for example) as a workaround, if the default of "use storage like at backup time" is not possible. editing the backed-up config doesn't really...

see https://bugzilla.proxmox.com/show_bug.cgi?id=4693

yeah, the errors all involve perl, so likely *something* there is broken

ah, I misread pveversion above, sorry, that actually seems somewhat okay. still, all the symptoms point at some kind of corruption or hardware issue (random processes shouldn't segfault, and core perl functionality should work as well ;)).

what do you mean? right now both are just directories on the root file system. if you want to have them separate, you need to put them somewhere else (e.g., on their own partition/LV/filesystem).

could you also post "apt update" output? your system is definitely not current ;)

yes, that should also help.

/boot is different than the ESP though - we don't set up a separate /boot for ages.. although the same issues apply to both /boot (if on its own partition) and /boot/efi of course.

note that the disks are still exactly where they were before - just one of the links pointing at them was dropped ;) these links are similar to those in /dev/disk/by-XXX and can change depending on the rule set. you can also write your own if you want :p

root@pve:~# pveupgrade Starting system upgrade: apt-get dist-upgrade Segmentation fault root@pve:~# pveupgrade Starting system upgrade: apt-get dist-upgrade this does look very suspicious though - either some on-disk corruption, or broken memory. can you try "debsums -c" (requires to install...

please provide "pveversion -v" (or if that is not possible, "apt list --installed")

you do need to manually remove kernels from time to time, there is no way around it.

this was changed upstream in OpenZFS back in 2021: https://github.com/openzfs/zfs/pull/12303 and made its way into the ZFS 2.2.0 stable release, which was imported into PVE last fall.. you can iterate over the VM config and call "pvesm path $VOLUME" on each volume to get the path.