Have you any information on dmesg or journalctl?, it will be a hardware failure, due to ram (memtest is your friend) or even power supply failure not serving the necessary voltage/current to the equipment.
You may setup another PBS instance in a remote location and made a sync Job between the two pbs.
https://pbs.proxmox.com/docs/managing-remotes.html
After this You can setup another pbs storage for the remote pbs
You can try to use the NFS as a removable storage in PBS, if the PBS host dies, you can create a new one, and add the storage again as a removable existent media.
If you use this trick you can access again to your backups.
You can try to boot with a live debian image, and do a copy of the disks in the lvm volume to a external usb or via rsync to a new machine. To find the disks you can use:
pvesm list local-lvm
Then for example:
qemu-img convert -O qcow2...
Thanks, this helped me finding the issue:
Adding the following lines to `/usr/share/perl5/PVE/API2/Storage/Content.pm` to the create function:
use Data::Dumper;
use Sys::Syslog;
syslog('info', Dumper($param));
The call was...
First you need to check the performance of your storage, yo can test it with fio command
https://pve.proxmox.com/wiki/Benchmarking_Storage
Also you can try
pveperf
For example
pveperf /var/lib/vz
Is not a good idea making backups in different datastores as you miss the dirty bit, so every time you do a backup weekly or monthly is a new copy not incremental.
The existing storage network is not affected. You only need to add a network that can communicate with your PBS, and when you add /modify the PBS storage it will try to reach the PBS by the new IP address.
There are some several escenarios for your approach:
1) You can use a firewall like Pfsense/Opnsense to connect it directly to your wan connection of any way (ppoE, DHCP, etc) for this you need to know what is the method for doing this. After...
This is a known issue after upgrade due changes made to systemd defaults. As shown in this section of the upgrade process, audit logging is disabled by default in Bookworm, and in Trixie this audit log is enabled.
systemctl disable --now...