Unsolved
This post is more than 5 years old
8 Posts
0
3251
SQL backup fails after upgrade to Networker 7.5
After upgrading our Networker server from Networker 7.3 to Networker 7.5, one of my SQL backup keeps failing. Networker keeps telling me 'The feature "NetWorker Module for Microsoft SQL Server" is not properly enabled', but nothing has changed.
* :MSSQL: savegrp: suppressed 72 lines of output.
* :MSSQL: 29085 1271833745 5 0 0 4276 3952 0 (pid3952) 36 Microsoft SQL Server Provider error: 0
* :MSSQL: 38006 1271833745 5 0 0 4276 3952 0 (pid3952) 3 %s. 1 24 123 Write on 'Legato#498ce3e8-57c8-4c1c-b888-874ecd21d975' failed, status = 995. See the SQL Server error log for more details.
* :MSSQL: 38006 1271833745 5 0 0 4276 3952 0 (pid3952) 3 %s. 1 24 42 BACKUP DATABASE is terminating abnormally.
* :MSSQL: 53084 1271833745 5 0 0 2348 3952 0 (pid3952) 47 Processing %s failed, the item will be skipped. 1 0 4 pubs
* :MSSQL: 0 1271833745 1 0 0 2348 3952 0 (pid3952) 88 %s%s: %-*s%s%s%s %*s %2.2ld:%2.2ld:%2.2ld, %ld-file(s)-processed, %ld-file(s)-succeeded 14 0 0 0 8 ezistsql 1 2 21 23 6 MSSQL: 0 7 level= 0 4 incr 0 1 , 1 1 9 0 4 0 KB 2 1 0 2 1 0 2 1 3 2 2 11 2 1 0
* : Backup operation finished with error(s). Refer to the module backup log file for details.
rovinabi
55 Posts
0
April 21st, 2010 09:00
Hi,
The message "'The feature "NetWorker Module for Microsoft SQL Server" is not properly enabled'" is displayed in the xbsa.messages when there is no license available for the SQL module. Check if the SQL server is using the lisence for NMSQL in NetWorker by running the command "nsrlic -v".
HTH,
Rovin D'Souza.
tomvr22
8 Posts
0
April 28th, 2010 02:00
At first it was using the license, so i removed the client and added it back again as a new client. When I run 'nsrlic -v' it is not using the license anymore. Still can't figure out what went wrong. I've got two SQL licenses and only two SQL clients, one keeps failing.
fizelsche
37 Posts
0
April 30th, 2010 04:00
Hi,
after we upgraded to the verison 7.5 we got some smillar error messages and we upgraded th SQL Modul up to the latest version.
After we had done that the backup has gone at the right way again.
Ciao Jens
tomvr22
8 Posts
0
May 3rd, 2010 05:00
I've already tried an upgrade to the newest SQL module, didn't solve the problem. Even tried a downgrade of the SQL module, didn't solve the problem either.
The file backup of the physical and virtual clusternodes are succesfull, it's just the SQL backup that fails. Seems like a licensing issue, so just gonna try to contact technical support to solve the problem.
Thanks for your replies
Tom
axavier1
76 Posts
0
May 3rd, 2010 08:00
Hi,
We have a similar issue here after NW upgrade with NMO for Linux, the solution was delete from NW server both client physical nodes and the virtual client and re-create all clients again, after that the NW server begun allocate the licenses correctly.
Regards.
ble1
14.3K Posts
0
May 4th, 2010 13:00
Probably your license is allocated to wrong node... given this is cluster. nsrlic -v might show that too.
tomvr22
8 Posts
0
May 28th, 2010 04:00
you're right. The license is allocated to wrong clusternode. Do you know how to solve this?
BSequeira
30 Posts
0
May 28th, 2010 07:00
Hi Tom,
The new version of NMSQL has probably solved the issue, but you still need to re-assign the licenses.
Try the following:
- Open the Physical nodes configuration in NW (Client Configuration) and check info&licensing tab, you will probably see the SQL licenses assigned in there when it should have NT licenses.
- Go to regstration in Networker server
- Locate the SQL licenses and copy the Enabler code and Auth Code from those licenses in a txt file.
- Delete the SQL licenses
- Stop NW and rename nsrlabd, its not mandatory, but its make sure all info stratch from scratch regarding the clients.
- Start NW and apply the SQL licenses again with the Enabler and Auth code for each one.
- Start a SQL backup and check if the licenses were assigned to the correct nodes, using nsrlic -v, you should see 2 licenses used by the SQL nodes.
Hopefully it will all be sorted after this process.
Regards
Bruno
elvinperez
87 Posts
0
May 28th, 2010 10:00
Hello,
It is advisable to make an upgrade from version 7.3 to version 7.5 you must perform the first upgrade from 7.3 to 7.4.x then 7.5.x, is probably why the application is not recognizing the license of SQL you have available.
Regards,
tomvr22
8 Posts
0
June 2nd, 2010 01:00
After deleting and re-adding the physical clusternodes in Networker, everything was back to normal. Thanks for your help.
Tom