[SOLVED] Backup job finished with errors

Quickly · May 19, 2022

Hallo Zusammen.
Ich habe hier einen PVE 6.4.13 der auf einen PBS sichern soll.
Immer bei der einen Maschine, immer bei 37% wird abgebrochen. Irgendwelche Vorschläge?

# Auszug

Code:

INFO:  37% (165.8 GiB of 448.0 GiB) in 7h 10m 13s, read: 5.2 MiB/s, write: 5.2 MiB/s
INFO:  37% (165.8 GiB of 448.0 GiB) in 7h 10m 29s, read: 3.0 MiB/s, write: 3.0 MiB/s
ERROR: backup write data failed: command error: protocol canceled

# Gesamt

Code:

()
INFO: starting new backup job: vzdump 251 201 104 --quiet 1 --storage MyPBSBackupServer --mailnotification failure --mailto server1@MyDomain.de --mode snapshot
INFO: Starting Backup of VM 104 (qemu)
INFO: Backup started at 2022-05-18 20:30:02
INFO: status = running
INFO: VM Name: win2012dc1.MyDom.lan
INFO: include disk 'scsi0' 'vz-array01:104/vm-104-disk-0.raw' 160G
INFO: include disk 'scsi1' 'vz-array01:104/vm-104-disk-1.raw' 288G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating Proxmox Backup Server archive 'vm/104/2022-05-18T18:30:02Z'
INFO: issuing guest-agent 'fs-freeze' command
INFO: enabling encryption
INFO: issuing guest-agent 'fs-thaw' command
INFO: started backup task '3bf53d68-edd3-464b-b68b-b7d76b571ff0'
INFO: resuming VM again
INFO: scsi0: dirty-bitmap status: existing bitmap was invalid and has been cleared
INFO: scsi1: dirty-bitmap status: existing bitmap was invalid and has been cleared
INFO:   0% (160.0 MiB of 448.0 GiB) in 3s, read: 53.3 MiB/s, write: 49.3 MiB/s
INFO:   1% (4.5 GiB of 448.0 GiB) in 13m 55s, read: 5.3 MiB/s, write: 5.3 MiB/s
INFO:   2% (9.0 GiB of 448.0 GiB) in 29m 52s, read: 4.8 MiB/s, write: 4.8 MiB/s
INFO:   3% (13.4 GiB of 448.0 GiB) in 40m 51s, read: 7.0 MiB/s, write: 7.0 MiB/s
INFO:   4% (17.9 GiB of 448.0 GiB) in 51m 36s, read: 7.1 MiB/s, write: 7.1 MiB/s
INFO:   5% (22.4 GiB of 448.0 GiB) in 1h 2m 8s, read: 7.3 MiB/s, write: 7.3 MiB/s
INFO:   6% (26.9 GiB of 448.0 GiB) in 1h 14m 14s, read: 6.3 MiB/s, write: 6.3 MiB/s
INFO:   7% (31.4 GiB of 448.0 GiB) in 1h 23m 37s, read: 8.2 MiB/s, write: 8.2 MiB/s
INFO:   8% (35.8 GiB of 448.0 GiB) in 1h 39m 3s, read: 4.9 MiB/s, write: 4.9 MiB/s
INFO:   9% (40.3 GiB of 448.0 GiB) in 1h 50m 8s, read: 6.9 MiB/s, write: 6.9 MiB/s
INFO:  10% (44.8 GiB of 448.0 GiB) in 1h 58m 54s, read: 8.7 MiB/s, write: 8.7 MiB/s
INFO:  11% (49.3 GiB of 448.0 GiB) in 2h 8m 11s, read: 8.2 MiB/s, write: 8.2 MiB/s
INFO:  12% (53.8 GiB of 448.0 GiB) in 2h 17m 39s, read: 8.1 MiB/s, write: 8.1 MiB/s
INFO:  13% (58.3 GiB of 448.0 GiB) in 2h 27m 56s, read: 7.5 MiB/s, write: 7.5 MiB/s
INFO:  14% (62.7 GiB of 448.0 GiB) in 2h 39m 19s, read: 6.7 MiB/s, write: 6.7 MiB/s
INFO:  15% (67.2 GiB of 448.0 GiB) in 2h 53m 1s, read: 5.6 MiB/s, write: 5.6 MiB/s
INFO:  16% (71.7 GiB of 448.0 GiB) in 3h 1m 42s, read: 8.8 MiB/s, write: 8.8 MiB/s
INFO:  17% (76.2 GiB of 448.0 GiB) in 3h 9m 41s, read: 9.6 MiB/s, write: 9.6 MiB/s
INFO:  18% (80.6 GiB of 448.0 GiB) in 3h 21m 36s, read: 6.4 MiB/s, write: 6.4 MiB/s
INFO:  19% (85.1 GiB of 448.0 GiB) in 3h 30m 40s, read: 8.4 MiB/s, write: 8.4 MiB/s
INFO:  20% (89.6 GiB of 448.0 GiB) in 3h 40m 49s, read: 7.5 MiB/s, write: 7.5 MiB/s
INFO:  21% (94.1 GiB of 448.0 GiB) in 3h 51m 23s, read: 7.2 MiB/s, write: 7.2 MiB/s
INFO:  22% (98.6 GiB of 448.0 GiB) in 4h 23s, read: 8.5 MiB/s, write: 8.5 MiB/s
INFO:  23% (103.1 GiB of 448.0 GiB) in 4h 11m 1s, read: 7.2 MiB/s, write: 7.2 MiB/s
INFO:  24% (107.5 GiB of 448.0 GiB) in 4h 20m 20s, read: 8.2 MiB/s, write: 8.2 MiB/s
INFO:  25% (112.0 GiB of 448.0 GiB) in 4h 35m 10s, read: 5.1 MiB/s, write: 5.1 MiB/s
INFO:  26% (116.5 GiB of 448.0 GiB) in 4h 51m 45s, read: 4.6 MiB/s, write: 4.6 MiB/s
INFO:  27% (121.0 GiB of 448.0 GiB) in 5h 6m 24s, read: 5.2 MiB/s, write: 5.2 MiB/s
INFO:  28% (125.4 GiB of 448.0 GiB) in 5h 22m 56s, read: 4.6 MiB/s, write: 4.6 MiB/s
INFO:  29% (129.9 GiB of 448.0 GiB) in 5h 33m 58s, read: 6.9 MiB/s, write: 6.9 MiB/s
INFO:  30% (134.4 GiB of 448.0 GiB) in 5h 50m 59s, read: 4.5 MiB/s, write: 4.5 MiB/s
INFO:  31% (138.9 GiB of 448.0 GiB) in 6h 2m 25s, read: 6.7 MiB/s, write: 6.7 MiB/s
INFO:  32% (143.4 GiB of 448.0 GiB) in 6h 12m 2s, read: 7.9 MiB/s, write: 7.9 MiB/s
INFO:  33% (147.9 GiB of 448.0 GiB) in 6h 20m 5s, read: 9.6 MiB/s, write: 9.6 MiB/s
INFO:  34% (152.3 GiB of 448.0 GiB) in 6h 26m 48s, read: 11.3 MiB/s, write: 11.3 MiB/s
INFO:  35% (156.8 GiB of 448.0 GiB) in 6h 40m 50s, read: 5.5 MiB/s, write: 5.5 MiB/s
INFO:  36% (161.3 GiB of 448.0 GiB) in 6h 55m 26s, read: 5.2 MiB/s, write: 5.2 MiB/s
INFO:  37% (165.8 GiB of 448.0 GiB) in 7h 10m 13s, read: 5.2 MiB/s, write: 5.2 MiB/s
INFO:  37% (165.8 GiB of 448.0 GiB) in 7h 10m 29s, read: 3.0 MiB/s, write: 3.0 MiB/s
ERROR: backup write data failed: command error: protocol canceled
INFO: aborting backup job
INFO: resuming VM again
ERROR: Backup of VM 104 failed - backup write data failed: command error: protocol canceled
INFO: Failed at 2022-05-19 03:40:57
INFO: Starting Backup of VM 201 (qemu)
INFO: Backup started at 2022-05-19 03:40:57
INFO: status = running
INFO: VM Name: iptam01.MyDom.lan
INFO: include disk 'scsi0' 'vz-array01:201/vm-201-disk-0.qcow2' 32G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating Proxmox Backup Server archive 'vm/201/2022-05-19T01:40:57Z'
INFO: enabling encryption
INFO: started backup task '7f74f3ee-6dbb-4d70-b163-69d595f222f8'
INFO: resuming VM again
INFO: scsi0: dirty-bitmap status: OK (240.0 MiB of 32.0 GiB dirty)
INFO: using fast incremental mode (dirty-bitmap), 240.0 MiB dirty of 32.0 GiB total
INFO:  81% (196.0 MiB of 240.0 MiB) in 3s, read: 65.3 MiB/s, write: 64.0 MiB/s
INFO: 100% (240.0 MiB of 240.0 MiB) in 6s, read: 14.7 MiB/s, write: 14.7 MiB/s
INFO: backup was done incrementally, reused 31.77 GiB (99%)
INFO: transferred 240.00 MiB in 7 seconds (34.3 MiB/s)
INFO: Finished Backup of VM 201 (00:00:08)
INFO: Backup finished at 2022-05-19 03:41:05
Result: {
  "data": null
}
INFO: Starting Backup of VM 251 (qemu)
INFO: Backup started at 2022-05-19 03:41:05
INFO: status = running
INFO: VM Name: unifi01.MyDom.lan
INFO: include disk 'scsi0' 'vz-array01:251/vm-251-disk-0.qcow2' 32G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating Proxmox Backup Server archive 'vm/251/2022-05-19T01:41:05Z'
INFO: enabling encryption
INFO: started backup task '530b9825-19a4-40d8-830a-1a34ba9cdc86'
INFO: resuming VM again
INFO: scsi0: dirty-bitmap status: OK (768.0 MiB of 32.0 GiB dirty)
INFO: using fast incremental mode (dirty-bitmap), 768.0 MiB dirty of 32.0 GiB total
INFO:  13% (100.0 MiB of 768.0 MiB) in 3s, read: 33.3 MiB/s, write: 33.3 MiB/s
INFO:  15% (116.0 MiB of 768.0 MiB) in 6s, read: 5.3 MiB/s, write: 5.3 MiB/s
INFO:  18% (144.0 MiB of 768.0 MiB) in 9s, read: 9.3 MiB/s, write: 9.3 MiB/s
INFO:  22% (172.0 MiB of 768.0 MiB) in 12s, read: 9.3 MiB/s, write: 9.3 MiB/s
INFO:  31% (244.0 MiB of 768.0 MiB) in 15s, read: 24.0 MiB/s, write: 24.0 MiB/s
INFO:  39% (300.0 MiB of 768.0 MiB) in 18s, read: 18.7 MiB/s, write: 18.7 MiB/s
INFO:  42% (328.0 MiB of 768.0 MiB) in 21s, read: 9.3 MiB/s, write: 9.3 MiB/s
INFO:  48% (372.0 MiB of 768.0 MiB) in 24s, read: 14.7 MiB/s, write: 14.7 MiB/s
INFO:  53% (412.0 MiB of 768.0 MiB) in 27s, read: 13.3 MiB/s, write: 12.0 MiB/s
INFO:  59% (456.0 MiB of 768.0 MiB) in 30s, read: 14.7 MiB/s, write: 13.3 MiB/s
INFO:  67% (516.0 MiB of 768.0 MiB) in 33s, read: 20.0 MiB/s, write: 17.3 MiB/s
INFO:  71% (552.0 MiB of 768.0 MiB) in 36s, read: 12.0 MiB/s, write: 12.0 MiB/s
INFO:  83% (640.0 MiB of 768.0 MiB) in 39s, read: 29.3 MiB/s, write: 25.3 MiB/s
INFO: 100% (768.0 MiB of 768.0 MiB) in 42s, read: 42.7 MiB/s, write: 42.7 MiB/s
INFO: backup was done incrementally, reused 31.28 GiB (97%)
INFO: transferred 768.00 MiB in 45 seconds (17.1 MiB/s)
INFO: Finished Backup of VM 251 (00:00:45)
INFO: Backup finished at 2022-05-19 03:41:50
Result: {
  "data": null
}
INFO: Backup job finished with errors

TASK ERROR: job errors

dcsapak · May 19, 2022

ist irgendein(e) proxy/firewall dazwischen die vielleicht ins http2 protokoll eingreift?
der fehler sollte nur auftreten wenn die http2 verbindung abbricht oder ein problem hat

Quickly · May 19, 2022

dcsapak said:
ist irgendein(e) proxy/firewall dazwischen die vielleicht ins http2 protokoll eingreift?
der fehler sollte nur auftreten wenn die http2 verbindung abbricht oder ein problem hat

Hmmm...
Ja, ipFire mit transparentem Proxy ist dazwischen. Jedoch auch bei 7 anderen ProxMox mit identischen Einstellungen, Leitungen und ISP.
Das "sollte" es eigentlich nicht sein.
Ich werde zur Sicherheit mal den ISP fragen ob es Leitungsabbrüche gegeben hat.

Was mich halt wundert ist, dass es dann mit den weiteren Maschinen (VM201 + VM251) einfach weiter geht.
Und auch das wirklich immer (in den letzten 5 Tagen) bei 37% der Abbruch war.

Noch Vorschläge? Würde mich freuen.

Quickly · May 20, 2022

Quickly said:
Noch Vorschläge? Würde mich freuen.

Hmpf... ärgerlich.

ISP-Tarif war mal Privatkunde mit entsprechendem Tarif und Zwangstrennung.
ISP dann umgestellt auf GK ohne Zwangsttrennung
Leider wurde das Leistungsmerkmal vergessen... also war Zwangstrennung noch aktiv.
Erledigt und siehe da... das Backup läuft durch.

Sorry und Danke!

Search

Search

[SOLVED] Backup job finished with errors

Quickly

Well-Known Member

dcsapak

Proxmox Staff Member

Quickly

Well-Known Member

Quickly

Well-Known Member