Networker SQL database backup forced to run level full
Summary: Networker SQL database backup forced to run level full
Acest articol se aplică pentru
Acest articol nu se aplică pentru
Acest articol nu este legat de un produs specific.
Acest articol nu acoperă toate versiunile de produs existente.
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
After
'nsrck -L6 client name'followed by
nsrinfo -n mssql clientnameand confirm save sets are being listed.
After
nsrck -L6the first backup would run level full and the consecutive backups would be incremental/logs only if scheduled correctly.
Additional Information
Ensure below is checked as well:
1) Database model is full
2) Previous DB full backup exists
3) The last backup on the database was performed by using NMM.
4) A log gap is not detected.
1) Database model is full
2) Previous DB full backup exists
3) The last backup on the database was performed by using NMM.
4) A log gap is not detected.
Produse afectate
NetWorker FamilyProprietăți articol
Article Number: 000055541
Article Type: Solution
Ultima modificare: 12 dec. 2025
Version: 5
Găsiți răspunsuri la întrebările dvs. de la alți utilizatori Dell
Servicii de asistență
Verificați dacă dispozitivul dvs. este acoperit de serviciile de asistență.