Hello,

Most likely you edited the .conf file and modified the
FileSet.  If that is the case, listing all the FileSets recorded
in the database will show multiple copies of the FileSet
record with different hashes.

In most cases, other than changing the FileSet, Bacula
clearly indicates why it is upgrading a level.  In the case
of a FileSet change, it prints a notice saying something
like a valid Full could not be found.

The probability that there is a new bug introduced between
5.2.1 and 5.2.2 is probably about 0.0001% since there were very
few coding changes except for bug fixes.

Regards,
Kern

On 11/30/2011 07:55 PM, Stephen Thompson wrote:
>
> FYI
>
> Not sure if anyone's seen or reported this, but I upgraded from 5.2.1 to
> 5.2.2 yesterday and during my backups last night, several jobs were
> promoted from Incremental to Full, even though their job configurations
> had not changed and they did have a valid Full backup from last week.
>
> I have never seen this happen before with bacula in general or my
> configuration in particular, so I thought it might be possible that a
> bug was introduced into 5.2.2.
>
> thanks,
> Stephen


------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users