hi arno,
i have matched up my config to the example that you gave. so now i have:
FD: 20
SD: 20
DIR/Jobs: 1
DIR/Director: 20
DIR/Storage1(Autochanger): 4

...but, jobs still seem to run in serial... any thoughts?

thx,
mike


Arno Lehmann wrote:
> Hi,
>
> 10.01.2008 20:34, Mike Seda wrote:
>   
>> hi arno,
>> i forgot to mention that i have:
>> Maximum Concurrent Jobs = 2
>>     
>
> Where do you have that setting?
>
>   
>> should i increase that number? fyi, i just noticed that two concurrent 
>> backup jobs do in fact run, but only for the _same_ host. it is weird.
>>     
>
> I'm not so sure yet...
>
> Let me explain what I usually set up regarding maximum concurrent jobs:
> In the FD: Whatever I think is reasonable for that machine and its 
> network link, usually one or two
> In the SD: Whatever you think it can manage. Depends on number of 
> drives, available spool space, and settings in the DIR. Usually rather 
> high - up to 20 or upwards even.
> In the DIR/Job resource: Typically one.
> In the DIR/Director resource: What you think is a reasonable upper 
> limit for the jobs running simultaneously. This applies to all 
> configured storage devices, so you'll need at least as many jobs as 
> you have storage devices, usually.
> DIR/Storage resource: Here goes the real number of jobs you want to go 
> to that device in parallel. This is where I actually manage how many 
> jobs run in parallel.
>
> Short example:
> Let's assume we have 20 clients, each with one job, all scheduled at 
> the same time.
> FD: 20
> SD: 20
> DIR/Jobs: 1
> DIR/Director: 20
> DIR/Storage1: 1
> DIR/Storage2: 4
> DIR/Storage3: 2
>
> In this case, Bacula could run up to 7 jobs in parallel, but would 
> never run more than 1/4/2 jobs to Storage1/2/3 at the same time.
>
> Provided you've got your storage devices assigned to the pools, and 
> the different job levels go to separate pools - which is what I prefer 
> - and Storage2 is an autochanger with more than one drive and tapes 
> from all pools loaded such a setup can help you using your tape drives 
> most efficiently.
>
> Arno
>
>
>   
>> regards,
>> mike
>>
>>
>> Arno Lehmann wrote:
>>     
>>> Hi,
>>>
>>> 08.01.2008 17:34, John Drescher wrote:
>>>   
>>>       
>>>> On Jan 8, 2008 11:21 AM, Mike Seda <[EMAIL PROTECTED]> wrote:
>>>>     
>>>>         
>>>>> all,
>>>>> i am frustrated beyond belief.
>>>>>
>>>>> i recently spent $8K for a second tape drive for my library.
>>>>>
>>>>> all i want is for two bacula backup jobs (one for each tape drive) to
>>>>> run concurrently. i upgraded the backup server to 2.2.7 (to take
>>>>> advantage of improved code for handling multiple drives). the clients
>>>>> are still running 2.0.x.
>>>>>
>>>>> i have looked at *so* many postings on concurrent jobs, and have tried
>>>>> multiple configuration changes but to no avail. please tell me that
>>>>> there is a way to make two concurrent backup jobs work. is there anyway
>>>>> to put an end to my suffering other than buying a gun? :-P
>>>>>       
>>>>>           
>>> Sure...
>>>
>>>   
>>>       
>>>>> My server setup is:
>>>>> Bacula 2.2.7
>>>>> RHEL 4 AS
>>>>> Quantum PX502 (FC, 2 HP LTO-3 Drives)
>>>>>
>>>>> i can send my *.conf files if needed.
>>>>>       
>>>>>           
>>> Probably not needed.
>>>
>>>   
>>>       
>>>>> mike
>>>>>
>>>>>       
>>>>>           
>>>> First advice:
>>>> Put the two jobs you want to run concurrently on different tape drives
>>>> in different pools.
>>>>     
>>>>         
>>> Also, read the manual chapter on configuring the DIR, especially the 
>>> Job section, and even more especially this part:
>>>
>>> Prefer Mounted Volumes = <yes|no>
>>>      If the Prefer Mounted Volumes directive is set to yes (default 
>>> yes), the Storage daemon is requested to select either an Autochanger 
>>> or a drive with a valid Volume already mounted in preference to a 
>>> drive that is not ready. This means that all jobs will attempt to 
>>> append to the same Volume (providing the Volume is appropriate -- 
>>> right Pool, ... for that job). If no drive with a suitable Volume is 
>>> available, it will select the first available drive. Note, any Volume 
>>> that has been requested to be mounted, will be considered valid as a 
>>> mounted volume by another job. This if multiple jobs start at the same 
>>> time and they all prefer mounted volumes, the first job will request 
>>> the mount, and the other jobs will use the same volume.
>>>
>>>      If the directive is set to no, the Storage daemon will prefer 
>>> finding an unused drive, otherwise, each job started will append to 
>>> the same Volume (assuming the Pool is the same for all jobs). Setting 
>>> Prefer Mounted Volumes to no can be useful for those sites with 
>>> multiple drive autochangers that prefer to maximize backup throughput 
>>> at the expense of using additional drives and Volumes. This means that 
>>> the job will prefer to use an unused drive rather than use a drive 
>>> that is already in use.
>>>
>>> Of course, you do this in addition to enabling basic Job Concurrency...
>>>
>>> Arno
>>>
>>>   
>>>       
>>>> John
>>>>
>>>> -------------------------------------------------------------------------
>>>> Check out the new SourceForge.net Marketplace.
>>>> It's the best place to buy or sell services for
>>>> just about anything Open Source.
>>>> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
>>>> _______________________________________________
>>>> Bacula-users mailing list
>>>> Bacula-users@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/bacula-users
>>>>
>>>>     
>>>>         
>>>   
>>>       
>> -------------------------------------------------------------------------
>> Check out the new SourceForge.net Marketplace.
>> It's the best place to buy or sell services for
>> just about anything Open Source.
>> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
>> _______________________________________________
>> Bacula-users mailing list
>> Bacula-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bacula-users
>>
>>     
>
>   


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to