On Tue, 6 May 2008, Alan Brown wrote:

> On Fri, 2 May 2008, Steve Thompson wrote:
>
>> On Wed, 30 Apr 2008, Ryan Novosielski wrote:
>>
>>> Steve Thompson wrote:
>>>> Besides this, I have noticed (for every version since 1.38), that if a
>>>> full backup is run manually (via bconsole), then the next occurrence of a
>>>> backup for the same job always repeats the full backup, even if the
>>>> scheduled backup was incremental.
>>>
>>> This has not been my experience. You might want to try duplicating that
>>> and showing the status of your jobs and media to see if it needs to be
>>> fixed, or to see if it is pilot error and you might want to make a change.
>>
>> I can duplicate this any time I like; it is not pilot error.
>
> Is the incremental starting up _before_ the full backup has completed?

Ah, I had thought of that. No, it isn't. I force a full backup, it runs to 
completion, and then the incremental starts some time later, and is always 
upgraded to a full. I have done several different bacula installations, 
and it happens like this on all of them. On one setup, I have 50 backup 
jobs, and I certainly haven't tested all fifty of them this way, but the 
half dozen or so that I have tested all do this.

Also, if the director happens to be down when a full backup is scheduled, 
and the next run, when the scheduled backup is an incremental, does not do 
the missing full while the previous full is still in the database.

Steve

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users