Its taking 2-3 hours per VM to backup on my setup, where each vm has roughtly 15-20 GB of data (producing on average a 9-12 GB backup file).
I'm guessing its because the disks are over provisioned - 300GB and 512GB, but they are sparse qcow2 files, only occupying the actual data size.
Whats worse, while the backup is going on, the network is being hammered at 60M, pressumably transferring lots of Zeros.
I though backup handled sparse files intelligently? this sort of behaviour renders it useless. If I migrate the rest of our VM's backup time will blow out to over 24 hours.
The Disks are so large because I used windows bare metal backup to transfer them them, I can probably resize most of them, but thats tricky under windows and we still need a large safety factor for growth.
Can qcow2 files be converted to thinly provisioned?
NB: GB Enternet, Dual nics on each node and the NAS. Not bonded. VM's are stored on a NFS share on the NAS.
I'm guessing its because the disks are over provisioned - 300GB and 512GB, but they are sparse qcow2 files, only occupying the actual data size.
Whats worse, while the backup is going on, the network is being hammered at 60M, pressumably transferring lots of Zeros.
I though backup handled sparse files intelligently? this sort of behaviour renders it useless. If I migrate the rest of our VM's backup time will blow out to over 24 hours.
The Disks are so large because I used windows bare metal backup to transfer them them, I can probably resize most of them, but thats tricky under windows and we still need a large safety factor for growth.
Can qcow2 files be converted to thinly provisioned?
NB: GB Enternet, Dual nics on each node and the NAS. Not bonded. VM's are stored on a NFS share on the NAS.