[SOLVED] Backup Failing

M

mtctech

New Member
Proxmox Subscriber
Apr 25, 2025
3
0
1
Running into a problem with backups failing on the server. Previously they worked sending to a NAS. It runs off the main host.

df -hl
root@pve:~# df -hl
Filesystem Size Used Avail Use% Mounted on
udev 32G 0 32G 0% /dev
tmpfs 6.3G 2.8M 6.3G 1% /run
/dev/mapper/pve-root 94G 82G 7.7G 92% /
tmpfs 32G 49M 32G 1% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
efivarfs 304K 164K 136K 55% /sys/firmware/efi/efivars
/dev/nvme0n1p2 1022M 12M 1011M 2% /boot/efi
/dev/fuse 128M 20K 128M 1% /etc/pve
tmpfs 6.3G 0 6.3G 0% /run/user/0


Code: 
2001: 2025-07-05 15:00:01 INFO: Starting Backup of VM 2001 (qemu)
2001: 2025-07-05 15:00:01 INFO: status = running
2001: 2025-07-05 15:00:01 INFO: VM Name: bridc
2001: 2025-07-05 15:00:01 INFO: include disk 'scsi0' 'vms-vlm-thin:vm-2001-disk-1' 300G
2001: 2025-07-05 15:00:01 INFO: include disk 'efidisk0' 'vms-vlm-thin:vm-2001-disk-0' 4M
2001: 2025-07-05 15:00:01 INFO: include disk 'tpmstate0' 'vms-vlm-thin:vm-2001-disk-2' 4M
2001: 2025-07-05 15:00:02 INFO: backup mode: snapshot
2001: 2025-07-05 15:00:02 INFO: ionice priority: 7
2001: 2025-07-05 15:00:02 INFO: snapshots found (not included into backup)
2001: 2025-07-05 15:00:02 INFO: creating vzdump archive '/var/lib/vz/dump/vzdump-qemu-2001-2025_07_05-15_00_01.vma.zst'
2001: 2025-07-05 15:00:02 INFO: attaching TPM drive to QEMU for backup
2001: 2025-07-05 15:00:02 INFO: issuing guest-agent 'fs-freeze' command
2001: 2025-07-05 15:00:03 INFO: issuing guest-agent 'fs-thaw' command
2001: 2025-07-05 15:00:04 INFO: started backup task '1029426c-023f-4532-9f59-a73b90b8282f'
2001: 2025-07-05 15:00:04 INFO: resuming VM again
2001: 2025-07-05 15:00:07 INFO:   0% (1.6 GiB of 300.0 GiB) in 3s, read: 559.9 MiB/s, write: 512.1 MiB/s
2001: 2025-07-05 15:00:12 INFO:   1% (3.3 GiB of 300.0 GiB) in 8s, read: 338.3 MiB/s, write: 329.9 MiB/s
2001: 2025-07-05 15:00:21 INFO:   2% (6.3 GiB of 300.0 GiB) in 17s, read: 345.2 MiB/s, write: 342.9 MiB/s
2001: 2025-07-05 15:00:30 INFO:   3% (9.1 GiB of 300.0 GiB) in 26s, read: 319.0 MiB/s, write: 313.1 MiB/s
2001: 2025-07-05 15:00:40 INFO:   4% (12.2 GiB of 300.0 GiB) in 36s, read: 317.5 MiB/s, write: 312.8 MiB/s
2001: 2025-07-05 15:00:47 INFO:   5% (16.0 GiB of 300.0 GiB) in 43s, read: 552.6 MiB/s, write: 344.9 MiB/s
2001: 2025-07-05 15:00:54 INFO:   6% (18.1 GiB of 300.0 GiB) in 50s, read: 311.8 MiB/s, write: 296.3 MiB/s
2001: 2025-07-05 15:01:05 INFO:   7% (21.0 GiB of 300.0 GiB) in 1m 1s, read: 268.2 MiB/s, write: 262.5 MiB/s
2001: 2025-07-05 15:01:15 INFO:   8% (24.3 GiB of 300.0 GiB) in 1m 11s, read: 334.6 MiB/s, write: 316.5 MiB/s
2001: 2025-07-05 15:01:22 INFO:   9% (29.8 GiB of 300.0 GiB) in 1m 18s, read: 813.0 MiB/s, write: 340.6 MiB/s
2001: 2025-07-05 15:01:25 INFO:  12% (38.4 GiB of 300.0 GiB) in 1m 21s, read: 2.8 GiB/s, write: 147.0 MiB/s
2001: 2025-07-05 15:01:28 INFO:  16% (50.6 GiB of 300.0 GiB) in 1m 24s, read: 4.1 GiB/s, write: 111.8 MiB/s
2001: 2025-07-05 15:01:31 INFO:  18% (55.2 GiB of 300.0 GiB) in 1m 27s, read: 1.6 GiB/s, write: 326.1 MiB/s
2001: 2025-07-05 15:01:34 INFO:  22% (66.9 GiB of 300.0 GiB) in 1m 30s, read: 3.9 GiB/s, write: 176.1 MiB/s
2001: 2025-07-05 15:01:37 INFO:  27% (82.4 GiB of 300.0 GiB) in 1m 33s, read: 5.2 GiB/s, write: 4.0 KiB/s
2001: 2025-07-05 15:01:40 INFO:  32% (97.4 GiB of 300.0 GiB) in 1m 36s, read: 5.0 GiB/s, write: 50.7 KiB/s
2001: 2025-07-05 15:01:43 INFO:  33% (100.5 GiB of 300.0 GiB) in 1m 39s, read: 1.0 GiB/s, write: 411.3 MiB/s
2001: 2025-07-05 15:01:47 INFO:  34% (102.0 GiB of 300.0 GiB) in 1m 43s, read: 377.3 MiB/s, write: 366.0 MiB/s
2001: 2025-07-05 15:01:51 INFO:  34% (102.8 GiB of 300.0 GiB) in 1m 47s, read: 214.4 MiB/s, write: 212.6 MiB/s
2001: 2025-07-05 15:01:51 ERROR: vma_queue_write: write error - Broken pipe
2001: 2025-07-05 15:01:51 INFO: aborting backup job
2001: 2025-07-05 15:01:51 INFO: resuming VM again
2001: 2025-07-05 15:01:52 ERROR: Backup of VM 2001 failed - vma_queue_write: write error - Broken pipe

2002: 2025-07-05 15:01:52 INFO: Starting Backup of VM 2002 (qemu)
2002: 2025-07-05 15:01:52 INFO: status = running
2002: 2025-07-05 15:01:52 INFO: VM Name: brisrv
2002: 2025-07-05 15:01:52 INFO: include disk 'scsi0' 'local-lvm:vm-2002-disk-0' 1200G
2002: 2025-07-05 15:01:52 INFO: include disk 'efidisk0' 'vms-vlm-thin:vm-2002-disk-0' 4M
2002: 2025-07-05 15:01:52 INFO: include disk 'tpmstate0' 'vms-vlm-thin:vm-2002-disk-1' 4M
2002: 2025-07-05 15:01:52 INFO: backup mode: snapshot
2002: 2025-07-05 15:01:52 INFO: ionice priority: 7
2002: 2025-07-05 15:01:52 INFO: creating vzdump archive '/var/lib/vz/dump/vzdump-qemu-2002-2025_07_05-15_01_52.vma.zst'
2002: 2025-07-05 15:01:52 INFO: attaching TPM drive to QEMU for backup
2002: 2025-07-05 15:01:52 INFO: issuing guest-agent 'fs-freeze' command
2002: 2025-07-05 15:01:54 INFO: issuing guest-agent 'fs-thaw' command
2002: 2025-07-05 15:01:54 INFO: started backup task 'ec100ae4-2cca-4e99-8f1b-0ab7fb9f333a'
2002: 2025-07-05 15:01:54 INFO: resuming VM again
2002: 2025-07-05 15:01:57 INFO:   0% (1.4 GiB of 1.2 TiB) in 3s, read: 484.5 MiB/s, write: 441.0 MiB/s
2002: 2025-07-05 15:02:31 INFO:   1% (12.3 GiB of 1.2 TiB) in 37s, read: 328.3 MiB/s, write: 323.0 MiB/s
2002: 2025-07-05 15:02:56 INFO:   2% (24.2 GiB of 1.2 TiB) in 1m 2s, read: 485.6 MiB/s, write: 306.7 MiB/s
2002: 2025-07-05 15:03:20 INFO:   3% (42.6 GiB of 1.2 TiB) in 1m 26s, read: 787.6 MiB/s, write: 293.1 MiB/s
2002: 2025-07-05 15:03:23 INFO:   5% (60.4 GiB of 1.2 TiB) in 1m 29s, read: 5.9 GiB/s, write: 123.3 MiB/s
2002: 2025-07-05 15:03:26 INFO:   5% (66.7 GiB of 1.2 TiB) in 1m 32s, read: 2.1 GiB/s, write: 258.6 MiB/s
2002: 2025-07-05 15:03:26 ERROR: vma_queue_write: write error - Broken pipe
2002: 2025-07-05 15:03:26 INFO: aborting backup job
2002: 2025-07-05 15:03:26 INFO: resuming VM again
2002: 2025-07-05 15:03:27 ERROR: Backup of VM 2002 failed - vma_queue_write: write error - Broken pipe
 
you have no diskspace: /dev/mapper/pve-root 94G 82G 7.7G 92% /
on the destination: zst'/var/lib/vz/dump/vzdump-qemu-2002-2025_07_05-15_01_52.vma.zstzst'
 
Is there a way to change that backup destination? I'm assuming its creating that snapshot to that location and then sends to the NAS?

Would setting up a PBS eliminate this problem?
 
Please share your backup job config. It looks like you back up to local.
 
I definitely recommend PBS. Backups to it are faster and a lot more space efficient.
 
Impact said:
I definitely recommend PBS. Backups to it are faster and a lot more space efficient.
Click to expand...
PBS is certainly not bad. Beyond that, however, the real flaw lies in the default setting. This should force a choice rather than defaulting to "local".
 
You must log in or register to reply here.
Top Bottom