It is a sparse file i believe, by confirm that [root@server export-domain]# du -hs VM1.ova 20G VM1.ova <--- actual size on disk
[root@server export-domain]# ls -l VM1.ova -rw-------. 1 root root 179142214656 Jul 13 02:56 VM1.ova <--- real file size After backup on bareos, it shown 167GB is backed up After restore [root@server export-domain]# ls -l ../restored/VM1.ova -rw-------. 1 root root 177794008064 Jul 12 15:07 ../restored/VM1.ova [root@mgnt21 export-domain]# du ../restored/VM1.ova 166G ../restored/VM1.ova <--- reverted to full allocated file. On Friday, July 12, 2019 at 10:40:31 PM UTC+8, Spadajspadaj wrote: > 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/cb896b52-df36-421b-8372-ab67ff7791f0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
