> I need a litte bit help with Baculas catalog database locking > mechanisms. Is there anything I can do, to avoid locking the whole > catalog db during pruning or restore (tree build)? I have used bacula for 4 years and I have never seen this behavior. However I have never ran a job that took more than a day. My biggest backup was around 2TB which I believe completed in 15 to 17 hours to my LTO2 tape archive which is located on a different server than the director and also the bacula database. During this and any other backup I am completely free to run other jobs (backup, restore, label ...) on my other tape drives as long as the jobs do not use any of the tapes that are used in the current running backup.
Do you have maximum concurrent jobs set in your bacula-dir.conf? There are several places that this needs to be set depending on what concurrency you need. Also I know that your version of bacula is has a bug that sometimes causes problems when doing concurrent restores in which some of the files may not be restored. This was fixed in bacula 2.2.3. John ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
