Seems that you have a communication issue , ( IP and naming resolutions problem ) , try to double check firstly that the communication between those two server are perfect, if it is like that. you have to to add in users field, through NMC, in administrators list user=root,host=sonl01bkp002.global.aes.com as mentioned by CarlosRojas.
Also be aware that upgrading to supported version is very important, you have to plan for that soon.
In the past issue like this has been seen where certain Linux clients would have name in /etc/hosts listed under 127.0.0.1 instead of localhost. In that case index of that linux client would go under name of the backup server and would create pretty much a mess. Your issue does reassemble something like that. Otherwise it is some name resolution issue (though what I said is name resolution issue too).
vishwanathkrish
75 Posts
1
February 22nd, 2012 18:00
Hello Louis,
Try performing the following steps on the client machine .
1. Remove the client's shortname from the loopback entry in the /etc/hosts file.
2.Rename nsr/res/nsrladb on the client and restart Networker services.
One more thing, Networker version 7.4 is no more supported , so upgrade networker version to the latest version
Regards,
Vishwanath
CarlosRojas
1.7K Posts
1
February 23rd, 2012 00:00
Hi Louis,
This means that user "Root" on server "sonl01..." has no permissions granted, and is not able to save the indexes.
To solve this issue ensure that the user root@sonl01bkp002.global.aes.com is included in the Administrator's list of NetWorker server.
You can do it from NMC or by command line.
Command line:
nsraddadmin -u "host=sonl01bkp002.global.aes.com,user=root"
From NMC you can just go to Configuration->User Groups->Double click on "Administrators" and add in theright field root@sonl01bkp002.global.aes.com
Thank you.
Carlos.
Bebo2k
544 Posts
0
March 1st, 2012 15:00
Seems that you have a communication issue , ( IP and naming resolutions problem ) , try to double check firstly that the communication between those two server are perfect, if it is like that. you have to to add in users field, through NMC, in administrators list user=root,host=sonl01bkp002.global.aes.com as mentioned by CarlosRojas.
Also be aware that upgrading to supported version is very important, you have to plan for that soon.
Thanks,
Ahmed Bahaa
ble1
4 Operator
•
14.4K Posts
0
April 25th, 2012 03:00
In the past issue like this has been seen where certain Linux clients would have name in /etc/hosts listed under 127.0.0.1 instead of localhost. In that case index of that linux client would go under name of the backup server and would create pretty much a mess. Your issue does reassemble something like that. Otherwise it is some name resolution issue (though what I said is name resolution issue too).
DavidHampson-rY
294 Posts
0
April 25th, 2012 07:00
Check your /nsr/res/servers file has an entry for the backup server.