Hello,

01.12.2009 17:56, Clark Hartness wrote:
> I know that subject doesn't make a lot of sense....
> 
> I have a job that I manually start at the completion of a script to
> backup a list of files on the Client.

Manually meaning you pass something like 'run job=name yes' to bconsole?

> I don't want the job to run on Schedule but I would like to be able
> to set the level of the Job by days following something like this
> Schedule.
> 
> Schedule { Name = "test_schedule" Run = Level=Full on 1st sat # Use
> for Monthly Full First Saturday Run = Level=Differential sun Run =
> Level=Incremental on 2nd-5th sat Run = Level=Incremental mon-fri }
> 
> This of course runs constantl because there is no "at" time set.
> 
> Is there a way to set the level using bacula's scheduler without
> scheduling the job?

No. The only thing the scheduler can do is scheduling jobs. It can't 
change the jobs setting depending on the date, time, etc.

In your script, you could set the level as you like, and then do
echo "run level=${JOBLEVEL} job=jobname yes" | bconsole

Getting the first Saturday of a month with bash & date is not as 
simple as using Bacula's scheduler, but still not really difficult... 
alternatively, you could run your script from a RunScript resource in 
the Job.

Arno

> TIA Clark 

-- 
Arno Lehmann
IT-Service Lehmann
Sandstr. 6, 49080 Osnabrück
www.its-lehmann.de

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing. 
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users