Backup problem

KonradP

New Member
Apr 15, 2021
3
0
1
38
Hi I have problem witch create vm backup log is below:
Code:
()
INFO: starting new backup job: vzdump 107 --storage FreeNas --remove 0 --node proxmox2 --mode snapshot --compress lzo
INFO: Starting Backup of VM 107 (qemu)
INFO: status = running
INFO: update VM 107: -lock backup
INFO: VM Name: SRV001
INFO: include disk 'virtio0' 'Data-Storage:vm-107-disk-1' 1T
INFO: include disk 'virtio1' 'Data-Storage:vm-107-disk-2' 1536G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating archive '/mnt/pve/FreeNas/dump/vzdump-qemu-107-2021_04_15-14_30_58.vma.lzo'
INFO: started backup task 'da92bcae-7194-48ee-9d2f-77301205be01'
INFO: status: 0% (544931840/2748779069440), sparse 0% (96985088), duration 3, read/write 181/149 MB/s
INFO: status: 0% (3486842880/2748779069440), sparse 0% (165613568), duration 26, read/write 127/124 MB/s
ERROR: job failed with err -5 - Input/output error
INFO: aborting backup job
ERROR: Backup of VM 107 failed - job failed with err -5 - Input/output error
INFO: Backup job finished with errors
TASK ERROR: job errors

Does anyone see what could be the reason

Thanks greetings
 
hi,

does the NAS work normally without problems, i.e. can you see files, delete/replace copy etc. without any problems?

is this the only VM with this problem, or also others?

does backup work normally when you select local storage?
 
Hi @oguz
Thanks for replay.

NAS work normally, besides I have another one from Qnap and its have similar error:

Code:
INFO: starting new backup job: vzdump 107 --compress lzo --storage Qnap --remove 0 --node proxmox2 --mode snapshot
INFO: Starting Backup of VM 107 (qemu)
INFO: status = running
INFO: update VM 107: -lock backup
INFO: VM Name: SRV001
INFO: include disk 'virtio0' 'Data-Storage:vm-107-disk-1' 1T
INFO: include disk 'virtio1' 'Data-Storage:vm-107-disk-2' 1536G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating archive '/mnt/samba/dump/vzdump-qemu-107-2021_04_16-07_31_29.vma.lzo'
INFO: started backup task '40c48e85-0613-4407-b200-85900be9ab39'
INFO: status: 0% (522780672/2748779069440), sparse 0% (96223232), duration 3, read/write 174/142 MB/s
INFO: status: 0% (3487170560/2748779069440), sparse 0% (165666816), duration 22, read/write 156/152 MB/s
ERROR: job failed with err -5 - Input/output error
INFO: aborting backup job
ERROR: Backup of VM 107 failed - job failed with err -5 - Input/output error
INFO: Backup job finished with errors
TASK ERROR: job errors

Problem occurs only on one VM, backup on other works good.

Code:
INFO: starting new backup job: vzdump 106 --compress lzo --node proxmox2 --storage FreeNas --remove 0 --mode snapshot
INFO: Starting Backup of VM 106 (qemu)
INFO: status = running
INFO: update VM 106: -lock backup
INFO: VM Name: HIL
INFO: include disk 'virtio0' 'Data-Storage:vm-106-disk-1' 130G
INFO: include disk 'virtio1' 'Data-Storage:vm-106-disk-2' 250G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating archive '/mnt/pve/FreeNas/dump/vzdump-qemu-106-2021_04_16-07_36_09.vma.lzo'
INFO: started backup task '9c6e93b9-1448-4da0-90bd-3dce7c1fd267'
INFO: status: 0% (370737152/408021893120), sparse 0% (111468544), duration 3, read/write 123/86 MB/s
INFO: status: 1% (4097572864/408021893120), sparse 0% (157016064), duration 67, read/write 58/57 MB/s
INFO: status: 2% (8219525120/408021893120), sparse 0% (203681792), duration 102, read/write 117/116 MB/s
INFO: status: 3% (12341673984/408021893120), sparse 0% (3635445760), duration 172, read/write 58/9 MB/s
INFO: status: 4% (16463167488/408021893120), sparse 1% (6146576384), duration 211, read/write 105/41 MB/s
.
.
.
.
.
.

On local storage backup this VM have similar error.

Thanks.
 
NAS work normally, besides I have another one from Qnap and its have similar error:
On local storage backup this VM have similar error.
then probably the issue is not related to the storage but to that specific VM.

i also see that the problematic VM has a much larger disk compared to the other one. do you have enough space to save this backup? maybe it's just running out of space.

otherwise it's also possible the VM disk is corrupted/damaged. you can check by running fsck or a similar tool in the VM to see if there are any filesystem errors