On 04/26/13 10:11, Ana Emília Machado de Arruda wrote:
> Hi Jonathan,
> 
> You have to put a "JobDefs = <JobDefs-Resource-Name>" directive in each Job
> definition. For example, for your above job definition:
> 
> 
> Job {
> 
>   Name = "D0LPHB040 System Backups"
>   JobDefs="DefaultJob"

Hi Ana, Johnathan...


Ana, you're close.   But the JobDef = line must point to a JobDef Resource
like so:

JobDef {
 # Options to be inherited by multiple Jobs
 Name = LinuxServers
 Type = Backup
 FileSet = LinuxFiles
 Level = Incremental
 Messages = LinuxBackups
 Schedule = LinuxSchedule
 Pool = LinuxPool
 Priority = 10
}

Job {
 Name = LinuxServer_A
 JobDef = LinuxServers
 ...
 rest of required options go here
 ...
}

Job {
 Name = LinuxServer_B
 JobDef = LinuxServers
 ...
 rest of required options go here
 ...
}

In that example above, Jobs LinuxServer_A and LinuxServer_B will inherit and
use all of the settings from the JobDef named "LinuxServers".

Jobs A and B will of course need to have all other required job options defined.

Also any options inherited from the JobDef may also be overridden in the Job.
So for example, you can set up a Job to use the LinuxServers JobDef, but then
also set up the Job to use a different schedule, Pool, Priority, Level, etc.

Hope this helps.

-- 
Bill Arlofski
Reverse Polarity, LLC

------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users