our backup storage (synology nas mounted via cifs) crashed last night during backup run.
some VMs have been stopped with io-error because of this (as they had been backed up when the crash happened), but unfortunately even with backup storage unmounted (umount -f...) i could not restart...
is there a way to limit backup parallelism/concurrency in a cluster?
i have 5 nodes and when they all have vzdump run in parallel, our nas is heavily saturated and each of the backup "threads" is running slow
let there be some "Status: IO-Error" for a VM, for example bacause of out-of-diskspace condition.
Where can i see more details about such errors, i searched a while but can find no logfile containing it.
I had some host where VMs got io errors from time to time and i would have found...
i'm using vm's with virtio-scsi-single, aio=threads and iothread=1 for better vm latency. i had too much trouble with vm jitter, cpu freeze on high io load situations.
when there is high write i/o in vm, i see kvm spawn 64 io threads for writing for the correspongin kvm vm process.
while backup is running, i'm getting this in syslog from pvestat (see below).
i'm backing up to a synology diskstation cifs share , which is mounted to all 5 cluster nodes.
doing ls on that mount is very slow to respond during backup.
despite that, backup seems to work fine.
i have come across https://www.linux-magazin.de/ausgaben/2017/05/kvm-security/2/ , which is telling that ksm may impose a security risk.
since it seems KSM is enabled in proxmox per default, i wonder if it's a good idea to have ksm active on a server which is hosting VMs exposed to the...
i had a problem with firefox at least twice that i see only "Search", "Task History" and "Subscription" after login and selecting one node in the datacenter.
page reload and clearing browser cache did not help, accessing cluster via different node or via private tab or different browser...
i'm trying to better understand verify/prune/garbage collection, which is an iops intensive process which keeps the pbs servers/storages i administer busy.
i'm often using fatrace as a utility for analysing filesystem access and i had a look at how proxmox-backup-server is accessing the...
is anybody using l2arc on single cheap consumer ssd with pbs, instead of using special device mirror (metadata allocation class) , as recommended in the pbs documentation - and would like to share his experience with that ?
i did not do exact performance comparison before/after yet, but my...
is there a way to reduce proxmox-backup-manager verbosity ?
i'm running pruny, verify and gc from a script and output to a logfile and most of the logfiles contents is progress information (processed 90% .... 91%.... )
it seems there is no option for this?
how do i determine which VM contributes most to backup growth, i.e. where the daily delta/increment is high ?
reason is, i want to put that VM into a different backup job/ds with a different gc/prune setting.
i have some datastore which is growing fast but i don't like to browse through all...
was macht man eigentlich wenn ein system kein efi boot kann und man proxmox 6.4 mit zfs 2.0 nutzen möchte ? es gibt doch nur die optionen grub-legacy boot und efi-boot via systemd-boot, oder?
ich hab mir jetzt schon das 3. (gottseidank) unwichtige system im kontext updates "geschrottet"...
i want to do a serialized gc/prune & verify from commandline via cronjob to minimize spinup/down of the backup-disk at my homeserver and i have come very close.
one problem is left:
how can i verify a datastore from cli with --ignore-verified and --outdated-after option...
i'm curious why proxmox only stores vm id and timestamp in the backup filename (also in pbs), but not the vm name.
this makes things intransparent, because i need extra steps to map a name to a "binary blob" i cannot easily derive the vm name from, especially when the backup is getting archived...
i have a low-power quadcore pc which has support for efi but, but after install i'm getting to an initramfs prompt and the system won't boot.
i disabled uefi boot in bios and reinstalled,but proxmox installs efi boot, though - and apparently and for my curiosity efi boot is enabled in bios...