Kern Sibbald wrote:
The problem is that your Catalog database is not well tuned (missing
indexes),
or you have a very large database. The performance problem comes from Bacula
attempting to find the next volume that will be used for each scheduled job,
and to do so, it must generally
On Wednesday 14 February 2007 13:22, Gavin Conway wrote:
Kern Sibbald wrote:
The problem is that your Catalog database is not well tuned (missing
indexes), or you have a very large database. The performance problem
comes from Bacula attempting to find the next volume that will be used
On Wednesday 14 February 2007 13:22, Gavin Conway wrote:
Kern Sibbald wrote:
The problem is that your Catalog database is not well tuned (missing
indexes), or you have a very large database. The performance problem
comes from Bacula attempting to find the next volume that will be used
Hello,
I'm currently using bacula 1.38.11 and sometimes, when I run status
dir on the console, it generates a high load on the server ( 3, more
than 15minutes) and blocks the console from user input. Basically, it
spends all this time to dress the list of scheduled jobs.
My server is maybe a bit
On Sunday 11 February 2007 10:28, Mikael Kermorgant wrote:
Hello,
I'm currently using bacula 1.38.11 and sometimes, when I run status
dir on the console, it generates a high load on the server ( 3, more
than 15minutes) and blocks the console from user input. Basically, it
spends all this
