Hi,

30.05.2008 23:16, Harik wrote:
> On Wed, May 28, 2008 at 3:17 AM, Arno Lehmann <al AT its-lehmann DOT de> 
> wrote:
>> Hi,
>>
>> If you just added the "Ignore Fileset Changes" setting, that's the
>> reason... this is considered a fileset change, and thus the next
>> backup will be upgraded.
> 
> That's probably what it was, thanks.
> 
> I ended up wiping everything - the database, the old volumes, the
> status, started from scratch.
> 
> It seems to be working properly now - as long as "Base" isn't supposed
> to be considered "Full".  From the documentation, it indicated it was
> used to save tape space - but the next job after a Base was promoted
> to Full.

Currently, only the three levels Full, Differential and Incremental 
are implemented for backup jobs.

"Base" is only defined, but not yet fully implemented.

Arno

> No fileset changes, I just ran them back-to-back.
> 
> A third run correctly did an incremental, so it's looking good now.
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Bacula-users mailing list
> Bacula-users AT lists.sourceforge DOT net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
> 

-- 
Arno Lehmann
IT-Service Lehmann
www.its-lehmann.de

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users