RE: [Bacula-users] Differentials Jobs referencing obsolete Full Job

[Bennett, S. \(GE Infrastructure\) <Sil...@ge...>]

-----Original Message-----
From: Phil Stracchino [mailto:phi...@sp...]
Sent: Thursday, September 29, 2005 1:31 PM
To: Arno Lehmann
Cc: Bennett, Silas (GE Infrastructure);
bac...@li...
Subject: Re: [Bacula-users] Differentials Jobs referencing obsolete Full
Job


>Arno Lehmann wrote:
>> Hello,
>>=20
>> I'll put my answer to Phil's post here... it just fits better.
>>=20
>> Phil, if he scenario you describe really can happen I think it would =
be
>> time to consider the time stamp stored in the FileSet when looking =
for
>> previous backups. sqlquery follows:
>
>I don't know whether I can or not; I haven't looked at the code to see.
>And at the moment I don't know that I could tell anything anyway.
>
>> Ha! Is it possible that your Full and Differential backups are =
actually
>> _two_ jobs, instead of one job with different levels in the schedule?
>> I've seen this from some people, and it might be that the manual =
doesn't
>> state it clear enough, but you must define one job and set the backup
>> level either manually when running that job, or override it in the
>> schedule.
>>=20
>> Bacula won't base a differential backup on a full one defined in =
another
>> job resource, even if they have client, fileset, and all other stuff =
in
>> common.
>

BINGO!!!

That is it exactly. The documentation was not clear at all on this. =
Thank you very much, I would have never been able to figure that out =
from the docs.

Is there someplace to issue a bug report against the documentation?

-Silas

>This possibility hadn't occurred to me.  Good thinking.
>
>
>
>--=20
> Phil Stracchino       phi...@sp...
>    Renaissance Man, Unix generalist, Perl hacker
> Mobile: 603-216-7037         Landline: 603-886-3518
>