Zitat von Uwe Schuerkamp <uwe.schuerk...@nionex.net>: > On Fri, Jan 11, 2013 at 02:52:05PM +0000, Martin Simmons wrote: > >> Do you know which volume is used? There seems to be some confusion between >> incremental-0058 and incremental-0508. >> >> Is that a common feature of other failures like this? > > > The problem is that this occurs only every once in a while, for the > most part volume recycling works as advertised. Do you suggest I > should delete the volume in question and have bacula create a new one? > >> Can you log all queries in the mysql server to see if that records anthing >> interesting? > > I guess such a log would grow to be quite large, right? Esp. as I have > no way of knowing when the error occurs, and I expect a *lot* of > queries to be fired up on a 200GB+ File table ;) >
Fact is that Bacula has to wait for the query doing the recycling/pruning task and MySQL does not finish in a reasonable time. With this the following errors are possible: - Wrong usage of SQL query by Bacula, but this should get problems everytime not at random occasions - Bad planer decisions inside MySQL - Scalability problems with MySQL While it might be possible to tune-up the MySQL part of Bacula, your short term solution is more at the MySQL side. Do you have the latest release and checked/repaired all index and optimizer values? If yes, you might try export/import or replicate/switch-over or maybe even switch to PostgreSQL. Regards Andreas ------------------------------------------------------------------------------ Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS and more. Get SQL Server skills now (including 2012) with LearnDevNow - 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only - learn more at: http://p.sf.net/sfu/learnmore_122512 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
