Backup procedure for qemu VM do not work correct

nick

Active Member
Mar 28, 2007
364
1
38
HI all,

I change the disk's into a PVE server and after the clean install I migrate all machines, add the backup disk (same disk as in pervious installation) and start to configure the backup directories and cron jobs from webUI.

all backups for qemu machines do not complete. I attach an image from folder after backup procedure started...and never ended until now. The backup was for a 32GB Windows XP Pro SP3.

The configuration is:

pve-manager: 1.6-5 (pve-manager/1.6/5261)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.32: 1.6-25
pve-kernel-2.6.32-4-pve: 2.6.32-25
qemu-server: 1.1-22
pve-firmware: 1.0-9
libpve-storage-perl: 1.0-14
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-8
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.12.5-2
ksm-control-daemon: 1.0-4
Screen shot 2010-12-07 at 18.35.00.png
 
any log (/var/log/vzdump/...)? maybe the snapshot run out of space.
 
HI, this is the log for this machine:

Code:
Dec 07 02:00:06 INFO: Starting Backup of VM 114 (qemu)
Dec 07 02:00:06 INFO: running
Dec 07 02:00:06 INFO: status = running
Dec 07 02:00:08 INFO: backup mode: snapshot
Dec 07 02:00:08 INFO: ionice priority: 7
Dec 07 02:00:10 INFO:   Logical volume "vzsnap-proxmox_ve-0" created
Dec 07 02:00:12 INFO: creating archive '/backup/Antivirus/vzdump-qemu-114-2010_12_07-02_00_06.tgz'

This is another log from a SBS2008 64bit; as you can see after 4 days nothing happen. The procedure was stopped by restart

Code:
Dec 02 23:00:03 INFO: Starting Backup of VM 105 (qemu)
Dec 02 23:00:03 INFO: running
Dec 02 23:00:03 INFO: status = running
Dec 02 23:00:04 INFO: backup mode: snapshot
Dec 02 23:00:04 INFO: ionice priority: 7
Dec 02 23:00:05 INFO:   Logical volume "vzsnap-proxmox_ve-0" created
Dec 02 23:00:05 INFO: creating archive '/backup/SBS2008/vzdump-qemu-105-2010_12_02-23_00_03.tgz'
Dec 02 23:00:06 INFO: adding '/backup/SBS2008/vzdump-qemu-105-2010_12_02-23_00_03.tmp/qemu-server.conf' to archive ('qemu-server.conf')
Dec 02 23:00:06 INFO: adding '/mnt/vzsnap0/images/105/vm-105-disk-1.raw' to archive ('vm-disk-ide0.raw')
Dec 06 20:11:33 INFO:   Logical volume "vzsnap-proxmox_ve-0" successfully removed
Dec 06 20:11:40 ERROR: Backup of VM 105 failed - interrupted by signal

and another log for an openvz machine:

Code:
Dec 02 10:45:01 INFO: Starting Backup of VM 103 (openvz)
Dec 02 10:45:01 INFO: CTID 103 exist mounted running
Dec 02 10:45:01 INFO: status = CTID 103 exist mounted running
Dec 02 10:45:02 INFO: backup mode: snapshot
Dec 02 10:45:02 INFO: ionice priority: 7
Dec 02 10:45:02 INFO: creating lvm snapshot of /dev/mapper/pve-data ('/dev/pve/vzsnap-proxmox_ve-0')
Dec 02 10:45:03 INFO:   Logical volume "vzsnap-proxmox_ve-0" created
Dec 02 10:45:04 INFO: creating archive '/backup/NS/vzdump-openvz-103-2010_12_02-10_45_01.tgz'
Dec 02 10:46:14 INFO: Total bytes written: 307230720 (293MiB, 4.5MiB/s)
Dec 02 10:46:14 INFO: archive file size: 127MB
Dec 02 10:49:48 INFO:   Logical volume "vzsnap-proxmox_ve-0" successfully removed
Dec 02 10:49:48 INFO: Finished Backup of VM 103 (00:04:47)

maybe the snapshot run out of space.

the disk is not out of space. it's a 500GB disk and as you can see in previous attached image 85% of disk is free
 
Last edited:
I do not talk about the disk, I am talking about the snapshot logical volume (e.g. Logical volume "vzsnap-proxmox_ve-0" created).

Just take a look on the logical volume (lvdisplay) if you think its hanging, I assume its 100 % then.

do you have already a custom /etc/vzdump.conf file? if yes, post it.
 
do you have already a custom /etc/vzdump.conf file? if yes, post it.

I do not change anything on the config file. It's the default!

btw...I try to edit /etc/vzdump.conf and I don't have such file in this location!
 
I do not change anything on the config file. It's the default!

btw...I try to edit /etc/vzdump.conf and I don't have such file in this location!

there is no such file by default, but you can create it if you do not want the defaults (see man vzdump).

I suggest you try the following:

Code:
nano /etc/vzdump.conf
and enter just this line:

Code:
size: 3072
 
the disk is not out of space. it's a 500GB disk and as you can see in previous attached image 85% of disk is free

You need to check the free space inside the snapshot partition (lvs shows that during backup). Or simply try to increase the size of the snapshot by creating /etc/vzdump.conf and adding a line like:

size: 2048

see man vzdump for details.
 
OK, I create the file /etc/vzdump.conf, I add the line: size 3072 and last night I start a new backup on same machine.

I don't receive any answer from server and this is the log:

Code:
Dec 07 02:00:06 INFO: Starting Backup of VM 114 (qemu)
Dec 07 02:00:06 INFO: running
Dec 07 02:00:06 INFO: status = running
Dec 07 02:00:08 INFO: backup mode: snapshot
Dec 07 02:00:08 INFO: ionice priority: 7
Dec 07 02:00:10 INFO:   Logical volume "vzsnap-proxmox_ve-0" created
Dec 07 02:00:12 INFO: creating archive '/backup/Antivirus/vzdump-qemu-114-2010_12_07-02_00_06.tgz'

I need to stop first the previous unfinished backup process? If yes, how?
 
check the size of the lv - is it 100%?
 
see postings above - and make yourself familar with lvm
 
see postings above - and make yourself familar with lvm

sorry for my stupid question; see the attached image.lv.jpg

Code:
  LV Name                /dev/pve/vzsnap-proxmox_ve-0
  VG Name                pve
  LV UUID                Uw1n4J-u0hn-gf5t-fdbF-V91A-sZZx-YR4WYD
  LV Write Access        read/write
  LV snapshot status     INACTIVE destination for /dev/pve/data
  LV Status              available
  # open                 1
  LV Size                827.02 GB
  Current LE             211716
  COW-table size         1.00 GB
  COW-table LE           256
  Snapshot chunk size    4.00 KB
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           254:3
 
Last edited:
This is the output:

Code:
proxmox_ve:~# lvs
  LV                  VG   Attr   LSize   Origin Snap%  Move Log Copy%  Convert
  data                pve  owi-ao 827.02G
  root                pve  -wi-ao  96.00G
  swap                pve  -wi-ao   4.00G
  vzsnap-proxmox_ve-0 pve  Swi-Io   1.00G data   100.00
 
your snapshot size is still 1 GB, but you told that changed it to 3 GB via vzdump.conf?

seems you did not do this right, post the output of:

Code:
cat /etc/vzdump.conf
should be:
Code:
size: 3072
 
This is the output! I reboot the entire system and I come back with feedback!
 
note, the vzdump.conf file needs to be edited on the node where the VM is located.
 
Success! After I reboot the PVE server the backup process finish correct! In this night I will test the second backup for SBS 2008 64bit to see if this will success too!
 

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!