On Apr 6, 2005 3:45 PM, Ian <[EMAIL PROTECTED]> wrote:
> > Thought about that, and i think it will be that way for me to archive
> > the results i try to get.
> >
> Would it be feasable to fire this off as the 'RunBeforeJob' job? You could
> then have a single master job that fired off all the other jobs before
> running?
Sounds good and i think i'll give it a try, but i've got some other
problems to fix first.
I reconfigured the system to use only two file devices (each about
1.1TB). According to tips.html#ConcurrentJobs i set up the system to
make 20 concurrent jobs, but i still get the following in the director
status:
JobId Level Name Status
======================================================================
38 Increme achilles.2005-04-08_13.46.55 is waiting on max Storage jobs
37 Increme pegasus.2005-04-08_13.46.42 is running
I'm stuck on that, since i don't see anything that would prevent more
than 1 job to be run simultaneously (sp?). I set the 'maximum
concurrent jobs' to 20 for each Director Client JobDef FileDaemon and
Storage configuration...
The only constellation where two jobs run together, is when they don't
use the same Device ... and i don't think that this should be correct.
Regards,
Frank
--
Two of the most famous products of Berkeley are LSD and Unix.
I don't think that this is a coincidence.
-- Anonymous
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
