client is not properly configured on the NetWorker Server
On 10/26/11 2:18 PM, Tim Mooney wrote:
In regard to: Re: [Networker] client is not properly configured on the...:
Though, in my case, I have 4-6 clients that I have to do this for every
time I restart the NetWorker server (and have had ever since I upgraded
a year ago to 220.127.116.11) - It has persisted against all the best EMC
support people who are completely baffled about what is corrupted deep
down in the recesses someplace. I am currently running 18.104.22.168 on the
server and the clients and it still persists for this same set of
clients every time I restart the server.
By any chance, have you tried removing the nsrladb on one of the
*clients*? The information should be regenerated, though you may need to
delete the peer information for that particular client on the server.
Yes, we've removed the entire /nsr/res directory on the client, deleted the client index and
client definition on the server and two restarts later the problem is back. The only way we
have found so far to completely get rid of this problem is to delete everything on the server
(/nsr/res, /nsr/mm, and /nsr/index) and start over. We are convinced at this point that there
is something wrong deep inside the server someplace.
However, we also believe (at least I think we do) that this is most likely a very unlikely set
of circumstances unique to our installation, given that we've been using NetWorker since 1994
and have migrated the /nsr directory from AIX, to Solaris, to Linux in that time frame - ie, a
lot of conversions - I have no idea what version of NW we started with in 1994, but I do know
this problem appeared in the middle of 7.5 (an upgrade from one cum fix level to another is
when it came to light in November 2010).
I absolutely do not intend this to be a complaint - EMC has worked diligently trying to figure
this out with me.
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER