MSSQL strange behavior

[Pancevo1956]

I have set up Networker to back some ordinary files. It works. The Schedule is full only on Suday while the rest of the week is inc. That is not the case for MSSQL:nameoddata base, because each day I am getting full backup with inc backup immediately after 8 minutes mminfo screen output


A00009 node2.fplus.local 8/5/2009 2326 MB full MSSQL:fptopup
A00009 node2.fplus.local 8/5/2009 412 B incr MSSQL:fptopup
....
A00009 node2.fplus.local 8/7/2009 2365 MB full MSSQL:fptopup
...
A00009 node2.fplus.local 8/7/2009 412 B incr MSSQL:fptopup
...
A00009 node2.fplus.local 8/8/2009 2381 MB full MSSQL:fptopup
...
A00009 node2.fplus.local 8/8/2009 412 B incr MSSQL:fptopup
...
A00009 node2.fplus.local 8/9/2009 2395 MB full MSSQL:fptopup
...
A00009 node2.fplus.local 8/9/2009 412 B incr MSSQL:fptopup

Am I missing something? The schedule works fine for non MSSL like work set. Why?

 

[JohnPlayerSpecial]

If MSSQL recovery model is set to simple, backup is always forced to full. What I learned from EMC Powerlink that 412 B incremental saveset is somekind of metadata and will always appear wit MSSQL backups.

Check your MSSQL recovery model. Allthough few times I have experienced that some SQL instances will always perform full backup even if recovery model is something else than simple. Maybe I have to update NMSQL.