Hi Radosław, I had another run this night with the "sparse = yes"
option turned on, but it doesn't seem to have solved the issue; backup
size is still 145G.
My configuration is as follows, do you see anything suspicious?
Thanks,
Alberto
JobDefs {
Name = "DefaultJob"
Type = Backup
Level = Incremental
Schedule = "WeeklyCycle"
Storage = File
Messages = Standard
Pool = File
Write Bootstrap = "/var/lib/bacula/%c.bsr"
Accurate = yes
}
Job {
Name = "BackupMailserver"
JobDefs = "DefaultJob"
FileSet="FileServer"
ClientRunBeforeJob = "/etc/init.d/zimbra stop"
ClientRunAfterJob = "/etc/init.d/zimbra start"
Priority = 20
Client = mail-fd
}
FileSet {
Name = "FileServer"
Include {
Options {
signature = SHA1
sparse = yes
}
File = /etc
File = /opt
File = /root
}
}
---
Alberto Caporro
Director of Security Services - Consulthink Srl
Via dell'Archivio di Stato, 15
00144 Rome, Italy
http://www.consulthink.it
M. +39 335 1217 394
F. +39 06 4549 2454
GPG key fingerprint
46B5 2D38 2D48 3EFA 5C12 B86B 157D 80BA 2EAD DF41
On 4 Apr 2013, at 10:40, Alberto Caporro wrote:
> Bingo! You saved my day, I'd never have thought of this :-)
>
> I have a very large (80G) sparse file in the /opt directory, I'm going
> to take advantage of the "sparse = yes" feature.
>
> Thanks again,
> Alberto
>
>
> ---
> Alberto Caporro
> Director of Security Services - Consulthink Srl
> Via dell'Archivio di Stato, 15
> 00144 Rome, Italy
> http://www.consulthink.it
> M. +39 335 1217 394
> F. +39 06 4549 2454
>
> GPG key fingerprint
> 46B5 2D38 2D48 3EFA 5C12 B86B 157D 80BA 2EAD DF41
> On 4 Apr 2013, at 10:20, Radosław Korzeniewski wrote:
>
>> Hello,
>>
>> 2013/4/4 Alberto Caporro <a.capo...@consulthink.it>
>>
>>> Hi everybody,
>>>
>>> I've just completed a Bacula deployment within our infrastructure
>>> and run
>>> through the first backups; while all of them have completed without
>>> any
>>> error, one of the jobs gave results that I find puzzling.
>>>
>>> I backed up our mail server, which is hosted in a virtual machine
>>> with two
>>> virtual disks sized at 20G and 200G respectively. I'm only backing
>>> up
>>> relevant files (/etc, /root and /opt) and measured on the server
>>> itself,
>>> the total size amounts to slightly more than 56G.
>>>
>>> The backup job ends with a total size of 145G, which is clearly
>>> wrong; the
>>> total number of backed up files is however correct, standing at
>>> 400k+.
>>>
>>> Check what files were backuped with "list files jobid=xx" bconsole
>>> command
>> and compare it with list of expected files. It is very plausible that
>> you
>> have more files on backup then expected. In this case you have to
>> tune your
>> FileSet definition.
>>
>> Another case could be a sparse files. If you have a very large sparse
>> file
>> (or files) i.e. 10GB file which allocated only a few MB on disk then
>> Bacula
>> will backup 10GB instead of a few MB. To avoid this you should add
>> "sparse
>> = yes" option to the FileSet definition. Then Bacula will try to
>> detect a
>> sparse space (all zeros) and do not backup this data but an
>> information
>> about sparse block only (a few bytes). Bacula sparse detection handle
>> 64kB
>> blocks only (a whole 64kB block has to be all zeros to mark it as a
>> sparse
>> block).
>>
>> best regards
>> --
>> Radosław Korzeniewski
>> rados...@korzeniewski.net
------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire
the most talented Cisco Certified professionals. Visit the
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
