Hi, On 4/14/2007 2:07 AM, Michael FIG wrote: > Hi, all... > > I have Bacula 1.38.11-5ubuntu1 installed. > > Just recently, I believe our Bacula setup hit its first year > anniversary, and so now our 365 day volume retention period goes into > effect. > > It now takes a long time (several minutes) to complete a "status dir" > command.
That's normal, because for the status output, the DIR has to go through the pruning/recycling process. > To try to speed it up, I've run "myisamchk -o *.MYI" on all > the Bacula tables on our MySQL server. I've also added the following > indices (based on watching what queries bacula-dir was issuing via > MySQLAdmin): > > mysql> alter table File ADD INDEX(JobId); > Query OK, 2679492 rows affected (59.59 sec) > Records: 2679492 Duplicates: 0 Warnings: 0 > > mysql> alter table JobMedia ADD INDEX(MediaId); > Query OK, 13895 rows affected (0.15 sec) > Records: 13895 Duplicates: 0 Warnings: 0 Quite a catalog, I'd say... > mysql> > > This has helped a little, but I'm wondering if there's anything else > that I can do to make it snappier. Probably the only possible solutions to get this faster are - using separate catalog databases for different clients, - using a faster database server (either PostgreSQL, though I suppose that won't help much, or an external, dedicated MySQL server, or a faster Bacula server with a local catalog), - keeping spare volumes available and trigger pruining when the system is idle otherwise. > My second question is that I just noticed "*unknown*" being returned for > the volume on the scheduled jobs. Is this normal? I don't remember > seeing this before. This happens when the DIR can't find the volumes the jobs will use. This might be because the volumes to use are not yet purged. > > Here is the output I get from running bconsole. > > # bconsole > Connecting to Director bacula-dir:9101 > 1000 OK: bacula-dir Version: 1.38.11 (28 June 2006) > Enter a period to cancel a command. > *status dir > Using default Catalog name=MyCatalog DB=bacula > bacula-dir Version: 1.38.11 (28 June 2006) i486-pc-linux-gnu debian > testing/unstable > Daemon started 13-Apr-07 17:40, 0 Jobs run since started. > > Scheduled Jobs: > Level Type Pri Scheduled Name Volume > =================================================================================== > Differential Backup 10 13-Apr-07 22:05 server1 > *unknown* > Full Backup 10 13-Apr-07 22:05 server2 > *unknown* > Full Backup 10 13-Apr-07 22:05 server3 > *unknown* > [...] > Full Backup 10 13-Apr-07 22:05 client1 *unknown* > Differential Backup 10 13-Apr-07 22:05 client2 > *unknown* > Full Backup 10 13-Apr-07 22:05 client3 > *unknown* > [...] > ==== > > Running Jobs: > No Jobs running. > ==== > No Terminated Jobs. > ==== > * > > Thanks for any help you can offer, > I hope this did help you understanding what happens. Arno -- IT-Service Lehmann [EMAIL PROTECTED] Arno Lehmann http://www.its-lehmann.de ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
