On 04/22/10 02:14, Sorix wrote:
>
> I've done some modifications.
>
> Schedule {
> Name = "Default"
> Run = Level=Full Pool=Tape 1st sun at 2:05
> Run = Level=Incremental Pool=File mon-fri at 2:05
> }
>
>
> JobDefs {
> Name = "Windows 2008"
> Schedule = "Default"
> Messages = Standard
> Priority = 10
> Write Bootstrap = "/var/bacula/%c.bsr"
> Type = Backup
> FileSet= "Windows 2008"
> Pool = File
> }
>
>
> Job {
> Name = "mail4srv"
> JobDefs = "Windows 2008"
> Client = "mail4srv-fd"
> Enabled = yes
> }
That's looking much better. One suggestion, though - Move your Pool
overrides from the Schedule to the Job or JobDefs, like this:
Schedule {
Name = "Default"
Run = Level=Full 1st sun at 2:05
Run = Level=Incremental mon-fri at 2:05
}
JobDefs {
[...]
Pool = File
Incremental Pool = File
Differential Pool = File
Full Pool = Tape
}
Pool overrides in the Schedule resource have been deprecated (but, for
backward compatibility, not removed) because they do not work properly
when a Job is promoted to a higher level because of a missing or failed
previous job. Overrides were re-implemented in the Job because it is
architecturally infeasible to fix the problem within the Schedule-based
implementation. Specifying per-level Pools in the Job or JobDefs is
both cleaner and more reliable, and also allows Jobs using the same
Schedule to use different override Pools.
(In this case, the Incremental Pool and Differential Pool directives are
redundant and should be unnecessary. But it won't hurt anything to have
them there, and the example is useful.)
--
Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355
ala...@caerllewys.net ala...@metrocast.net p...@co.ordinate.org
Renaissance Man, Unix ronin, Perl hacker, Free Stater
It's not the years, it's the mileage.
------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
