Search results

It's an AMD 16 core with 128GB memory and dual 10-gbit and full SSD on both sides. There is no high load on either cluster/backup server. I altered the time a couple of times already, the last backup now worked but that could have been a lucky shot as it sometimes did work. I added the config...

No, I already thought of that and set the backup after all other backups on that cluster are finished. The backups on the cluster work together without any issues. Unless it's an issue on the pbs, as other backups from other clusters are possible at that time however we don't have any issues...

I have the same vzdump output and backup failure with 1 VM in a cluster of +- 200VM's. The VM doesn't hang/crash, only the backup fails. The only different with other VM's is that it's a very big VM with a 50TB disk on a ceph storage. This is getting backed up to a pbs server. The daily backup...

Similar issue here with same proxmox version and also on nfs: INFO: starting new backup job: vzdump 107 --remove 0 --compress zstd --storage backup2-prox02 --mode snapshot --node prox04 INFO: Starting Backup of VM 107 (qemu) INFO: Backup started at 2021-10-20 11:30:03 INFO: status = running...

small update: I don't have the problem when bonding 2 interfaces together through LACP. A reboot then works fine.

I also upgraded a host from proxmox 3 to 4 and encounter the same problem with the Broadcom/Qlogic BCM57840 NetXtreme II 10 Gigabit Ethernet (rev 11) using the bnx2x proxmox-ve: 4.2-58 (running kernel: 4.4.13-2-pve) pve-manager: 4.2-17 (running version: 4.2-17/e1400248) pve-kernel-4.4.6-1-pve...