Unsolved
This post is more than 5 years old
79 Posts
0
4207
December 3rd, 2014 10:00
SQL DB backups are failing with error "Failed to get nsr attribute version for server " & "Invalid pool name "
Hi All,
Has anyone ever encountered this error when running SQL DB backups (initiated by DBA)
Networker Server Version : 8.1.1.2.Build.280 Enterprise Edition
OS : Linux RHEL 5.10
Client Networker Version :8.1.1.2.Build.280
NMM : 3.0 Sp1
DBA is using the below command
nsrsqlsv -s NWSERVER -C -a"device interface=data domain" -gXYZ -bXYZ MSSQL:DBNAME
-------
43708:(pid 19108):Start time: Wed Dec 03 11:50:27 2014
44504:(pid 19108):common\apputil(353): Failed to get nsr attribute version for server NWSERVER
passing null into one of the msg creation calls with msg id 46166
46166:(pid 19108):nsr/db_apps/bsmsql/savemain.cpp(2244): Unable to identify NetWorker Server Version. Status: 0x0000000d
Server: null
29331:(pid 19108):Invalid pool name XYZ
Backup operation finished with error(s). Refer to the module backup log file for details.
43709:(pid 19108):Stop time: Wed Dec 03 11:50:29 2014
We do have the pool name XYZ. this was working fine until few days ago.. but something is changed recently ..
all the DB backups going to this networker server are failing so somewhere there is a common problem affecting multiple backups.
Any suggestions would be greatly appreciated.
ble1
2 Intern
•
14.3K Posts
0
December 3rd, 2014 10:00
Check DNS and auth peers.
ble1
2 Intern
•
14.3K Posts
0
December 3rd, 2014 11:00
Auth peers?
new2prog2
79 Posts
0
December 3rd, 2014 11:00
Forward and backward DNS is not a issue. Also I reverted the nsrauth to oldauth and it seems to be not supported on 8.1.1
so I reverted back to nsrauth as per below link
https://emc--c.na5.visual.force.com/apex/KB_BreakFix_1?id=kA1700000000WO4
Windows servers were patched recently..so not sure what is causing this problem..
new2prog2
79 Posts
0
December 3rd, 2014 12:00
We had conflicting peer information for one db client that I deleted it.
is that what you meant by auth peers ?
new2prog2
79 Posts
0
December 3rd, 2014 12:00
Are you suggesting to path the networker server from where we are (lgtoserv-8.1.1.2-1) ? If so what version are you recommending ?
I can completely uninstall a client and re install the s/w will that help ?
ble1
2 Intern
•
14.3K Posts
0
December 3rd, 2014 12:00
Yes. I would update server (most likely not related, but it is low on patch list) and I would try to re-init nsrladb on client. Note, this will also cause a need to remove older nsr peer for client in question.
ble1
2 Intern
•
14.3K Posts
0
December 3rd, 2014 13:00
It's not just lgtoserv... it is remaning 3 packages too (lgtonode, lgtoman and lgtoclnt). You can see patches here - so make your own pick:
ftp://ftp.legato.com/pub/NetWorker/Cumulative_Hotfixes/8.1/Cumulative_8.1_Readme.txt
On client side you can also update it. Then you can stop services, remove nsrladb, start it and new nsrladb will be created. On server, remove peer information for client.
bingo.1
2.4K Posts
0
December 3rd, 2014 21:00
Be careful - NW is picky with pool & group names.
Carefully look for lower/upper case letters and use these names exactly as they exists.
new2prog2
79 Posts
0
December 4th, 2014 06:00
well these backups were all working fine before few days..so something is changed.
Definitely not on networker app side but some patches or something else .
So at the moment I am holding on to changing the NW code on client or server..
thanks for all your suggestions.. I will see what CS has to say and let you know.
CarlosRojas
1.7K Posts
0
December 9th, 2014 06:00
Hi new2prog
Can you make sure there is blank space between the arguments and the values? for example -gXYZ should be -g XYZ
Also, make sure the nsr peer information is deleted on server for clients and on clients for server.
Have you tried to run the group with savegrp -D3vvv -l full group_name ?
Thank you,
Carlos
elvinperez
87 Posts
0
December 9th, 2014 11:00
Hi,
Please verify the pool name XYZ, the pool is case sensitive.
u can used the networker module for SQL Server and send the backup specified the pool name in the properties.
Elvin..
new2prog2
79 Posts
0
December 10th, 2014 06:00
well the command is now working after placing a space after "-b" poolname but not working in conjunction with -g "groupname"
So CS is looking into this at the moment.
crazyrov
4 Operator
•
1.3K Posts
0
December 10th, 2014 06:00
new2prog
The error also states that it was not able to ge the server version. Is the NetWorker server name used in the command correct. Have the DBA run the manual backups using the NMSQL user interface on the client machine. There is an option to select the target pool from this user interface.
CarlosRojas
1.7K Posts
0
December 10th, 2014 06:00
Just tested it and works fine, use this command:
nsrsqlsv.exe -s nw_server -g group_name -b pool_name -l full MSSQL:DB_name
Sorry, no -N required.
Thank you,
Carlos
new2prog2
79 Posts
0
December 10th, 2014 06:00
Yeah but it is working with only -b pooname for some reason the -g groupname is not working.
I think nsrsqlsv is sensitive to the sequence of switches that we pass on i.e -S -s -b -g