Hello,
On 2020-11-07 01:01, B. Smith wrote:
> Hi,
>
> When using accurate=yes and verify=pins5, does Bacula recalculate the MD5
> for each file even when the atime/mtime/ctime of the file has not changed?
It is configurable, and from what I see in your fileset, this is what
you have set. "Accurate = pins5" (the character 5 at the end).
To speed up things, you might want to not do it unless you data is very
critical.
Hope it helps!
Best Regards,
Eric
> I have large files (~60GB) that rarely change in a directory; usually just
> a new large file is added every couple of weeks... files are rarely ever
> deleted and never modified. When I run the incremental, however, it is
> taking hours to examine the files. Is there anything I can do to speed this
> up? I have what should be plenty of memory (32GB). Job and FileSet
> definitions are below.
>
> Job {
> Name = "Big Files"
> Write Bootstrap = "/var/db/bacula/bigfiles-%s-%e.bsr"
> JobDefs = DefaultJob
> Type = Backup
> Level = Incremental
> Client = FreeNAS-fd
> FileSet = "Big Files"
> Spool Data = yes
> Storage = TapeLibrary
> Pool = File
> Accurate = yes
> Schedule=LargeFileCycle
> Priority = 12
> }
>
> FileSet {
> Name = "Big Files"
> Include {
> Options {
> signature = MD5
> Accurate=pins5 #should allow keeping track of deleted/renamed files.
> verify = pins5 #compare permission bits, then inodes, number of links,
> size, and finally MD5 changes
> IgnoreCase = yes
> }
> File = "/media/DataSet1/Big Files/"
> }
> }
>
> Thanks,
>
> B. Smith
>
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
