Hello,
I'll put my answer to Phil's post here... it just fits better.
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:
select * from FileSet;
+-----------+------------------+------------------------+---------------------+
| FileSetId | FileSet | MD5 | CreateTime |
+-----------+------------------+------------------------+---------------------+
| 4 | LinuxOrk | M7+oT5+Nb8+0B/dJ7x+ZtB | 2004-09-11 22:56:36 |
| 10 | LinuxTrollHome | SF/at7+sF60rfSdGm8JTKC | 2004-10-06 23:06:24 |
| 12 | Mail | 2Q+hw9/cjF+V7+kmX5/iBC | 2004-11-01 02:59:04 |
| 17 | Catalog | u7/syB/mq5sUOnRVt+/qYA | 2004-11-01 16:25:01 |
>...
That would be worth a look at the code...
Now, on to Silas' original question...
On 29.09.2005 19:38, Bennett, Silas (GE Infrastructure) wrote:
-----Original Message-----
From: Phil Stracchino [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 28, 2005 12:50 PM
To: Bennett, Silas (GE Infrastructure)
Cc: [email protected]
Subject: Re: [Bacula-users] Differentials Jobs referencing obsolete Full
Job
Bennett, Silas (GE Infrastructure) wrote:
Is it possible that Bacula's Diff jobs are purposefully not referencing
a "Good" Full backup because of the mail warning?
In short, no. Bacula is referencing a Full backup that it believes to
be good; if it's not good, then Bacula doesn't know it isn't. Why this
may be is hard to say at this point.
The Full backup it is referencing "_IS_" good, but it is old. As a result the
differentials are much bigger than they need to be. My question is why is it referencing
an old Good Full backup verses a new Good Full backup?
What you could try, assuming you have a newer Full backup based on the
same Filesets, is to manually delete the old Full job. This should
either force it to work from the newer Full or, if the more recent Full
was somehow made against a different Fileset than is currently being
used, will force a new Full backup.
I will backup my catalog, and try this. The file sets between the Full and Diff
jobs are the same, so I don't think that is the issue.
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.
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.
Arno
--
IT-Service Lehmann [EMAIL PROTECTED]
Arno Lehmann http://www.its-lehmann.de
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
