Unsolved

This post is more than 5 years old

1648

August 16th, 2010 10:00

Installed NMM after removing NW Client

Hi

     I am new with NW and have few questions. I had NW client 7.6 installed and runing on one of our servers(W2K8 SP2). Because of other apps on the server I decided to uninstall NW client and install NMM 2.2.1 On the NW admin console the client would not connect and I would get the "Unable to connect to host: Please check networker security settings and deamon logs on the networker client and Console server for more details." I looked the best I could and saw no errors. I deleted the client on the console and tried to re-install it with the client wizard and I get the same error. The admin console sees the client server because in the Networker version line in the wizard it show rb_nmm22_sp1 Build 95. Which is the new install. I click on next and get the same error again. I am sure it is some simple step I am missing. Something to do with authentication maybe? Any ideas?

Thanks.

79 Posts

August 16th, 2010 11:00

Hi,

I think your nsrladb database got corrupted. Kindly refer the KB article :esg103363 for more details and follow the steps given in the article for recreating nsrladb database.

http://solutions.emc.com/EMCSolutionView.asp?id=esg103363&usertype=C

Thanks

Pradeep

August 16th, 2010 12:00

Hi Pradeep,

     I gave it a try and it made no difference I get the same error. Anything else you can think of?

August 16th, 2010 16:00

Is the Networker service running on the backup client?

August 17th, 2010 04:00

Hello all,

If I understood well the issue comes up when you try to configure a client using the NMC (Networker Management Console) wizard, right?

NMM is based on VSS service, so the way to get the valid save sets to configure the client is using the nsrsnap_vss_save command. Please check the following solution:

http://solutions.emc.com/emcsolutionview.asp?id=esg114320

As that command has to be ran on the client, Networker Server is not able to retrieve the data to be backed up on the client, that's why you get that error message.

To configure the NMM client please follow the steps described in the above solution and then configure the client manually in NMC GUI.

Thank you.

Carlos.

August 17th, 2010 05:00

Hi to all,

David: yes the service is running.

Carlos: I followed the article and issued the command. The save set list came up no problem. If I create the client manually, I see the name resolves in Aliases under Global's 1 of 2 tab, but if I try to change the save set I get the same error again. I noticed under the clients information on the admin page that the Backup type does not populate.

Something I did not mention in my initial request was that when I uninstalled the client on the server, I deleted the Legato directory as well. I think I should not have if I was to put in another client. As it is a new install I was not worried about it. Should I have deleted it?

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

August 25th, 2010 04:00

My understanding of NMM is that it replaces client so you do not need it on system.  In such case, deleting its folder sounds ok to me.

I still didn't pay with NMM, but I plan to soon just to get granular AD backups and restores.

August 25th, 2010 05:00

Hi,

No problem at all deleting those folders. I would say that, if you deleted the client in NMC, there is still some info still present on the res configuration folder on NW server.

I would suggest you to delete the nsrladb folder in server and client (with services stopped) and also to delete the peer informaiton in both, client and server.

You can do it as follows. In the client:

nsradmin -p nsrexec

nsradmin>. type: nsr peer information

Current query set

nsradmin>delete

delete?

Hit yes+Intro as many times as you are prompted to

In the NW server:

nsradmin -p nsrexec

nsradmin>. type: nsr peer informaiton

Current query set

nsradmin>print

.

.

.

.

delete name: client_name

delete resource....?

y+intro

Then Stop NW services in the client and delete the /nsr/tmp folder, then start services again.

Let us know how it goes.

Thank you

Carlos.

August 25th, 2010 23:00

Hi! Have the same problem, tried this solution, now it's an another error: "Unable to connect to server". All networker services are running.

0 events found

No Events found!

Top