Hi, Before submitting a bug, I want to discuss here on the list, to be sure that this is a bug, and not a misunderstanding of how bacula works. I have bacula (2.0.1) configured to do concurrent jobs, and it works very well. The only thing that isn't perfect is the restore job. I have a default restore job, with a random pool, random storage, etc. The problem is that when bacula is about to restore something, it uses the concurrency configuration of this random storage (which on my case was a storage with a limit of 1 concurrent job). Shouldn't bacula use the concurrency configuration of the storage that it will actually use for the restore?
I have a tape drive with a configuration of 1 concurrent job, and a hard disk with a configuration of 4 concurrent jobs. Should I configure bacula with two restore jobs to be able to maintain this concurrency policy also when restoring? Thanks in advance. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
