Start a Conversation

Unsolved

T

1 Rookie

 • 

10 Posts

790

December 20th, 2022 02:00

Backup level 'MSSQL:' is obsolete. Change the backup level to logs only and restart

Hello guys . Recently I had a problem with an MSSQL database backup with incremental level 

networker version on both the backup server and client is 19.5.07 

NMM is 19.5 as well 

windows is server 2012 R2 

The backup only works on logs only and full backup .  not incremental or cumulative incremental 

any idea why suddenly it requires me to change to logs only ?  

thanks 

 

Check the detailed logs at 'C:\Program Files\EMC NetWorker\nsr\applogs\nsrsqlsv.log'.

Version information for C:\Program Files\EMC NetWorker\nsr\bin\nsrsqlsv.exe: Original file name: nsrsqlsv.exe                Version: 19.5.0.Build.166 (ntx64)              Comments: Supporting Microsoft Volume Shadow Copy Service

 

 

 

 

157931:nsrsqlsv:Backup level 'MSSQL:' is obsolete. Change the backup level to logs only and restart the backup.

37758:nsrsqlsv: Usage: nsrsqlsv [] {path}

options: [-CGjqRTvkuHXZ] [-A SQL virtual server name] [-s NetWorker Server]

         [-c NetWorker client] [-N name] [-b pool] [-g group]

         [-S count] [-l level] [-m masquerade]

         [-O "sqlOption1[,sqlOption2][,...]"]

         [-D debuglevel] [-I ]

         [-U ] [-P ]

         [-h "DB_to_exclude1[,DB_to_exclude2][,...]"]

         [-h ["DB_to_exclude_wildcards"]]

         [-f aes] [-w browse] [-y retention]

         [-a ]

path:    d-path | i-path

d-path:  MSSQL: | [MSSQL:]s-path [[MSSQL:]s-path [...]]

i-path:  MSSQL$inst-name: | MSSQL$inst-name:s-path [...]

s-path:  database | database. | database.filegroup |

         database.filegroup. | database.filegroup.file

Stop time: Mon Dec 19 15:18:10 2022

 

 

 

 

2.4K Posts

December 20th, 2022 03:00

1 Rookie

 • 

10 Posts

December 20th, 2022 03:00

The only supported levels are ( FULL, Logs Only, Cumulative Incremental )

the only backup working is full and logs only . 
but it was working on cumulative incremental since last sunday. 

so I dont know why the sudden change . 

4 Operator

 • 

1.3K Posts

December 27th, 2022 21:00

@teie , Can you check the backup command again in your client configuration. Someone might have changed some configuration or added a a `-l` to the backup command for some reason. Sharing the complete log from one of the failed runs would help us get a better picture of what is happening. 

No Events found!

Top