Hi,

I've been using InitCatalog and Verify jobs to monitor my production
machines. This seems to work very well when there are modified files. 
However if a new files appears in one of the monitored directories then
all the files from then on will be reported at the same time as missing
and as new files with the same name/path/attributes...

I debugged this problem a bit and it seems to be due to the fact that
when bacula queries the DB for the file attributes one of the where
clauses is the FileIndex. If there are added or missing files the
FileIndex is no longer correct for all subsequent files and they are all
reported as missing and new. I think a possible solution would be to
tweak the local FileIndex variable when doing the Verify pass: so if a
file is new don't increment the FileIndex and if a file is missing
increment it anyway. In this way the proper FileIndex would be used in
the query and only "real" problematic files would be reported. 

Daniel.

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users