Each client has its own volume and pool, but each gets written to the same directory location.
I've set up Bacula to use maximum concurrent jobs everywhere, so jobs should be able to be run concurrently. Each of the three clients is configured to run its job at the same time: 12:35am. When 12:35 rolls around, though, I get one job that finishes correctly, and the other two get errors saying something like "28-Apr 00:35 ruby-sd: Emerald.2005-04-28_00.35.01 Fatal error: Device /root/backup is busy writing on another Volume."
I've gone through the Bacula handbook a couple of times now, and I must be missing the point where it says that you can only run one job on an archive device at any given time. It pseudo-makes sense for tapes, but not for random-access devices such as hard disks. Could someone go through and explain to me why this can't be done, or if I'm just doing (or interpreting) things incorrectly, where in the handbook it explains it?
If it helps, I can send out my config files as well.
-- Alan Gerber
------------------------------------------------------- SF.Net email is sponsored by: Tell us your software development plans! Take this survey and enter to win a one-year sub to SourceForge.net Plus IDC's 2005 look-ahead and a copy of this survey Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users