I am running v5.0.2 against some clients with many files (5-10
million). I have and want the fileset option of accurate=mcs5 (md5
checks) when I do a full backup of the clients. However I DO NOT want
to do a md5 check when I do differentials/incremental's due to the fact
that it takes days for bacula to calculate the md5's as it's single
threaded.
I was hoping to get around manually editing the fileset options before a
full backup to use mcs5 and then reset it to mcs for day/day
incrementals. Something like
Run=Differential Pool=BackupSetDD FullPool=BackupSetAA Include {
Options { accurate=mcs }} Sat at 02:00
but that doesn't work. Is there a way to do this, or, where are we at
with multi-threading which would alleviate this (assuming we can get
12-24 threads/one per core) going at the same time in the file director?
Steve
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
