Since 4 weeks it starts again with failing backups.

ednt

Active Member
Mar 16, 2017
95
7
28
Hi,

for a long time I got always some failing backups from Prxmox clustr to the PBS.
I also reported this long time ago.
Then, 3 month ago, after somenew updates it worked like charm.
Now, since arround 3 or 4 weeks, again after some updates, it starts to fail on many machines.
Here is one error report:

Code:
2022-06-30T01:38:53+02:00: starting new backup on datastore 'backup-41': "vm/1025701/2022-06-29T23:38:49Z"
2022-06-30T01:38:53+02:00: download 'index.json.blob' from previous backup.
2022-06-30T01:38:58+02:00: register chunks in 'drive-virtio0.img.fidx' from previous backup.
2022-06-30T01:38:58+02:00: download 'drive-virtio0.img.fidx' from previous backup.
2022-06-30T01:39:31+02:00: created new fixed index 1 ("vm/1025701/2022-06-29T23:38:49Z/drive-virtio0.img.fidx")
2022-06-30T01:40:04+02:00: register chunks in 'drive-virtio1.img.fidx' from previous backup.
2022-06-30T01:40:04+02:00: download 'drive-virtio1.img.fidx' from previous backup.
2022-06-30T01:40:05+02:00: created new fixed index 2 ("vm/1025701/2022-06-29T23:38:49Z/drive-virtio1.img.fidx")
2022-06-30T01:40:34+02:00: register chunks in 'drive-virtio2.img.fidx' from previous backup.
2022-06-30T01:40:34+02:00: download 'drive-virtio2.img.fidx' from previous backup.
2022-06-30T01:40:58+02:00: created new fixed index 3 ("vm/1025701/2022-06-29T23:38:49Z/drive-virtio2.img.fidx")
2022-06-30T01:41:31+02:00: register chunks in 'drive-virtio3.img.fidx' from previous backup.
2022-06-30T01:41:31+02:00: download 'drive-virtio3.img.fidx' from previous backup.
2022-06-30T01:43:12+02:00: created new fixed index 4 ("vm/1025701/2022-06-29T23:38:49Z/drive-virtio3.img.fidx")
2022-06-30T01:43:46+02:00: register chunks in 'drive-virtio4.img.fidx' from previous backup.
2022-06-30T01:43:46+02:00: download 'drive-virtio4.img.fidx' from previous backup.
2022-06-30T01:43:47+02:00: created new fixed index 5 ("vm/1025701/2022-06-29T23:38:49Z/drive-virtio4.img.fidx")
2022-06-30T01:44:20+02:00: register chunks in 'drive-virtio5.img.fidx' from previous backup.
2022-06-30T01:44:20+02:00: download 'drive-virtio5.img.fidx' from previous backup.
2022-06-30T01:44:21+02:00: created new fixed index 6 ("vm/1025701/2022-06-29T23:38:49Z/drive-virtio5.img.fidx")
2022-06-30T01:44:54+02:00: add blob "/mnt/datastore/data-1/backup-41/vm/1025701/2022-06-29T23:38:49Z/qemu-server.conf.blob" (497 bytes, comp: 497)
2022-06-30T01:44:54+02:00: add blob "/mnt/datastore/data-1/backup-41/vm/1025701/2022-06-29T23:38:49Z/fw.conf.blob" (103 bytes, comp: 103)
2022-06-30T01:44:54+02:00: backup ended and finish failed: backup ended but finished flag is not set.
2022-06-30T01:44:54+02:00: removing unfinished backup
2022-06-30T01:44:54+02:00: TASK ERROR: backup ended but finished flag is not set.

Any idea?
 

ednt

Active Member
Mar 16, 2017
95
7
28
Here is a shorter error message of an other VM:
Code:
2022-06-30T01:31:40+02:00: starting new backup on datastore 'backup-41': "vm/1135/2022-06-29T23:31:21Z"
2022-06-30T01:31:40+02:00: download 'index.json.blob' from previous backup.
2022-06-30T01:35:41+02:00: register chunks in 'drive-virtio1.img.fidx' from previous backup.
2022-06-30T01:35:41+02:00: download 'drive-virtio1.img.fidx' from previous backup.
2022-06-30T01:35:41+02:00: created new fixed index 1 ("vm/1135/2022-06-29T23:31:21Z/drive-virtio1.img.fidx")
2022-06-30T01:36:13+02:00: add blob "/mnt/datastore/data-1/backup-41/vm/1135/2022-06-29T23:31:21Z/qemu-server.conf.blob" (539 bytes, comp: 539)
2022-06-30T01:36:14+02:00: backup ended and finish failed: backup ended but finished flag is not set.
2022-06-30T01:36:14+02:00: removing unfinished backup
2022-06-30T01:36:14+02:00: TASK ERROR: backup ended but finished flag is not set.
 

itNGO

Well-Known Member
Jun 12, 2020
550
118
48
44
Germany
it-ngo.com
And on what Version are you on?
 

dcsapak

Proxmox Staff Member
Staff member
Feb 1, 2016
8,221
1,044
164
34
Vienna
also what does the client log say?
 

ednt

Active Member
Mar 16, 2017
95
7
28
Backup Server 2.2-3
latest version from pbs-no-subscription

Client cluster 7.1-11
I can not update at the moment, because I can not transfer or shutdown some LXCs on the cluster.

Clientside:

Code:
()
INFO: starting new backup job: vzdump 102 104 105 106 107 108 110 303 304 208 130 131 210 134 135 136 215 129 139 137 138 209 221 101 111 112 114 115 117 118 122 123 126 133 103 119 128 1214 146 100 145 101841 101451 100021 100822 121 200001 100111 1025702 1025701 152 153 151 150 149 148 147 101352 101351 102361 127 101354 109 1135 1134 157 116 211 212 206 102132 102721 100503 159 158 155 169 165 170 --storage pk-pbs-02 --compress zstd --mode snapshot --mailto edv@ednt.de --quiet 1 --mailnotification always
INFO: skip external VMs: 100, 102, 103, 104, 105, 106, 107, 109, 110, 111, 112, 114, 115, 116, 117, 118, 119, 121, 122, 123, 126, 128, 129, 130, 131, 133, 134, 135, 138, 139, 145, 147, 148, 149, 150, 151, 152, 153, 155, 158, 159, 165, 169, 170, 206, 208, 209, 210, 211, 212, 215, 221, 303, 304, 1134, 1214, 100021, 100111, 100503, 100822, 101351, 101352, 101354, 101451, 101841, 102132, 102361, 102721, 200001, 1025701, 1025702
INFO: Starting Backup of VM 101 (qemu)
INFO: Backup started at 2022-06-30 01:00:05
INFO: status = stopped
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: VM Name: RZEDNT-MAILGW-1
INFO: include disk 'sata0' 'hdd-1:vm-101-disk-0' 80G
INFO: creating Proxmox Backup Server archive 'vm/101/2022-06-29T23:00:05Z'
INFO: starting kvm to execute backup task
INFO: started backup task 'a0e19928-8d5c-46ea-8b47-1d685eaff0c8'
INFO: sata0: dirty-bitmap status: created new
INFO:   0% (800.0 MiB of 80.0 GiB) in 3s, read: 266.7 MiB/s, write: 0 B/s
INFO:   1% (1.6 GiB of 80.0 GiB) in 6s, read: 264.0 MiB/s, write: 0 B/s
INFO:   2% (2.3 GiB of 80.0 GiB) in 9s, read: 254.7 MiB/s, write: 0 B/s
INFO:   3% (3.0 GiB of 80.0 GiB) in 12s, read: 253.3 MiB/s, write: 0 B/s
INFO:   4% (3.8 GiB of 80.0 GiB) in 15s, read: 258.7 MiB/s, write: 0 B/s
INFO:   6% (5.3 GiB of 80.0 GiB) in 18s, read: 514.7 MiB/s, write: 0 B/s
INFO:   8% (6.8 GiB of 80.0 GiB) in 21s, read: 496.0 MiB/s, write: 0 B/s
INFO:  11% (9.1 GiB of 80.0 GiB) in 24s, read: 805.3 MiB/s, write: 0 B/s
INFO:  14% (11.4 GiB of 80.0 GiB) in 27s, read: 774.7 MiB/s, write: 0 B/s
INFO:  17% (13.7 GiB of 80.0 GiB) in 30s, read: 788.0 MiB/s, write: 0 B/s
INFO:  19% (15.5 GiB of 80.0 GiB) in 33s, read: 628.0 MiB/s, write: 0 B/s
INFO:  21% (17.5 GiB of 80.0 GiB) in 36s, read: 665.3 MiB/s, write: 0 B/s
INFO:  23% (18.7 GiB of 80.0 GiB) in 39s, read: 400.0 MiB/s, write: 0 B/s
INFO:  24% (19.4 GiB of 80.0 GiB) in 42s, read: 250.7 MiB/s, write: 0 B/s
INFO:  25% (20.8 GiB of 80.0 GiB) in 45s, read: 470.7 MiB/s, write: 0 B/s
INFO:  28% (23.0 GiB of 80.0 GiB) in 48s, read: 758.7 MiB/s, write: 0 B/s
INFO:  31% (25.1 GiB of 80.0 GiB) in 51s, read: 706.7 MiB/s, write: 0 B/s
INFO:  33% (27.1 GiB of 80.0 GiB) in 54s, read: 708.0 MiB/s, write: 0 B/s
INFO:  36% (29.1 GiB of 80.0 GiB) in 57s, read: 657.3 MiB/s, write: 0 B/s
INFO:  37% (30.4 GiB of 80.0 GiB) in 1m, read: 452.0 MiB/s, write: 0 B/s
INFO:  40% (32.5 GiB of 80.0 GiB) in 1m 3s, read: 734.7 MiB/s, write: 0 B/s
INFO:  43% (34.6 GiB of 80.0 GiB) in 1m 6s, read: 705.3 MiB/s, write: 0 B/s
INFO:  45% (36.8 GiB of 80.0 GiB) in 1m 9s, read: 742.7 MiB/s, write: 0 B/s
INFO:  48% (38.5 GiB of 80.0 GiB) in 1m 12s, read: 592.0 MiB/s, write: 0 B/s
INFO:  51% (40.8 GiB of 80.0 GiB) in 1m 15s, read: 789.3 MiB/s, write: 0 B/s
INFO:  53% (43.2 GiB of 80.0 GiB) in 1m 18s, read: 802.7 MiB/s, write: 0 B/s
INFO:  55% (44.5 GiB of 80.0 GiB) in 1m 21s, read: 458.7 MiB/s, write: 0 B/s
INFO:  56% (45.2 GiB of 80.0 GiB) in 1m 24s, read: 229.3 MiB/s, write: 0 B/s
INFO:  57% (46.1 GiB of 80.0 GiB) in 1m 27s, read: 301.3 MiB/s, write: 0 B/s
INFO:  58% (46.7 GiB of 80.0 GiB) in 1m 30s, read: 210.7 MiB/s, write: 0 B/s
INFO:  59% (47.5 GiB of 80.0 GiB) in 1m 34s, read: 195.0 MiB/s, write: 0 B/s
INFO:  60% (48.2 GiB of 80.0 GiB) in 1m 37s, read: 260.0 MiB/s, write: 0 B/s
INFO:  61% (49.1 GiB of 80.0 GiB) in 1m 40s, read: 290.7 MiB/s, write: 0 B/s
INFO:  62% (49.9 GiB of 80.0 GiB) in 1m 43s, read: 270.7 MiB/s, write: 0 B/s
INFO:  63% (50.7 GiB of 80.0 GiB) in 1m 46s, read: 277.3 MiB/s, write: 0 B/s
INFO:  64% (51.4 GiB of 80.0 GiB) in 1m 49s, read: 249.3 MiB/s, write: 0 B/s
INFO:  65% (52.3 GiB of 80.0 GiB) in 1m 52s, read: 289.3 MiB/s, write: 0 B/s
INFO:  66% (53.1 GiB of 80.0 GiB) in 1m 55s, read: 290.7 MiB/s, write: 0 B/s
INFO:  67% (53.9 GiB of 80.0 GiB) in 1m 58s, read: 260.0 MiB/s, write: 0 B/s
INFO:  68% (54.8 GiB of 80.0 GiB) in 2m 1s, read: 302.7 MiB/s, write: 0 B/s
INFO:  69% (55.6 GiB of 80.0 GiB) in 2m 4s, read: 281.3 MiB/s, write: 0 B/s
INFO:  70% (56.3 GiB of 80.0 GiB) in 2m 7s, read: 249.3 MiB/s, write: 0 B/s
INFO:  71% (57.1 GiB of 80.0 GiB) in 2m 10s, read: 285.3 MiB/s, write: 0 B/s
INFO:  72% (57.9 GiB of 80.0 GiB) in 2m 13s, read: 254.7 MiB/s, write: 0 B/s
INFO:  73% (58.6 GiB of 80.0 GiB) in 2m 16s, read: 252.0 MiB/s, write: 0 B/s
INFO:  74% (59.5 GiB of 80.0 GiB) in 2m 19s, read: 284.0 MiB/s, write: 0 B/s
INFO:  75% (60.4 GiB of 80.0 GiB) in 2m 22s, read: 302.7 MiB/s, write: 0 B/s
INFO:  76% (61.2 GiB of 80.0 GiB) in 2m 25s, read: 297.3 MiB/s, write: 0 B/s
INFO:  77% (62.0 GiB of 80.0 GiB) in 2m 28s, read: 249.3 MiB/s, write: 0 B/s
INFO:  78% (62.7 GiB of 80.0 GiB) in 2m 31s, read: 260.0 MiB/s, write: 0 B/s
INFO:  79% (63.3 GiB of 80.0 GiB) in 2m 34s, read: 190.7 MiB/s, write: 0 B/s
INFO:  80% (64.1 GiB of 80.0 GiB) in 2m 37s, read: 292.0 MiB/s, write: 0 B/s
INFO:  81% (65.0 GiB of 80.0 GiB) in 2m 40s, read: 284.0 MiB/s, write: 0 B/s
INFO:  82% (65.7 GiB of 80.0 GiB) in 2m 43s, read: 264.0 MiB/s, write: 0 B/s
INFO:  83% (66.5 GiB of 80.0 GiB) in 2m 46s, read: 249.3 MiB/s, write: 0 B/s
INFO:  84% (67.4 GiB of 80.0 GiB) in 2m 50s, read: 237.0 MiB/s, write: 0 B/s
INFO:  85% (68.2 GiB of 80.0 GiB) in 2m 53s, read: 260.0 MiB/s, write: 0 B/s
INFO:  86% (68.9 GiB of 80.0 GiB) in 2m 56s, read: 269.3 MiB/s, write: 0 B/s
INFO:  87% (69.7 GiB of 80.0 GiB) in 2m 59s, read: 269.3 MiB/s, write: 0 B/s
INFO:  88% (70.5 GiB of 80.0 GiB) in 3m 2s, read: 277.3 MiB/s, write: 0 B/s
INFO:  89% (71.3 GiB of 80.0 GiB) in 3m 5s, read: 244.0 MiB/s, write: 0 B/s
INFO:  90% (72.0 GiB of 80.0 GiB) in 3m 8s, read: 262.7 MiB/s, write: 0 B/s
INFO:  91% (72.9 GiB of 80.0 GiB) in 3m 11s, read: 297.3 MiB/s, write: 0 B/s
INFO:  94% (75.2 GiB of 80.0 GiB) in 3m 14s, read: 802.7 MiB/s, write: 0 B/s
INFO:  95% (76.7 GiB of 80.0 GiB) in 3m 17s, read: 498.7 MiB/s, write: 0 B/s
INFO:  98% (78.6 GiB of 80.0 GiB) in 3m 20s, read: 645.3 MiB/s, write: 0 B/s
INFO: 100% (80.0 GiB of 80.0 GiB) in 3m 23s, read: 477.3 MiB/s, write: 0 B/s
INFO: Waiting for server to finish backup validation...
INFO: backup is sparse: 46.67 GiB (58%) total zero data
INFO: backup was done incrementally, reused 80.00 GiB (100%)
INFO: transferred 80.00 GiB in 204 seconds (401.6 MiB/s)
INFO: stopping kvm after backup task
INFO: Finished Backup of VM 101 (00:03:34)
INFO: Backup finished at 2022-06-30 01:03:39
INFO: Starting Backup of VM 108 (qemu)
INFO: Backup started at 2022-06-30 01:03:41
INFO: status = running
INFO: VM Name: pk-pmg-01
INFO: include disk 'scsi0' 'hdd-1:vm-108-disk-0' 32G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating Proxmox Backup Server archive 'vm/108/2022-06-29T23:03:41Z'
ERROR: VM 108 qmp command 'backup' failed - got timeout
INFO: aborting backup job
INFO: resuming VM again
ERROR: Backup of VM 108 failed - VM 108 qmp command 'backup' failed - got timeout
INFO: Failed at 2022-06-30 01:06:06
INFO: Starting Backup of VM 127 (qemu)
INFO: Backup started at 2022-06-30 01:06:06
INFO: status = running
INFO: VM Name: webhosting-postgresql
INFO: include disk 'scsi0' 'hdd-1:vm-127-disk-0' 32G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating Proxmox Backup Server archive 'vm/127/2022-06-29T23:06:06Z'
INFO: started backup task '5edd8c12-8185-4218-b909-f929ca4a6487'
INFO: resuming VM again
INFO: scsi0: dirty-bitmap status: OK (244.0 MiB of 32.0 GiB dirty)
INFO: using fast incremental mode (dirty-bitmap), 244.0 MiB dirty of 32.0 GiB total
INFO: 100% (244.0 MiB of 244.0 MiB) in 3s, read: 81.3 MiB/s, write: 70.7 MiB/s
INFO: backup was done incrementally, reused 31.79 GiB (99%)
INFO: transferred 244.00 MiB in 30 seconds (8.1 MiB/s)
INFO: Finished Backup of VM 127 (00:01:22)
INFO: Backup finished at 2022-06-30 01:07:28
INFO: Starting Backup of VM 136 (qemu)
INFO: Backup started at 2022-06-30 01:07:28
INFO: status = running
INFO: VM Name: LIC001-10000
INFO: include disk 'virtio0' 'hdd-1:vm-136-disk-1' 300G
INFO: include disk 'virtio1' 'hdd-1:vm-136-disk-0' 100G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating Proxmox Backup Server archive 'vm/136/2022-06-29T23:07:28Z'
INFO: issuing guest-agent 'fs-freeze' command
INFO: issuing guest-agent 'fs-thaw' command
ERROR: VM 136 qmp command 'backup' failed - got timeout
INFO: aborting backup job
INFO: resuming VM again
ERROR: Backup of VM 136 failed - VM 136 qmp command 'backup' failed - got timeout
INFO: Failed at 2022-06-30 01:10:04
INFO: Starting Backup of VM 137 (qemu)
INFO: Backup started at 2022-06-30 01:10:04
INFO: status = running
INFO: VM Name: GW001-10000
INFO: include disk 'virtio1' 'hdd-1:vm-137-disk-0' 100G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating Proxmox Backup Server archive 'vm/137/2022-06-29T23:10:04Z'
INFO: issuing guest-agent 'fs-freeze' command
INFO: issuing guest-agent 'fs-thaw' command
ERROR: VM 137 qmp command 'backup' failed - got timeout
INFO: aborting backup job
INFO: resuming VM again
ERROR: Backup of VM 137 failed - VM 137 qmp command 'backup' failed - got timeout
INFO: Failed at 2022-06-30 01:13:53
INFO: Starting Backup of VM 146 (qemu)
INFO: Backup started at 2022-06-30 01:13:53
INFO: status = running
INFO: VM Name: webhosting.ednt.eu
INFO: include disk 'scsi0' 'hdd-1:vm-146-disk-0' 32G
INFO: include disk 'scsi1' 'hdd-1:vm-146-disk-1' 500G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: snapshots found (not included into backup)
INFO: creating Proxmox Backup Server archive 'vm/146/2022-06-29T23:13:53Z'
INFO: started backup task '026b2d9d-62e6-4ac9-8d0f-d239d4cd00a1'
INFO: resuming VM again
INFO: scsi0: dirty-bitmap status: OK (1.3 GiB of 32.0 GiB dirty)
INFO: scsi1: dirty-bitmap status: OK (388.0 MiB of 500.0 GiB dirty)
INFO: using fast incremental mode (dirty-bitmap), 1.7 GiB dirty of 532.0 GiB total
INFO:  22% (396.0 MiB of 1.7 GiB) in 3s, read: 132.0 MiB/s, write: 130.7 MiB/s
INFO:  26% (460.0 MiB of 1.7 GiB) in 17s, read: 4.6 MiB/s, write: 4.3 MiB/s
INFO:  31% (548.0 MiB of 1.7 GiB) in 21s, read: 22.0 MiB/s, write: 21.0 MiB/s
INFO:  38% (660.0 MiB of 1.7 GiB) in 29s, read: 14.0 MiB/s, write: 14.0 MiB/s
INFO:  40% (696.0 MiB of 1.7 GiB) in 41s, read: 3.0 MiB/s, write: 2.7 MiB/s
INFO:  42% (740.0 MiB of 1.7 GiB) in 44s, read: 14.7 MiB/s, write: 14.7 MiB/s
INFO:  45% (788.0 MiB of 1.7 GiB) in 52s, read: 6.0 MiB/s, write: 6.0 MiB/s
INFO:  46% (812.0 MiB of 1.7 GiB) in 55s, read: 8.0 MiB/s, write: 8.0 MiB/s
INFO:  51% (888.0 MiB of 1.7 GiB) in 1m, read: 15.2 MiB/s, write: 15.2 MiB/s
INFO:  52% (908.0 MiB of 1.7 GiB) in 1m 3s, read: 6.7 MiB/s, write: 6.7 MiB/s
INFO:  53% (916.0 MiB of 1.7 GiB) in 1m 8s, read: 1.6 MiB/s, write: 1.6 MiB/s
INFO:  59% (1020.0 MiB of 1.7 GiB) in 1m 11s, read: 34.7 MiB/s, write: 34.7 MiB/s
INFO:  63% (1.1 GiB of 1.7 GiB) in 1m 28s, read: 4.9 MiB/s, write: 4.9 MiB/s
INFO:  66% (1.1 GiB of 1.7 GiB) in 1m 31s, read: 17.3 MiB/s, write: 17.3 MiB/s
INFO:  68% (1.2 GiB of 1.7 GiB) in 1m 40s, read: 2.7 MiB/s, write: 2.7 MiB/s
INFO:  72% (1.2 GiB of 1.7 GiB) in 1m 43s, read: 25.3 MiB/s, write: 25.3 MiB/s
INFO:  73% (1.2 GiB of 1.7 GiB) in 1m 51s, read: 1.5 MiB/s, write: 1.5 MiB/s
INFO:  75% (1.3 GiB of 1.7 GiB) in 1m 54s, read: 10.7 MiB/s, write: 6.7 MiB/s
INFO:  79% (1.3 GiB of 1.7 GiB) in 1m 57s, read: 25.3 MiB/s, write: 22.7 MiB/s
INFO:  81% (1.4 GiB of 1.7 GiB) in 2m 2s, read: 4.8 MiB/s, write: 3.2 MiB/s
INFO:  82% (1.4 GiB of 1.7 GiB) in 2m 5s, read: 9.3 MiB/s, write: 9.3 MiB/s
INFO:  84% (1.4 GiB of 1.7 GiB) in 2m 11s, read: 6.0 MiB/s, write: 5.3 MiB/s
INFO:  86% (1.5 GiB of 1.7 GiB) in 2m 14s, read: 8.0 MiB/s, write: 8.0 MiB/s
INFO:  90% (1.5 GiB of 1.7 GiB) in 2m 17s, read: 25.3 MiB/s, write: 24.0 MiB/s
INFO:  91% (1.6 GiB of 1.7 GiB) in 2m 21s, read: 6.0 MiB/s, write: 6.0 MiB/s
INFO:  93% (1.6 GiB of 1.7 GiB) in 2m 25s, read: 7.0 MiB/s, write: 5.0 MiB/s
INFO:  95% (1.6 GiB of 1.7 GiB) in 2m 28s, read: 13.3 MiB/s, write: 10.7 MiB/s
INFO:  97% (1.6 GiB of 1.7 GiB) in 2m 31s, read: 9.3 MiB/s, write: 9.3 MiB/s
INFO: 100% (1.7 GiB of 1.7 GiB) in 2m 34s, read: 14.7 MiB/s, write: 9.3 MiB/s
INFO: backup was done incrementally, reused 530.39 GiB (99%)
INFO: transferred 1.69 GiB in 195 seconds (8.9 MiB/s)
INFO: Finished Backup of VM 146 (00:04:55)
INFO: Backup finished at 2022-06-30 01:18:48
INFO: Starting Backup of VM 157 (qemu)
INFO: Backup started at 2022-06-30 01:18:53
INFO: status = running
INFO: VM Name: DC001-10145
INFO: include disk 'virtio0' 'hdd-1:vm-157-disk-0' 100G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating Proxmox Backup Server archive 'vm/157/2022-06-29T23:18:53Z'
INFO: skipping guest-agent 'fs-freeze', agent configured but not running?
ERROR: VM 157 qmp command 'backup' failed - got timeout
INFO: aborting backup job
ERROR: VM 157 qmp command 'backup-cancel' failed - got timeout
INFO: resuming VM again
ERROR: Backup of VM 157 failed - VM 157 qmp command 'backup' failed - got timeout
INFO: Failed at 2022-06-30 01:31:21
INFO: Starting Backup of VM 1135 (qemu)
INFO: Backup started at 2022-06-30 01:31:21
INFO: status = running
INFO: VM Name: DC002-10000
INFO: include disk 'virtio1' 'hdd-1:vm-1135-disk-0' 100G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating Proxmox Backup Server archive 'vm/1135/2022-06-29T23:31:21Z'
INFO: issuing guest-agent 'fs-freeze' command
INFO: issuing guest-agent 'fs-thaw' command
ERROR: VM 1135 qmp command 'backup' failed - got timeout
INFO: aborting backup job
INFO: resuming VM again
ERROR: Backup of VM 1135 failed - VM 1135 qmp command 'backup' failed - got timeout
INFO: Failed at 2022-06-30 01:36:13
INFO: Backup job finished with errors
TASK ERROR: job errors

Short version:

Code:
INFO: creating Proxmox Backup Server archive 'vm/1135/2022-06-29T23:31:21Z'
INFO: issuing guest-agent 'fs-freeze' command
INFO: issuing guest-agent 'fs-thaw' command
ERROR: VM 1135 qmp command 'backup' failed - got timeout
INFO: aborting backup job
INFO: resuming VM again
ERROR: Backup of VM 1135 failed - VM 1135 qmp command 'backup' failed - got timeout

But it is connected via a 10G and most of the backups are working.

Also a ping does not report any lost packages.
 
Last edited:

dcsapak

Proxmox Staff Member
Staff member
Feb 1, 2016
8,221
1,044
164
34
Vienna
that issue is probably fixed by an pve update though...
 
  • Like
Reactions: itNGO

itNGO

Well-Known Member
Jun 12, 2020
550
118
48
44
Germany
it-ngo.com
Hi,

we've an similar problem

Could you precise this? Is there a patch available?

Bye

Gregor
I guess it will be in 7.2-5 or 7.2-7.... some more days to wait in Enterprise Repository...
 

grefabu

Active Member
May 23, 2018
201
10
38
48
I guess it will be in 7.2-5 or 7.2-7.... some more days to wait in Enterprise Repository...
sorry for request: Did you mean proxmox-ve or pve-manager?

proxmox-ve is now 7.2-1 in the community repository, pve-manager is already 7.2-7
Here I've installed pve-manager 7.2-3
 

itNGO

Well-Known Member
Jun 12, 2020
550
118
48
44
Germany
it-ngo.com
sorry for request: Did you mean proxmox-ve or pve-manager?

proxmox-ve is now 7.2-1 in the community repository, pve-manager is already 7.2-7
Here I've installed pve-manager 7.2-3
pve-manager... was just a guess... can also be that it will take until 7.2-8,9 or 7.3 until fix.... I just saw some commits the last days in Mailing-List that make me guess, there is happening something for that Problem....
 

grefabu

Active Member
May 23, 2018
201
10
38
48
For now I've no change of behavior, I've install yesterday the newest patches.

Maybe my setup is the problem. I'll made an own thread for this.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!