VZDump/VMA fail on Template backups?

Jan 12, 2015
94
2
28
Why does 'vma' consistenly fail when backing up VM Templates? I have over 1T of space available in /var/lib/vz/dump so not sure what's going on here. Tried to find some documentation/man page but only find a basic blurb about it here https://pve.proxmox.com/wiki/VMA nothing about details for the cli arguments.

I have several Proxmox servers with this issue and it only seems to happend when 'template: 1' is set in the /etc/pve/nodes/$hostname/qemu-server/$vm.conf. The problem is that this process hangs and then none of my other VMs get dumped until I kill the vma process. This really messes up timing when running the dumps at night because I have to essentially have to continue backing-up during work hours causing performance issues.


This is how I started vmdump from cron. It started at 2AM and when I logged in at 7:30am vzdump was stitting there so I killed it with CTRL+C:
Code:
  vzdump $vm --dumpdir /var/lib/vz/dump/ --mailto root --compress lzo --mailnotification failure --ionice 3 --mode suspend --maxfiles 3

This is the vma error:
Code:
# cat /var/log/vzdump/qemu-100.log 
May 03 02:00:05 INFO: Starting Backup of VM 100 (qemu)
May 03 02:00:05 INFO: status = stopped
May 03 02:00:05 INFO: update VM 100: -lock backup
May 03 02:00:05 INFO: backup mode: stop
May 03 02:00:05 INFO: ionice priority: 3
May 03 02:00:07 INFO: creating archive '/var/lib/vz/dump/vzdump-qemu-100-2015_05_03-02_00_05.vma.lzo'
May 03 02:00:07 INFO: starting template backup
May 03 02:00:07 INFO: /usr/bin/vma create -v -c /var/lib/vz/dump/vzdump-qemu-100-2015_05_03-02_00_05.tmp/qemu-server.conf exec:lzop>/var/lib/vz/dump/vzdump-qemu-100-2015_05_03-02_00_05.vma.dat drive-virtio0=/var/lib/ssd/images/100/base-100-disk-1.qcow2
May 03 02:00:07 INFO: progress 0% 0/34359738368 0
May 03 02:00:10 INFO: progress 1% 343605248/34359738368 254586880
May 03 02:00:15 INFO: progress 2% 687210496/34359738368 307601408
May 03 02:00:19 INFO: progress 3% 1030815744/34359738368 449925120
May 03 02:00:19 INFO: progress 4% 1374420992/34359738368 775675904
May 03 02:00:20 INFO: progress 5% 1718026240/34359738368 1119272960
May 03 02:00:20 INFO: progress 6% 2061631488/34359738368 1462878208
May 03 02:00:20 INFO: progress 7% 2405236736/34359738368 1805918208
May 03 02:00:21 INFO: progress 8% 2748841984/34359738368 2149462016
May 03 02:00:21 INFO: progress 9% 3092381696/34359738368 2492985344
May 03 02:00:22 INFO: progress 10% 3435986944/34359738368 2836582400
May 03 02:00:22 INFO: progress 11% 3779592192/34359738368 3179868160
May 03 02:00:22 INFO: progress 12% 4123197440/34359738368 3523473408
May 03 02:00:23 INFO: progress 13% 4466802688/34359738368 3867078656
May 03 02:00:26 INFO: progress 14% 4810407936/34359738368 4044939264
May 03 02:00:32 INFO: progress 15% 5154013184/34359738368 4046434304
May 03 02:00:35 INFO: progress 16% 5497618432/34359738368 4241207296
May 03 02:00:35 INFO: progress 17% 5841158144/34359738368 4584738816
May 03 02:00:35 INFO: progress 18% 6184763392/34359738368 4928344064
May 03 02:00:36 INFO: progress 19% 6528368640/34359738368 5271949312
May 03 02:00:39 INFO: progress 20% 6871973888/34359738368 5433421824
May 03 02:00:45 INFO: progress 21% 7215579136/34359738368 5436542976
May 03 02:00:51 INFO: progress 22% 7559184384/34359738368 5438631936
May 04 07:50:45 ERROR: Backup of VM 100 failed - command '/usr/bin/vma create -v -c /var/lib/vz/dump/vzdump-qemu-100-2015_05_03-02_00_05.tmp/qemu-server.conf 'exec:lzop>/var/lib/vz/dump/vzdump-qemu-100-2015_05_03-02_00_05.vma.dat' 'drive-virtio0=/var/lib/ssd/images/100/base-100-disk-1.qcow2'' failed: interrupted by signal
 
Can you reproduce this issue with other/new templates? If so, please provide exact steps to reproduce the problem.
 
Can you reproduce this issue with other/new templates? If so, please provide exact steps to reproduce the problem.

Seems to be happening every night. I'll make a new template and see what happens tonight.I have two Proxmox servers which both back up the VMs just fine until they hit one or more template. Here is from last two days. One template was vmid 111 the other 115. The backup started on the 5th and I had to kill it this afternoon. Server #2 has templates with VMID 100 and 102. VMID 100 suceeded for some reason...:

(this is server #1 - two templates with VMIDs 111 and 115)
Code:
# cat /var/log/vzdump/qemu-115.log /var/log/vzdump/qemu-111.log
May 05 12:11:23 INFO: Starting Backup of VM 115 (qemu)
May 05 12:11:23 INFO: status = stopped
May 05 12:11:23 INFO: update VM 115: -lock backup
May 05 12:11:23 INFO: backup mode: stop
May 05 12:11:23 INFO: ionice priority: 3
May 05 12:11:23 INFO: creating archive '/var/lib/vz/dump/vzdump-qemu-115-2015_05_05-12_11_23.vma.lzo'
May 05 12:11:23 INFO: starting template backup
May 05 12:11:23 INFO: /usr/bin/vma create -v -c /var/lib/vz/dump/vzdump-qemu-115-2015_05_05-12_11_23.tmp/qemu-server.conf exec:lzop>/var/lib/vz/dump/vzdump-qemu-115-2015_05_05-12_11_23.vma.dat drive-virtio0=/var/lib/ssd/images/115/vm-115-disk-2.qcow2
May 05 12:11:23 INFO: progress 0% 0/10737418240 0
May 05 12:11:24 INFO: progress 1% 107413504/10737418240 34783232
...
May 05 12:11:48 INFO: progress 30% 3221225472/10737418240 434270208
May 06 14:27:25 ERROR: Backup of VM 115 failed - command '/usr/bin/vma create -v -c /var/lib/vz/dump/vzdump-qemu-115-2015_05_05-12_11_23.tmp/qemu-server.conf 'exec:lzop>/var/lib/vz/dump/vzdump-qemu-115-2015_05_05-12_11_23.vma.dat' 'drive-virtio0=/var/lib/ssd/images/115/vm-115-disk-2.qcow2'' failed: interrupted by signal
May 05 02:52:36 INFO: Starting Backup of VM 111 (qemu)
May 05 02:52:36 INFO: status = stopped
May 05 02:52:36 INFO: update VM 111: -lock backup
May 05 02:52:36 INFO: backup mode: stop
May 05 02:52:36 INFO: ionice priority: 3
May 05 02:52:36 INFO: creating archive '/var/lib/vz/dump/vzdump-qemu-111-2015_05_05-02_52_36.vma.lzo'
May 05 02:52:36 INFO: starting template backup
May 05 02:52:36 INFO: /usr/bin/vma create -v -c /var/lib/vz/dump/vzdump-qemu-111-2015_05_05-02_52_36.tmp/qemu-server.conf exec:lzop>/var/lib/vz/dump/vzdump-qemu-111-2015_05_05-02_52_36.vma.dat drive-ide0=/var/lib/ssd/images/111/vm-111-disk-2.qcow2
May 05 02:52:36 INFO: progress 0% 0/42949672960 0
May 05 02:52:39 INFO: progress 1% 429522944/42949672960 106233856
...
May 05 02:53:45 INFO: progress 46% 19756875776/42949672960 12319559680
May 05 02:53:46 INFO: progress 47% 20186398720/42949672960 12749082624
May 05 12:01:39 ERROR: Backup of VM 111 failed - command '/usr/bin/vma create -v -c /var/lib/vz/dump/vzdump-qemu-111-2015_05_05-02_52_36.tmp/qemu-server.conf 'exec:lzop>/var/lib/vz/dump/vzdump-qemu-111-2015_05_05-02_52_36.vma.dat' 'drive-ide0=/var/lib/ssd/images/111/vm-111-disk-2.qcow2'' failed: interrupted by signal

(server #2)
#cat /var/log/vzdump/qemu-100.log /var/log/vzdump/qemu-102.log
Code:
May 06 02:00:06 INFO: Starting Backup of VM 100 (qemu)
May 06 02:00:06 INFO: status = stopped
May 06 02:00:06 INFO: update VM 100: -lock backup
May 06 02:00:06 INFO: backup mode: stop
May 06 02:00:06 INFO: ionice priority: 3
May 06 02:00:07 INFO: creating archive '/var/lib/vz/dump/vzdump-qemu-100-2015_05_06-02_00_06.vma.lzo'
May 06 02:00:07 INFO: starting template backup
May 06 02:00:07 INFO: /usr/bin/vma create -v -c /var/lib/vz/dump/vzdump-qemu-100-2015_05_06-02_00_06.tmp/qemu-server.conf exec:lzop>/var/lib/vz/dump/vzdump-qemu-100-2015_05_06-02_00_06.vma.dat drive-virtio0=/var/lib/ssd/images/100/base-100-disk-1.qcow2
May 06 02:00:08 INFO: progress 0% 0/34359738368 0
May 06 02:00:11 INFO: progress 1% 343605248/34359738368 254586880
...
May 06 02:01:43 INFO: progress 100% 34359738368/34359738368 31432732672
May 06 02:01:43 INFO: image drive-virtio0: size=34359738368 zeros=31432732672 saved=2927005696
May 06 02:01:43 INFO: archive file size: 1.24GB
May 06 02:01:43 INFO: delete old backup '/var/lib/vz/dump/vzdump-qemu-100-2015_05_01-02_00_05.vma.lzo'
May 06 02:01:46 INFO: Finished Backup of VM 100 (00:01:40)
May 06 02:01:48 INFO: Starting Backup of VM 102 (qemu)
May 06 02:01:48 INFO: status = stopped
May 06 02:01:48 INFO: update VM 102: -lock backup
May 06 02:01:48 INFO: backup mode: stop
May 06 02:01:48 INFO: ionice priority: 3
May 06 02:01:48 INFO: creating archive '/var/lib/vz/dump/vzdump-qemu-102-2015_05_06-02_01_48.vma.lzo'
May 06 02:01:48 INFO: starting template backup
May 06 02:01:48 INFO: /usr/bin/vma create -v -c /var/lib/vz/dump/vzdump-qemu-102-2015_05_06-02_01_48.tmp/qemu-server.conf exec:lzop>/var/lib/vz/dump/vzdump-qemu-102-2015_05_06-02_01_48.vma.dat drive-virtio0=/var/lib/ssd/images/102/base-102-disk-1.qcow2
May 06 02:01:48 INFO: progress 0% 0/34359738368 0
May 06 02:01:52 INFO: progress 1% 343605248/34359738368 254586880
...
May 06 02:03:09 INFO: progress 50% 17179869184/34359738368 14254788608
May 06 15:07:28 ERROR: Backup of VM 102 failed - command '/usr/bin/vma create -v -c /var/lib/vz/dump/vzdump-qemu-102-2015_05_06-02_01_48.tmp/qemu-server.conf 'exec:lzop>/var/lib/vz/dump/vzdump-qemu-102-2015_05_06-02_01_48.vma.dat' 'drive-virtio0=/var/lib/ssd/images/102/base-102-disk-1.qcow2'' failed: interrupted by signal
 

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 yours easily in our online shop.

Buy now!