Uses the entire disk when backing up

thenewworldbd

New Member
Dec 1, 2021
2
0
1
25
Hello. My English is not very good, but I can only find help here.
INFO: starting new backup job: vzdump 100 --remove 0 --compress lzo --storage Backup --mode snapshot --node Prometey
INFO: Starting Backup of VM 100 (qemu)
INFO: Backup started at 2022-01-13 00:37:04
INFO: status = stopped
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: include disk 'sata0' 'SSD:vm-100-disk-0' 447G
INFO: include disk 'sata1' 'local-lvm:vm-100-disk-0' 300G
INFO: creating vzdump archive '/var/lib/backup//dump/vzdump-qemu-100-2022_01_13-00_37_04.vma.lzo'
INFO: starting kvm to execute backup task
INFO: started backup task 'c15a2782-146d-43dd-901a-6eafbe482f31'
In fact, I have ~ 300 GB of information, but it starts to take all 700 GB, and it takes a very long time to backup.

INFO: 95% (709.9 GiB of 747.0 GiB) in 1h 6m 24s, read: 408.3 MiB/s, write: 404.9 MiB/s
INFO: 96% (717.1 GiB of 747.0 GiB) in 1h 7m 2s, read: 194.6 MiB/s, write: 194.6 MiB/s
INFO: 97% (724.6 GiB of 747.0 GiB) in 1h 8m 4s, read: 123.2 MiB/s, write: 123.2 MiB/s
INFO: 98% (732.2 GiB of 747.0 GiB) in 1h 9m 1s, read: 136.4 MiB/s, write: 136.3 MiB/s
lzop: No space left on device: <stdout>
INFO: 98% (733.1 GiB of 747.0 GiB) in 1h 9m 6s, read: 192.1 MiB/s, write: 192.1 MiB/s
ERROR: vma_queue_write: write error - Broken pipe
INFO: aborting backup job
INFO: stopping kvm after backup task
trying to acquire lock...
OK
ERROR: Backup of VM 100 failed - vma_queue_write: write error - Broken pipe
INFO: Failed at 2022-01-13 01:46:23
INFO: Backup job finished with errors
TASK ERROR: job errors
I have a second server, the settings are the same. In fact, 50 GB of information.

INFO: status: 95% (959433146368/1009317314560), sparse 69% (700281434112), duration 8729, read/write 2497/0 MB/s
INFO: status: 96% (971159371776/1009317314560), sparse 70% (712007659520), duration 8733, read/write 2931/0 MB/s
INFO: status: 97% (979510165504/1009317314560), sparse 71% (720358453248), duration 8736, read/write 2783/0 MB/s
INFO: status: 98% (989498179584/1009317314560), sparse 72% (730346467328), duration 8740, read/write 2497/0 MB/s
INFO: status: 99% (999869775872/1009317314560), sparse 73% (740718063616), duration 8744, read/write 2592/0 MB/s
INFO: status: 100% (1009317314560/1009317314560), sparse 74% (750165598208), duration 8748, read/write 2361/0 MB/s
INFO: transferred 1009317 MB in 8748 seconds (115 MB/s)
INFO: archive file size: 52.41GB
INFO: delete old backup '/var/lib/backup//dump/vzdump-qemu-100-2022_01_07-14_30_01.vma.zst'
INFO: Finished Backup of VM 100 (02:25:53)
INFO: Backup finished at 2022-01-12 16:55:55
INFO: Backup job finished successfully
TASK OK
Tell me how can I fix it? I'm new to this and I need help.
 

t.lamprecht

Proxmox Staff Member
Staff member
Jul 28, 2015
5,339
1,644
164
South Tyrol/Italy
shop.proxmox.com
Hi,
In fact, I have ~ 300 GB of information, but it starts to take all 700 GB, and it takes a very long time to backup.
Your backup log shows that you have two disks, one with 447 GB space and one with 300 GB space. In sum that's 747 GB raw space:
INFO: include disk 'sata0' 'SSD:vm-100-disk-0' 447G
INFO: include disk 'sata1' 'local-lvm:vm-100-disk-0' 300G
If one of those disks is left-over, or if it is not used anymore, you could just remove it (please triple check to avoid data loss!).

If you need both disks for the VM to run but do not need both disks to be backed up, you can edit the disk in the GUI so that it's not included in the backup.

You could also try using zstd or gzip for compression, those two can often compress data a bit more.
 

thenewworldbd

New Member
Dec 1, 2021
2
0
1
25
Hi,

Your backup log shows that you have two disks, one with 447 GB space and one with 300 GB space. In sum that's 747 GB raw space:

If one of those disks is left-over, or if it is not used anymore, you could just remove it (please triple check to avoid data loss!).

If you need both disks for the VM to run but do not need both disks to be backed up, you can edit the disk in the GUI so that it's not included in the backup.

You could also try using zstd or gzip for compression, those two can often compress data a bit more.
Thanks for the information. May I ask one more question?
Now on version 7.2 restore is done for a very long time. (289gb backup). 289 GB recovered 7 hours, on version 6.2 recovered 2-3 hours. What could I be missing?
 

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 your own in 60 seconds.

Buy now!