vzdump snapshot backup of .qcow2 never ending and still growing

KJH

New Member
Nov 3, 2009
8
0
1
Hello
I`ve got a problem with a snapshot backup of an 350GB qcow2 image to a local directory. The backup is without zipping.
The image contains a w2k3 R2 32 bit Windows Fileserver
The backup is after 12h still running (vmtar) and at about 660GB still growing?!?

Snapshot backups of cqow files <100GB function normally.

Anyone an idea or same problems with big image files

Thanks
 
I`ve killed the job to get these log-file:

Nov 05 18:00:04 INFO: Starting Backup of VM 111 (qemu)
Nov 05 18:00:05 INFO: running
Nov 05 18:00:05 INFO: status = running
Nov 05 18:00:05 INFO: backup mode: snapshot
Nov 05 18:00:05 INFO: bandwidth limit: 10240 KB/s
Nov 05 18:00:07 INFO: Logical volume "vzsnap-node2-0" created
Nov 05 18:00:07 INFO: creating archive '/mnt/node4backup/vzdump-qemu-111-2009_11_05-18_00_04.tar'
Nov 05 18:00:08 INFO: adding '/mnt/node4backup/vzdump-qemu-111-2009_11_05-18_00_04.tmp/qemu-server.conf' to archive ('qemu-server.conf')
Nov 05 18:00:08 INFO: adding '/mnt/vzsnap0/images/111/vm-111-disk-1.qcow2' to archive ('vm-disk-ide0.qcow2')
Nov 06 12:16:09 INFO: received signal - terminate process
Nov 06 12:16:31 INFO: archive file size: 642.18GB
Nov 06 12:16:36 INFO: Logical volume "vzsnap-node2-0" successfully removed
Nov 06 12:16:37 INFO: Finished Backup of VM 111 (18:16:33)

---------------
The filesize of the KVM image is about 140GB
 
The filesize of the KVM image is about 140GB

I need access to that qcow2 file (a copy) in order to debug that. Please contact me directly (dietmar@proxmox.com) if that is possible.

If not, maybe you can setup a test image similar to the one you have and try to reproduce the bug. Then give me a access to that test image.
 
Have you mounted a NFS oder SAMBA Share insinde the VE?

I had this previously where a 15GB container wrote 32GB compressed backup and kept growing... until i realized that it was backing up the VE *and* the Share.