Hi folks,

looks like extending the value range did not fix the error
entirely. When running an incr. backup, I receive the following error
message: 

Fatal error: Can't fill File table Query failed: INSERT
INTO File (FileIndex, JobId, PathId, FilenameId, LStat, MD5)SELECT
batch.FileIndex,
batch.JobId, Path.PathId, Filename.FilenameId,batch.LStat, batch.MD5
FROM batch JOIN Path ON
(batch.Path = Path.Path) JOIN Filename ON (batch.Name =
Filename.Name): ERR=Duplicate entry
'0' for key 1

I've tried deleting those rows with "0" from File (1 Row), but
apparently that did not fix the problem. 

Will I need to upgrade to bacula 5.0 in order to resolve the issue? Is
3.x limited to 32bit auto_inc counters or something?

All the best, 

Uwe 
-- 
NIONEX ist ein Unternehmen der DirectGroup Germany www.directgroupgermany.de

------------------------------------------------------------------------------
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users 
worldwide. Take advantage of special opportunities to increase revenue and 
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users