Hi,

On 1/19/2007 8:54 PM, Wessel van Heerde wrote:
> 
> 
> Arno Lehmann wrote:
> 
>>Hello,
>>
>>On 1/19/2007 12:02 PM, Wessel van Heerde wrote:
>>
>>>Hi there,
>>>
>>>In my Bacula setup I have specified several backup jobs, that are based
>>>on a
>>>job definition. In the job definition i have specified that the pool to
>>>use
>>>is the Default Pool. That pool does exists, but i do not want to use it
>>>at
>>>all. In the schedule resource I specified the pools to use for the backup
>>>jobs, but when the jobs in the schedule are runned, the director always
>>>chooses the pool specified in the job definition, instead of the one in
>>>the
>>>schedule, which actually should override the one in the job definition.
>>>Here
>>>is my configuration:
>>
>>... which looks good to me.

For reference, here is a schedule I run:

Schedule {
   Name = "RegBacula"
   Run = Level=Full Priority=100 Storage=DLT Pool=Full 1st tue at 8:32
   Run = Level=Full Priority=100 Pool=Diff 2nd-5th tue at 8:33
   Run = Level=Full Priority=100 Pool=Incr sun,mon,wed-sat at 8:34
}

This worked as expected since - I believe - 1.36 or .37

>>
>>>What am I doing wrong. Why doesn't the schedule override the JobDefs? I
>>>would appriciate it very much if anyone would like to help me out on
>>>this. I
>>>have been looking at this problem for some time and I don't now where to
>>>look anymore.
>>
>>Which version of bacula do you run?
>>
>>In the newer ones, the job reports give information about where the pool 
>>was determined, so that might give a clue.

And the following text is a job result mail from a jobs using this schedule:

18-Jan 10:40 goblin-dir: Start Backup JobId 8577, 
Job=BackupCatalog.2007-01-18_08.34.02
18-Jan 11:04 goblin-sd: Job write elapsed time = 00:23:18, Transfer rate 
= 1.204 M bytes/second
18-Jan 11:04 goblin-dir: AfterJob: run command 
"/etc/bacula/delete_catalog_backup goblin-fd BackupCatalog Full OK"
18-Jan 11:04 goblin-dir: Bacula 2.0.0 (04Jan07): 18-Jan-2007 11:04:49
   JobId:                  8577
   Job:                    BackupCatalog.2007-01-18_08.34.02
   Backup Level:           Full
   Client:                 "goblin-fd" 2.0.0 (04Jan07) 
i586-pc-linux-gnu,suse,8.1
   FileSet:                "Catalog" 2004-11-01 16:25:01
   Pool:                   "Incr" (From Run pool override)
                                   ^^^^^^^^^^^^^^^^^^^^^^
here you see why a newer version might help analyzing this problem.

   Storage:                "HPDAT" (From Pool resource)
   Scheduled time:         18-Jan-2007 08:34:00
...
   Termination:            Backup OK

> 
> Thanks for your reply,
> 
> I'm running Bacula 1.38.11. An other post states that I should just let the
> schedule run, and that the run command makes the wrong pool choice. But that
> is not the case. It also makes the wrong choice when the schedule is
> started.
> 
> Also, when I run the show schedule command, the schedule always choices the
> right pool. The wrong pool is used at the moment the schedule starts
> running.

Well, thinking about an upgrade would not be wrong.

Apart from that I can only suggest to run the DIR with debug output enabled.

At a sufficiently high debug level (try 200 to start) you should see the 
decisions the DIR makes when it schedules a job.

At least I can confirm that the schedule should work.

Arno

-- 
IT-Service Lehmann                    [EMAIL PROTECTED]
Arno Lehmann                  http://www.its-lehmann.de

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to