[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bacula-devel] Improving job scheduling flexibility


On Saturday 23 February 2008, Kern Sibbald wrote:
> My current idea is to create a new "DuplicateJobs" resource and a new
> Duplicate Jobs directive which would point to the duplicate jobs resource.
> The reason for the resource is that there are just too many different
> variations that it would require a lot of new directives, and it seems a
> shame to add them to every Job.

While your point about redundant setups for different jobs is certainly valid, 
I also like Marc's opinion that directives in JobDefs ressources probably 
would be sufficient. Configuration of existing ressources is more simple than 
understanding the meaning of a new ressource. Adding a new ressource would 
not help the ease of use, esp. for beginners.

> DuplicateJobs {
>   Name = "xxx"
>   Allow = yes|no          (no = default)

While I personally in fact don't need duplicate jobs: Wouldn't your proposal 
modify the default behavior of the system, raising some problems for some 

>   Job Proximity = <time-interval>  (0)

Great idea.

Thx for your efforts,

Collax GmbH . Burkheimer Straße 3 . 79111 Freiburg . Germany
p: +49 (0) 761-45684-24
f: +49 (0) 761-45684-10        www.collax.com

Geschäftsführer: William K. Hite / Boris Nalbach
AG München HRB 158898 . Ust.-IdNr: DE 814464942

This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
Bacula-devel mailing list

This mailing list archive is a service of Copilot Consulting.