Proxmox 2.1 backup process error...

[andrea68]

Hi,

I have a simple environment with proxmox 2.1 on a Dell and 3 VM running on it.
I Have a qnap storage connected to proxmox in iSCSI for backup the VM every week.

I notice that latest 2 backup give an unexpected error and in my task log i see an old backup tak that seems to be unfinished or appended (see image file)...

In ssh i see a tar process that occupy almost 100% of processor.

How can i solve this?

Thanks.

 

[tom]

pls give more details. our backup does not support iSCSI as target, so what are you doing exactly?

 

[andrea68]

pls give more details. our backup does not support iSCSI as target, so what are you doing exactly?

I'm sorry, my mistake: you're right, the qnap share via NFS a portion of storage for backup.

I try to stop the backup that seems to be "appended" via task manager and now i try to backup manually the VM's.
I also see via top that tar process no longer appear in top processes.

Thanks for now...

Ps.
I do not have a professional support.

 

[tom]

you can double click the task - this will show more info.

 

[andrea68]

you can double click the task - this will show more info.

I follow your instructions and i see in error backup task:

INFO: trying to get global lock - waiting...
ERROR: can't aquire lock '/var/run/vzdump.lock' - got timeout


Looking back to the first error on backup task i found this:


INFO: starting new backup job: vzdump 101 102 104 --quiet 1 --mailto supporto@xxxxx.it --mode snapshot --compress lzo --storage QNAP --node proxmox
INFO: Starting Backup of VM 101 (qemu)
INFO: status = running
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: Logical volume "vzsnap-proxmox-0" created
INFO: creating archive '/mnt/pve/QNAP/dump/vzdump-qemu-101-2012_05_26-01_00_01.tar.lzo'
INFO: adding '/mnt/pve/QNAP/dump/vzdump-qemu-101-2012_05_26-01_00_01.tmp/qemu-server.conf' to archive ('qemu-server.conf')
INFO: adding '/mnt/vzsnap0/images/101/vm-101-disk-1.raw' to archive ('vm-disk-ide0.raw')
INFO: Total bytes written: 214748367360 (90.14 MiB/s)
INFO: archive file size: 24.77GB
INFO: delete old backup '/mnt/pve/QNAP/dump/vzdump-qemu-101-2012_05_19-01_00_01.tar.lzo'
INFO: Finished Backup of VM 101 (00:46:31)
INFO: Starting Backup of VM 102 (qemu)
INFO: status = running
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: Logical volume "vzsnap-proxmox-0" created
INFO: creating archive '/mnt/pve/QNAP/dump/vzdump-qemu-102-2012_05_26-01_46_32.tar.lzo'
INFO: adding '/mnt/pve/QNAP/dump/vzdump-qemu-102-2012_05_26-01_46_32.tmp/qemu-server.conf' to archive ('qemu-server.conf')
INFO: adding '/mnt/vzsnap0/images/102/vm-102-disk-1.raw' to archive ('vm-disk-ide0.raw')
INFO: Total bytes written: 214748367360 (53.82 MiB/s)
INFO: archive file size: 45.23GB
INFO: delete old backup '/mnt/pve/QNAP/dump/vzdump-qemu-102-2012_05_19-01_33_18.tar.lzo'
INFO: Finished Backup of VM 102 (01:12:44)
INFO: Starting Backup of VM 104 (qemu)
INFO: status = running
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: Logical volume "vzsnap-proxmox-0" created
INFO: creating archive '/mnt/pve/QNAP/dump/vzdump-qemu-104-2012_05_26-02_59_16.tar.lzo'
INFO: adding '/mnt/pve/QNAP/dump/vzdump-qemu-104-2012_05_26-02_59_16.tmp/qemu-server.conf' to archive ('qemu-server.conf')
INFO: adding '/mnt/vzsnap0/images/104/vm-104-disk-1.raw' to archive ('vm-disk-ide0.raw')
ERROR: Backup of VM 104 failed - command '/usr/lib/qemu-server/vmtar '/mnt/pve/QNAP/dump/vzdump-qemu-104-2012_05_26-02_59_16.tmp/qemu-server.conf' 'qemu-server.conf' '/mnt/vzsnap0/images/104/vm-104-disk-1.raw' 'vm-disk-ide0.raw'|lzop >/mnt/pve/QNAP/dump/vzdump-qemu-104-2012_05_26-02_59_16.tar.dat' failed: interrupted by signal
INFO: Backup job finished with errors
TASK ERROR: job errors

 

[andrea68]

you can double click the task - this will show more info.

Hi,

I realize that when this backup stall and one of three VM's stall too and i must to reboot manually from terminal...

I have 3 VM on this task backup: it's 3 linux centos 5.x, one of these with plesk.
This VM with plesk it's the one with problems...

How can I debug this situation?

Thanks...

 

[andrea68]

Anyone?

Thanks...