Backup failed

[silicom]

Hi,

I do a backup of all my VM every night. Recently, I've made an upgrade on all my proxmox nodes (3.2 to 3.3), and the backup worked well at the beginning but for a week I have errors on most of my nodes like :

command 'qm set 121 --lock backup' failed: exit code 107

and backup will not ending before I make the 'service pvecluster restart' command.

I know I can make a 'qm unlock 121' to solve this problem but it's not permanent. Somebody knows why I have these errors ?

Thanks you !

 

[dietmar]

try

# qm unlock 121

 

[silicom]

Thank you for your response.

This command works, but I have to do this every day. I didn't have to do that before.
Is it a problem with the update?

 

[tamatech]

Even that command does not work for me, as the backups always get hung up. I'm seeing the exact same problem - backups worked flawlessly in 3.2.

 

[tamatech]

OpenVZ containers still backing up OK, but the VMs appear to have lost their names in addition to failing the backup.

 

[dietmar]

This command works, but I have to do this every day. I didn't have to do that before.
Is it a problem with the update?

So your backup task hangs or produce an unexpected error - please check the backup logs.

 

[dietmar]

Even that command does not work for me, as the backups always get hung up.

Maybe one of your storages is offline? Unreliable NFS servers often produce such hangs.

 

[tamatech]

The OpenVZ containers and VMs are getting backed up to the same external storage location.

 

[silicom]

In the Proxmox interface, I see :

As you can see, the backup locks but doesn't stop in some nodes.

I've cheked the backup logs (qemu-xxx.log) and I don't understand the problem : sometimes, I don't have errors, like with Feta node :

Nov 05 00:20:17 INFO: Starting Backup of VM 121 (qemu)
Nov 05 00:20:17 INFO: status = running

or with Canut node :

Nov 05 01:39:30 INFO: status: 97% (208488562688/214748364800), sparse 12% (27207815168), duration 16765, 81/51 MB/s
Nov 05 01:39:42 INFO: status: 98% (210536300544/214748364800), sparse 13% (29026033664), duration 16777, 170/19 MB/s
Nov 05 01:39:44 INFO: status: 100% (214748364800/214748364800), sparse 15% (33238097920), duration 16779, 2106/0 MB/s
Nov 05 01:39:44 INFO: transferred 214748 MB in 16779 seconds (12 MB/s)
Nov 05 01:39:45 INFO: archive file size: 150.72GB
Nov 05 01:39:45 INFO: delete old backup '/mnt/pve/virt_nfs/dump/vzdump-qemu-118-2014_11_04-15_55_14.vma.lzo'

But the backup doesn't continue.

Sometimes I get errors (like in Arrouya node) :

ERROR: Backup of VM 160 failed - command 'qm set 160 --lock backup' failed: exit code 25
INFO: Backup job finished with errors
TASK ERROR: job errors

Thanks for your help !