On 16.07.2019 08:30, Andreas Rogge wrote:
"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
)Sorry.
> "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 )Sorry.
> My bad.
The docs is correct.
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
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 <---
The question that comes to mint is "how sparse is the sparse file". I
know it sounds a bit strange but the bareos sparcity logic, as I see in
the docs is that it checks whether a 32k block is made entirely of
zeros. So if your sparse file doesn't have continuous 32k blocks
(properly aligned I
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
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
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.
