Quantcast
Channel: Proxmox Support Forum
Viewing all articles
Browse latest Browse all 170710

Backup 3x times bigger than VM content

$
0
0
Hi all,

There's an issue that I can't really understand.

We have one KVM VM (W2k3) with a disk of 32G in LVM. The used disk inside the VM is about 9G, and the backup make 23'5G.Who can understand this ?

We tried to move it to a /directory storage converting it to qcow2, to defrag the entire disk ...and always the same result: 23'5G.


Code:

INFO: starting new backup job: vzdump 312 --remove 0 --mode snapshot --compress lzo --storage backups_TMP --node hw01
INFO: Starting Backup of VM 312 (qemu)
INFO: status = stopped
INFO: update VM 312: -lock backup
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: creating archive '/backups/dump/vzdump-qemu-312-2013_12_19-00_11_29.vma.lzo'
INFO: starting kvm to execute backup task
INFO: started backup task 'e5146c78-b255-49cc-b4b7-11f26f2dfa6f'
INFO: status: 2% (830603264/34359738368), sparse 0% (59838464), duration 3, 276/256 MB/s
INFO: status: 4% (1620901888/34359738368), sparse 0% (68513792), duration 6, 263/260 MB/s
...
INFO: status: 96% (33205846016/34359738368), sparse 10% (3646115840), duration 129, 223/223 MB/s

INFO: status: 98% (34003812352/34359738368), sparse 10% (3646181376), duration 132, 265/265 MB/s
INFO: status: 100% (34359738368/34359738368), sparse 10% (3658600448), duration 134, 177/171 MB/s
INFO: transferred 34359 MB in 134 seconds (256 MB/s)
INFO: stopping kvm after backup task
INFO: archive file size: 23.52GB
INFO: Finished Backup of VM 312 (00:02:17)
INFO: Backup job finished successfully
TASK OK

And after trying almost everything, we tried to make a backup using gzip instead of LZO and almost the same, but this time backup needed 7x more time for a similar result:

Code:

INFO: starting new backup job: vzdump 312 --remove 0 --mode snapshot --compress gzip --storage backups_TMP --node hw01
INFO: Starting Backup of VM 312 (qemu)
INFO: status = running
INFO: update VM 312: -lock backup
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating archive '/backups/dump/vzdump-qemu-312-2013_12_19-00_50_59.vma.gz'
INFO: started backup task '38f5e637-c14d-44bc-a9c9-0f99bc8e4271'
INFO: status: 0% (106430464/34359738368), sparse 0% (446464), duration 3, 35/35 MB/s
INFO: status: 1% (368705536/34359738368), sparse 0% (55898112), duration 10, 37/29 MB/s
INFO: status: 2% (710803456/34359738368), sparse 0% (59432960), duration 22, 28/28 MB/s
INFO: status: 3% (1053229056/34359738368), sparse 0% (62881792), duration 34, 28/28 MB/s
...
INFO: status: 98% (33673248768/34359738368), sparse 10% (3645939712), duration 1047, 29/29 MB/s

INFO: status: 99% (34046345216/34359738368), sparse 10% (3646005248), duration 1059, 31/31 MB/s
INFO: status: 100% (34359738368/34359738368), sparse 10% (3658424320), duration 1071, 26/25 MB/s
INFO: status: 100% (34359738368/34359738368), sparse 10% (3658424320), duration 1072, 0/0 MB/s
INFO: transferred 34359 MB in 1072 seconds (32 MB/s)
INFO: archive file size: 22.03GB
INFO: Finished Backup of VM 312 (00:17:52)
INFO: Backup job finished successfully
TASK OK

We have a similar VM (same template) with same disk, OS, etc and the 14GBs used space makes a 9GBs backup. This means there's something weird with that VM disk.

Any ideas ? maybe this is normal ? A VM with 9GBs of total data generating backups of 24GBs ?

Thanks

Viewing all articles
Browse latest Browse all 170710

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>