> A very good point.
> 
> In our environment, dbcheck takes about 3 days to run. The catalog is
> about 21GB, and the server is a dual-proc 3.2GHz, 32-bit machine with
12GB
> of RAM, running bacula 1.38.11 and MySQL 5.?.

How many rows are in your 'file' and 'path' tables?

Would there be any sense in doing the orphan check for only a subset of
entries at any given time? Eg every time db_check runs check only for
certain prefixes, eg first backup check for files starting with 'a',
then 'b' on the next backup and so on. Assuming the file is indexed
there shouldn't be much overhead. I think there are around 64 valid
filename characters, so 1/64th of 3 days would be an hour or two
(depending on the distribution of filenames over the set of valid
characters, which won't be uniform), which is probably more acceptable.

If the dataset was much larger though you might look at checking for
prefixes of (eg) 'aa - ae', then 'af - aj' etc, which would reduce the
time required but would mean a longer cycle time, during which time
orphans would increase in number.

James

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users