Search results

This is strange, now i tried another test, and the node that is out of quorum did not auto restart.

Is this by design? Am I missing something? If any one of my nodes drops due to network issue or anything, then once it rejoins it causes the remaining nodes to restart?

Stop mode didn't with for me either, wondering if this is because my qcow2 is in raw mode, what's yours?

I'm still having the same issues, I had to disable HA on the VM I was having this error on, and use STOP mode backup. I'm not sure what the issue is, I watched my df during a backup and didn't see /tmp run out of space. But could have been a fluke.

Well, problem with STOP mode is HA.... INFO: starting new backup job: vzdump 110 --mode stop --mailnotification always --storage Backup-1n1 --quiet 1 --compress zstd ERROR: Backup of VM 110 failed - Cannot execute a backup with stop mode on a HA managed and enabled Service. Use snapshot mode or...

Same result using suspend backup, and ZSTD. INFO: suspending guest INFO: creating vzdump archive '/mnt/pve/Backup-1n1/dump/vzdump-qemu-110-2020_10_24-00_00_02.vma.zst' INFO: skipping guest-agent 'fs-freeze', agent configured but not running? INFO: started backup task...

I just switched it to suspend mode backup, will report if there's a change

This is happening to me too on 6.2-12 Target is a local nfs, only happens on one of my QM's and it locks up the VM instance that I need to hard stop and start after every node backup. INFO: creating vzdump archive '/mnt/pve/Backup-1n1/dump/vzdump-qemu-110-2020_10_22-19_30_02.vma.lzo' INFO...