Am 13.07.19 um 08:19 schrieb levindecaro: > 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 That is correct. Even if bytes have been skipped on backup still the whole size of the file is recorded.
> 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. That's also correct. Bareos does not punch holes in files during restore. The problem is the logic for sparse files: Bareos does detect contiguous streams of zeroes, but it doesn't check whether the region was sparse or not (I'm not aware of a portable way to do so right now). So we don't know what regions of a backed up file are sparse and therefore cannot punch the correct holes into the file during restore. Sorry. Best Regards, Andreas -- Andreas Rogge [email protected] Bareos GmbH & Co. KG Phone: +49 221-630693-86 http://www.bareos.com Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 Komplementär: Bareos Verwaltungs-GmbH Geschäftsführer: S. Dühr, M. Außendorf, J. Steffens, Philipp Storz -- 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/9d244afd-8800-2f2f-8149-d449b885aaad%40bareos.com. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature
