Hi Arno, Thanks for the response.
Arno Lehmann wrote: > Do you think a separate section regarding concurrent jobs would be > necessary, that extends the existing contents in "Tips and Suggestions"? I don't think so, I understood how things worked where I was looking, but wasn't looking in the right place. After reading your response I found the explanation in the "Basic Volume Management" section. Maybe a link between the two sections would be useful. >> jobs... I want "Client A" to run "Job A" and "Client B" to run "Job B" >> at the same time, do I need to set concurrency in my clients and jobs in >> order to do this? > > It's not necessary in your case then. Okay, that's what I thought. Thanks for confirming. >> The error I get is something like, "trying to write to volume daily-0002 >> but storage is currently writing to daily=0001". > > That indicates that Bacula would run jobs concurrently if you hadn't set > up your jobs to require different volumes. Ah-ha! I think I understand now, and ironically while looking for the "Tips and Suggestions" section to respond to your question above, I found the "Basic Volume Management" section in which it pretty plainly says I will "need multiple Device resources in your bacula-sd.conf file, and thus multiple Storage resources in your bacula-dir.conf." > More detailed information about your pools and job settings would be > helpful to explain that. I write one job per volume, and currently all volumes are in one place, e.g. "/var/bacula/monthly-0003". After reading some more, I think I should be able to make four more identical (except for Name) Device and Storage resources that all point to the same directory and it will be able to write up to five jobs at once. I was planning on splitting my volumes up, however, so each client had their own directory and volumes, e.g. "/var/bacula/foo.domain.com/0001" and "/var/bacula/bar.domain.com/0001", which I think means I would need additional Device and Storage defnintions each with their own Media Types, like "Media Type = File-foo.domain.com". I'll have to think about if I still want to do that and how to organize it...maybe just different pools. Is there a way to prevent Bacula from killing the job after just a few seconds of waiting for the volume? Last night I had a large backup running and eight incremental jobs failed because they couldn't mount a volume...I can see this happening in the future if there is a large backup or two, even if I have a number of Devices, so maybe that's not the best course of action. Is there some sort of timeout option? Would data spooling take care of this? Thanks again, Josh ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
