Check database when bacula-dir start
Do you think if I tuning databases with :
CREATE INDEX File_JobId_idx ON File(JobId);
CREATE INDEX File_PathId_idx ON File(PathId);
CREATE INDEX File_FilenameId_idx ON File(FilenameId);
CREATE INDEX Path_PathId_idx ON Path(PathId);
CREATE INDEX Job_FileSetId_idx ON Job(FileSetId);
CREATE INDEX Job_ClientId_idx ON Job(ClientId);
CREATE INDEX File_FilenameIdPathId_idx ON File(FilenameId,PathId);
Or with :
CREATE INDEX file_jobid_idx on file (jobid);
CREATE INDEX file_jpf_idx on file (jobid, pathid, filenameid);
it will be faster?
Le 6 avril 2012 18:10, John Drescher <drescherjm < at > gmail.com ([email]drescherjm < at > gmail.com[/email])> a écrit :
> I have a bacual-dir with ~250 clients. And each client has its own catalog.
When bacula-dir start, bacula-dir checks each database (~10s per client =
~45 minutes !!!)
Meanwhile, the director is not accessible...
How can I bypass that or reduce that ?
I would try speeding up your database server perhaps by putting the
databases on an SSD or an array of them or at minimum a RAID10 of fast