Symptoms

Networker SQL data base backup forced to run full when backup level was set to incremental/logs only.Warning in nsrsqlsv log: (pid7004) NSR critical 39 Failed to find matching recover object. (pid7004) NSR info 75 No full backupset was found for "database name" Backup level forced to database full

Cause

Indexes for the client not getting generated on the networker server. Messages in daemon logs of the networker server: File_index notice Notice: the index header for client is currently unavailable

Resolution

Run 'nsrck -L6 client name' followed by nsrinfo -n mssql clientname and confirm save sets are being listed.After nsrck -L6 the first backup would run level full and the consecutive backups would be incremental/logs only if scheduled correctly.

Support Cases