sql db client initiated backups are not working with NMM MODULE

Did this ever work before?

What about standard file backups of this client?

 

Assuming the message "Unable to identify NetWorker Server Version.Status" is correct, it seems as if the client cannot establish a connection to verify the resource details. This looks more to either a generic connection or firewall problem.

From both sites, you should run the command

   nsradmin -p nsrexec -s [server | client]

to verify that the other site will answer correctly.

 

with client initiated backups, do you mean using the "Microsoft SQL Ad-hoc plugin" or rather the nsrsqlsv cli?

"NMM Microsoft SQL Server Management Studio (SSMS) plug-in GUI: This user interface uses the VDI technology to backup and recover the supported versions of SQL Server. The NetWorker Module for Microsoft for SQL VDI User Guide provides more information.

NetWorker SQL Ad-hoc plug-in: You can install the NetWorker SQL Ad-hoc plugin during the NMM installation. This plugin enables the user to perform manual backups and recoveries from the Microsoft SQL Server Management Studio GUI. The NetWorker Module for Microsoft for SQL VDI User Guide provides more information."

Is lnxvib120.internal.draexlmaier.com the NW backup server, as it states trying to connect to it? How did you select the NW server to use?

An unrelated KB article (000115431) about Exchange backups using NMM states the "Failed to get nsr attribute version for server" due to:

Cause

The user does not have "Monitor NetWorker" privilege.

Resolution

Add "Monitor NetWorker" privilege to the user performing the recovery operation.

hello , 

thanks for the reply .

this was never working .

standard file backups of this cluster are working .

nsradmin -p nsrexec -s [server | client] is working in both directions .

for firewall blocking possibility , i disabled the internal firewall in the windows cluster and i checked with network team if there is a firewall rule blocking the traffic from the client to the backup server , but it is not .

the range of the nsrports activated on  the client is 79-37  to 99-36.

 

I'm always getting this message :

44504:nsrsqlsv:common\apputil(360): Failed to get nsr attribute version for server lnxvib120.internal.draexlmaier.com
passing null into one of the msg creation calls with msg id 148692
148692:nsrsqlsv:D:/views/nw/19.5/nsr/db_apps/bsmsql/sqlutil.cpp(16270): Unable to identify NetWorker Server Version.Status: 0x0000000d
Server: null
44504:nsrsqlsv:common\apputil(360): Failed to get nsr attribute version for server lnxvib120.internal.draexlmaier.com

Do you have other ideas that we can test ?

 

 

 

nsradmin -p nsrexec -s [server | client] is woking in both directions 

Unfortunately not. Let me suggest that you contact support to find out what exactly triggers this message.