Are you sure the OVA file is a sparse one? AFAIR, thin provisioning
means that the file size should sum up to already provisioned chunks of
data.
In other words, if inside the virtual machine you use 4G and have a 4G
file even though the maximum disk size is 30G you'd have a 4G file. But
it wouldn't be a sparse file.
If it were a sparse file, the filesystem would report a file size of 30G
but with only 4G of actual contents.
I hope I'm not making this overly confusing :-)
On 12.07.2019 09:56, levindecaro wrote:
Hi,
I'm using bareos 18.2, to backup bunch of ova files exported from
RHEV, the ova file size is the actual used size of the image after
export(thin image). However bareos still allocate the real size of
image during backup or restore. The sparse=yes options seems cannot
handle ova files.
Anyone has experience to workaround that?
Thank you!
--
You received this message because you are subscribed to the Google Groups
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to bareos-users+unsubscr...@googlegroups.com.
To post to this group, send email to bareos-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/bareos-users/af423b5f-64bf-fb47-2a5c-f56ecb8d02b9%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
