On 08/12/10 10:03, Romer Ventura wrote:
Hello,
I am trying to have 1Job definition and have it run Full, Incremental
and Differential backups to different media depending on the schedule
set, but i cant get it to work. What i want to do is do full backups 1st
sunday of every month and write it to tape, then do incremental backups
monday-friday and write it to disk, finally do differential backups
every sunday except for the 1st sun of the month and write it to tape.
The job "H34-FileServ-dsk-tap" keeps running every night when it should
just run on sundays
Here is what i got:
You're doing this wrong. You've defined two separate Jobs for the same
backup, you've forced the level in your JobDefs, and you have two
redundant sets of Pool overrides.
JobDefs {
Name = H34-FileServ-def
Type = Backup
Level = Incremental
Client = housigma34-fd
FileSet = "H34-FileServ"
Schedule = "WeeklyCycle"
Messages = Standard
# Pool = Default
Full Backup Pool = Full-Pool-dsk-tpe
Differential Backup Pool = Diff-Pool-dsk-tpe
Incremental Backup Pool = Incre-Pool-dsk-dsk
Write Bootstrap = "/var/lib/bacula/%c.bsr"
Priority = 10
}
Remove the Fileset and Client specificiation from this JobDefs resource.
They belong in the Job resource; otherwise, you've tied this JobDefs to
a single client and completely defeated the point of JobDefs by making
it non-reusable. I'd advise making the default level in the JobDefs
Full, and the default Pool your full pool.
Job {
Name = H34-FileServ-dsk-tap
JobDefs = H34-FileServ-def
Pool = Default
Storage = SLDLTv4
}
Don't specify the Storage in the Job definition. Let Bacula figure out
which Storage to use. Your FileSet and your Client directives belong
here. You're also specifying a static default Pool in your Job which is
better left in the JobDefs.
Job {
Name = H34-FileServ-dsk-dsk
JobDefs = H34-FileServ-def
Pool = Default
Storage = File
}
Get rid of this second Job definition. It's doing you no good
whatsoever and just confusing the issue.
Schedule {
Name = "WeeklyCycle"
Run = Level=Full Pool=Full-Pool-dsk-tpe 1st sun at 20:00
Run = Level=Differential Pool=Diff-Pool-dsk-tpe 2nd-5th sun at 20:00
Run = Level=Incremental Pool=Incre-Pool-dsk-dsk mon-fri at 22:00
}
Remove the Pool overrides from this Schedule. Pool overrides in the
Schedule are deprecated because they don't work reliably and cannot be
made to work reliably. Having two sets of overrides for the same job is
likely confusing Bacula. Keep the ones in your JobDefs; lose the ones
in the Schedule.
After those changes, you should be looking at something pretty much like
this:
JobDefs {
Name = H34-FileServ-def
Type = Backup
Level = Full
Schedule = "WeeklyCycle"
Messages = Standard
Pool = Full-Pool-dsk-tpe
Full Backup Pool = Full-Pool-dsk-tpe
Differential Backup Pool = Diff-Pool-dsk-tpe
Incremental Backup Pool = Incre-Pool-dsk-dsk
Write Bootstrap = "/var/lib/bacula/%c.bsr"
Priority = 10
}
Job {
Name = H34-FileServ-dsk-tap
JobDefs = H34-FileServ-def
Client = housigma34-fd
FileSet = "H34-FileServ"
}
Schedule {
Name = "WeeklyCycle"
Run = Level=Full 1st sun at 20:00
Run = Level=Differential 2nd-5th sun at 20:00
Run = Level=Incremental mon-fri at 22:00
}
Give that a shot and see if it works for you.
--
Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355
Renaissance Man, Unix ronin, Perl hacker, Free Stater
It's not the years, it's the mileage.
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
_______________________________________________
Bacula-users mailing list
