Re: [Bacula-devel] Director { Maximum Concurrent Jobs = X; }

[Carsten P. <ca...@ca...>]

Hi.

Sun, Feb 27, 2005 at 12:33:48PM +0100, Arno Lehmann schrieb:
> Hi,
> 
> Carsten Paeth wrote:
> >At this time no "just in time" restore is possible,
> >because restore jobs will by queued until one backup 
> >job is ready (priority of restore jobs is 1).
> >
> >It would be very nice to let the restore running if
> >the storage device is not in use (there is no job running
> >for this client in my setup).
> 
> Here lies one problem (not in your case, though).
> It should be possible for you to use a configuration which allows you 
> doing what you want, I think. Although not only with bacula-internal tools.
> 
> The key would be the Maximum concurrent jobs settings for all the 
> resources - file storage devices, clients, director, jobs and storage 
> definitions in the direcector's config file.
> 
> When setting this up, you /only/ have to keep one "slot" free for the 
> restore / verify jobs... You could use priorities to have the backups 
> run in blocks, so not all storage device "slots" are used at the same 
> time, but I wouldn't do this.
> 
> I'd rather start the backup jobs by a script, probably run as a post-job 
> script for each client or using cron or a script-internal scheduling, so 
> that a job is only started if less than a given number of jobs are 
> already running.
> 
> bconsole can be easily called from the shell, and with a little sed/awk 
> and grep this should be easily done.

Yes, this could be a solution for this time, but bacula has an internal
scheduling and I would like to use it.

> 
[...]
> More detailed scheduling directives would be better, of course.
> 
> I'd rather like a limit to the automatically scheduled jobs. Something 
> like Maximum scheduled Jobs = 6 and setting everything up for 10 
> concurrent jobs.

Yes, also a possiblity to fix by problem.
I will check how to implement these things ...

> 
> Perhaps a suggestion for the next release?
> 
> Arno
> 

best regards,

calle