Hello Peter, One more question: Is the client for which this Catalog error is occurring a Windows machine?
If so, I believe that I have found the problem, if not, then I have to look further. Best regards, Kern On 12/25/2015 09:18 PM, Peter Keller wrote: > Hello, > > On 12/25/2015 02:01 AM, Kern Sibbald wrote: >> On 12/25/2015 08:11 AM, Kern Sibbald wrote: >>> On 12/25/2015 01:33 AM, Peter Keller wrote: >>>>> 23-Dec 18:47 DIR:xxx.yyy.zzz JobId 4: Error: Catalog error updating file >>>>> digest. bdb.h:101 Update failed: affected_rows=0 for UPDATE File SET >>>>> MD5='oGhRwHZ+y+mWb+fv9ppFrA' WHERE FileId=6148914691236517205 >> If you do not have Spool Attributes turned on, I recommend that you do >> so to see if it fixes the problem. > I turned it on and it indeed ceased emitting the error! Thank you very much! > > Although the underlying bug is not fixed, this just prevented the situation > where it arose. Good enough for my needs though, I appreciate it a lot! > > Concerning your recommendations for Volume size, I'll probably use ~50GB since > I'm interested in auto recycling and don't want to maximize the number of > volumes that are holding unexpired jobs by using very large volumes like > 500GB. > I admit I could be wrong about my reasoning. :) > > I'm also implementing offsite backups via copy jobs (but haven't started on > this task yet). I don't have a good handle on how Volume sizes relate > to or modulate how copy jobs work. Would you be so kind as to comment on > this topic? > > Thank you! > > -pete > ------------------------------------------------------------------------------ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
