>> > When you run a job by hand the schedule isn't involved.
>> > Either way, for your "Schedule" entry you need "Level="
>> > before the work "Full".
>> >
>> > Schedule {
>> >   Name = "test"
>> >   Run = Level=Full at 11:50
>> > }
>> >
>> >
>> > But, your problem is that your Job doesn't have a Default
>> > Level defined.  You'll need something like this:
>> >
>> > Job {
>> >   Name = "job_backup1"
>> >   Type = Backup
>> >   Level = Full
>> >   .
>> >   .
>> > }
>> >
>> > On Fri, May 22, 2009 at 11:48:07AM -0500, Zhengquan Zhang wrote:
>> >> Hello,
>> >>
>> >> The first time I run the job it runs full well, but I tried to run it
>> >> more times, it will run incremental automatically. Could anyone help 
>> >> me
>> >> understand this? I am learning bacula and please forgive me for this 
>> >> easy
>> >> question.
>> >>
>> >> *run
>> >> A job name must be specified.
>> >> Automatically selected Job: job_backup1
>> >> Run Backup job
>> >> JobName:  job_backup1
>> >> Level:    Incremental
>> >> Client:   client_backup1
>> >> FileSet:  fileset_backup1
>> >> Pool:     Default (From Job resource)
>> >> Storage:  storage_backup1 (From Job resource)
>> >> When:     2009-05-22 11:49:34
>> >> Priority: 10
>> >> OK to run? (yes/mod/no):
>> >>
>>
>> One further note, that may be very obvious, but since this was a learning
>> phase (well, it always is a learning phase, after a few years we just 
>> have
>> proceeded to a little higher level in the studies...)
>
> Thank you, Timo for your patience to a learner.
>
>>
>> When running jobs manually, any of the job parameters (level, pool, etc) 
>> may
>> be changed manually from the command line by answering "mod" to the 
>> prompt
>> above. These changes do not modify the original confs, but affect just to
>> this spesific run.
>>
>> So, if it were intentional that job is normally run as incremental by
>> default, for a single manual run it still could be promoted to full by
>> answering "mod". Or vice versa (if there is no reason like a modified
>> fileset why the system automatically promotes it anyway)
>>
>>
>> But obviously there was a need to add level spec to job definition, 
>> wheter
>> it should be full or whichever. IMO, it's a kind of important setting 
>> that
>> it's not a good idea to only trust on internal defaults, explicitly
>
> Thanks for pointing this out. But if I do set the runlevel for each
> backup task in the schedule section of the configuration file. Do I
> still need a "level=**" in a job definition? I remember for a few
> config files I saw on the web, the level of the backup are always
> explicitly stated in the schedule section. So I don't truly understand
> why we neede a default backup level in the job definition. Could you
> help me understand this?
>

>>From Bacula manual (concerning "level" in job definition):
----
The Level directive specifies the default Job level to
be run. Each different Job Type (Backup, Restore, ...) has a different
set of Levels that can be specified. The Level is normally overridden
by a different value that is specified in the Schedule resource.
This directive is not required, but must be specified either by a Level
directive or as an override specified in the Schedule resource.
----

So, you have to specify level *somewhere*, either in the job definition, or 
in the shedule, and nothing technically prevents you specifying it in the 
both places as well.

The one specified in the job definition is a default that may be overridden 
elsewhere: in the schedule, or on command line when running a job manually. 
If you want to control the default that is offered to you when running jobs 
manually from the command line, then you have to define the level (at least) 
in the job definition.

Specifying it in the job definition allows you not to repeat it every time 
if you had several lines (to be run on the same level) in your schedule. The 
decision where to do it, is up to you. Just choose the way you feel most 
comfortable with.


>> mentioning the level in the conf file makes it easier to read and 
>> understand
>> the configuration. However, to keep the conf more clear, I think it's a 
>> good
>> idea to specify in the job definition a level that will be used most 
>> often,
>> and only specify a minimal amount of changes in the schedule. So, I would
>> usually prefer "incremental" in the job definition, unless it's really
>> desirable to run the job as "full" every time. In this sense, in the
>> original conf the "full" setting only in the schedule seemed reasonable.
>>
>> Btw, if there is a need to add more job definitions to the conf in the
>> future, have a look at "job defaults" section. This way there is no need 
>> to
>> repeat all the settings for every job definition. It's a kind of named
>> "macro" that is referred to in the job definition.
>
> Thanks for this suggestion. I will definetely use this feature once I
> get the backup running correctly.
>
> Regards,
>
> -- 
> Zhengquan
>



------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, & 
iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian
Group, R/GA, & Big Spaceship. http://www.creativitycat.com 
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users