On 15.07.2019 09:05, Andreas Rogge wrote:
[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.
The docs are misleading then.
"By turning on the *sparse* option, Bareos will specifically look for
empty space in the file, and any empty space will not be written to the
Volume, nor will it be restored."
(https://docs.bareos.org/Configuration/Director.html#fileset-resource )
--
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/e5388d64-8dca-1ef3-532a-cba9c5e390dc%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
