Unsupported savegrp option -o will be ignored NW 7.3.1

I have this error too WTF:

43708:(pid 10204):Start time: Fri Mar 24 10:04:21 2017

43621:(pid 10204):Computer Name: LEXSERV     User Name: SYSTEM

38571:(pid 10204): Bad switch: -o

38562:(pid 10204): Unsupported savegrp option -o will be ignored

100224:(pid 10204):Unable to proceed backup. Unsupported saveset specified

43709:(pid 10204):Stop time: Fri Mar 24 10:04:38 2017

Please check the NetWorker client, and look at what is in the backup command  as well as in the save operations field.

If possible, paste it here for review.

It could be that there is a blank character embedded in the save operations field.  If so, then blank would be acting like a delimiter, and causing NetWorker not to parse the field correctly.  If this is true, then surround the field with quotes.

Another troubleshooting step would be to run the backup from command line.  On the backup server, please start the group by:

  open a command line window

  run:  savegrp -v -c (client name) -l 0 > out.txt 2>&1

then look at the output file, and paste it here if possible,,, 

baa wrote: I have this error too WTF: 43708:(pid 10204):Start time: Fri Mar 24 10:04:21 2017 43621:(pid 10204):Computer Name: LEXSERV     User Name: SYSTEM 38571:(pid 10204): Bad switch: -o 38562:(pid 10204): Unsupported savegrp option -o will be ignored 100224:(pid 10204):Unable to proceed backup. Unsupported saveset specified 43709:(pid 10204):Stop time: Fri Mar 24 10:04:38 2017

What deserves WTF is your post :-D  I mean, from 2007 to 2017 it is 10 years... this message suggests you are using older module where when direct save (client direct) is disabled then via -o parameter to instruct module is passed, but if you run old enough module version then module won't understand it. 

NW server version 8.2.3 b. 1165

NW client version 8.2.4 b.1313

this is the parameter that is the likely issue:

     -o "\"REQUESTED_LEVEL:level=full;\""

Need to see where this is set.  As is stated earlier, please check the NetWorker SQL client, and look at what is in the backup command  as well as in the save operations field.  Pease paste it here for review.

From the output you provided, you see the message:  "See the file C:\Program Files\EMC NetWorker\nsr\logs\sg\Lexstest\758853 for command output"   ?  Please look at these output files for additional details on what the issue could be.

What is the NMM and SQL version on this SQL server?

Finally, try running the actual backup on the SQL server using the command:

nsrsqlsv -v -C -s bksrv-main-n1.bashneft.ru -a "DIRECT_ACCESS=No" -b Lexema_Pool -o "REQUESTED_LEVEL:level=full"  -l full  MSSQL#Group_UDNGKR:UDNGKR

If that fails, then try without the -o parameter:

nsrsqlsv -v -C -s bksrv-main-n1.bashneft.ru -a "DIRECT_ACCESS=No" -b Lexema_Pool  -l full  MSSQL#Group_UDNGKR:UDNGKR

What is the version of SQL module?

baa wrote: NW server version 8.2.3 b. 1165 NW client version 8.2.4 b.1313

Microsoft Windows [Version 6.3.9600] (c) 2013 Microsoft Corporation. All rights reserved. C:\Windows\system32>nsrsqlsv -v -C -s bksrv-main-n1.bashneft.ru -a "DIRECT_ACCESS=No" -b Lexema_Pool -o "REQUESTED_LEVEL :level=full"  -l full  MSSQL#Group_UDNGKR:UDNGKR 43708:(pid 15268):Start time: Wed Mar 29 10:42:27 2017 43621:(pid 15268):Computer Name: LEXSERV26-1    User Name: baa 38571:(pid 15268): Bad switch: -o 38562:(pid 15268): Unsupported savegrp option -o will be ignored 29446:(pid 15268):Local host has following SQL Server online: 37977:(pid 15268):              MSSQL server : LEXSERV26-1 passing null into one of the msg creation calls with msg id 100220 100220:(pid 15268):Saveset [null] validated. 38008:(pid 15268):An internal error occurred. nsr/db_apps/bsmsql/sqlutil.c(12421): SQL Server FILESTREAM Database called for database 'UDNGKR'96808:(pid 15268):Succes sfully converted from group id to AG name. 51340:(pid 15268):jobhandler(340): Created Job ID: 762832         Save command: nsrsqlsv -v -C -s bksrv-main-n1.bashneft.ru -a DIRECT_ACCESS=No -b Lexema_Pool -o REQUESTED_LEVEL: level=full -l full MSSQL#Group_UDNGKR:UDNGKR 85942:(pid 15268):Stopping Federated backup - ========== Slave backup with job id (762832) failed to start on node LEXSE RV26-1. Check if the user has sufficient permissions to run the job. Refer to NetWorker Server logs for more details. == ======== nsrsqlsv: MSSQL:UDNGKR level=full, 0 KB 00:00:05,  0-file(s)-processed, 1-file(s)-succeeded 43709:(pid 15268):Stop time: Wed Mar 29 10:42:51 2017 C:\Windows\system32>nsrsqlsv -v -C -s bksrv-main-n1.bashneft.ru -a "DIRECT_ACCESS=No" -b Lexema_Pool  -l full  MSSQL#Gro up_UDNGKR:UDNGKR 43708:(pid 16704):Start time: Wed Mar 29 10:42:59 2017 43621:(pid 16704):Computer Name: LEXSERV26-1    User Name: baa 29446:(pid 16704):Local host has following SQL Server online: 37977:(pid 16704):              MSSQL server : LEXSERV26-1 passing null into one of the msg creation calls with msg id 100220 100220:(pid 16704):Saveset [null] validated. 38008:(pid 16704):An internal error occurred. nsr/db_apps/bsmsql/sqlutil.c(12421): SQL Server FILESTREAM Database called for database 'UDNGKR'96808:(pid 16704):Succes sfully converted from group id to AG name. 51340:(pid 16704):jobhandler(340): Created Job ID: 762835         Save command: nsrsqlsv -v -C -s bksrv-main-n1.bashneft.ru -a DIRECT_ACCESS=No -b Lexema_Pool -l full MSSQL#Group _UDNGKR:UDNGKR 85942:(pid 16704):Stopping Federated backup - ========== Slave backup with job id (762835) failed to start on node LEXSE RV26-1. Check if the user has sufficient permissions to run the job. Refer to NetWorker Server logs for more details. == ======== nsrsqlsv: MSSQL:UDNGKR level=full, 0 KB 00:00:05,  0-file(s)-processed, 1-file(s)-succeeded 43709:(pid 16704):Stop time: Wed Mar 29 10:43:14 2017 C:\Windows\system32>

log from C:\Program Files\EMC NetWorker\nsr\logs\sg\Lexstest\758853

43708:(pid 14520):Start time: Tue Mar 28 08:34:15 2017 43621:(pid 14520):Computer Name: LEXSERV26-1     User Name: SYSTEM 38571:(pid 14520): Bad switch: -o 38562:(pid 14520): Unsupported savegrp option -o will be ignored 100224:(pid 14520):Unable to proceed backup. Unsupported saveset specified 43709:(pid 14520):Stop time: Tue Mar 28 08:34:24 2017

NMM for SQL - 8.2.4.0.1313

Note: i cant backup only this DB - UDNGKR , another system base i can backup.

I know that on SQL server  "always on" option is enabled.

Thank you for the output...  the first nsrsqlsv output confirms what I suspected ..  it does not know what the -o switch is...

     -o "REQUESTED_LEVEL:level=full"

But it shows a new issue:

        Save command: nsrsqlsv -v -C -s bksrv-main-n1.bashneft.ru -a DIRECT_ACCESS=No -b Lexema_Pool -l full MSSQL#Group

_UDNGKR:UDNGKR

     85942:(pid 16704):Stopping Federated backup - ========== Slave backup with job id (762835) failed to start on node LEXSE

RV26-1. Check if the user has sufficient permissions to run the job. Refer to NetWorker Server logs for more details. ==

So that is the bigger issue...   please look at the logs for more information...

And since this is a different issue than the -o issue... please start a new conversation... so that it is not mixed with the original post from 2007

Yup, that is classic where user used doesn't have permission to perform backup on secondary replica (on primary it will work just fine).