UNSOLVED

fx8282

updated

14 years ago

F

fx8282

38 Posts

0

5230

June 11th, 2012 05:00

Unable to browse save sets from client config window

I am unable to browse the client's filesystem/savesets from the client configuration window.

(Error attached)

Have already tried the following

- deleting the nsr peer information from the server

- renaming nsrladb from the client and restarting networker but still keep getting the same error.

1 Attachment

  • SurajPujari

    155 Posts

    1601

    0

    Posted June 11th, 2012 12:00

    Try doing a DNS query with both client and server at both the ends, also hav a check of Host entries at client and server.

  • CarlosRojas

    1 Rookie

    •

    1693 Posts

    1601

    0

    Posted June 11th, 2012 23:00

    Hi Fx8282,

    Is this Windows or Unix?

    If Windows, do you have NMM installed on that client?

    If NMM installed this is normal.

    Do you have Windows Firewall enabled?

    If enabled either disabled Firewall, configure manually the exceptions in Windows Firewall for NetWorker client or uninstall the software and reinstall it by selecting "Configure Windows Firewall".

    Besides ensure name resolution is correct as Suraj pointed out.

    Check the daemon.log in client and server to find out what is going on, in case none of the above applies.

    Thank you.

    Carlos.

  • fx8282

    38 Posts

    1601

    0

    Posted June 12th, 2012 21:00

    @Carlos- We have about 100+ clients with various flavors of Unix and Windows.

    All of them have the networker client alone installed. Some of them have modules installed but none have the one for MS apps.

    @Suraj- dns resolution seems to be fine with the NMC server, backup server and clients all having entries in each others host files as well

  • danag2

    20 Posts

    1601

    0

    Posted June 13th, 2012 05:00

    You get this error if strong auth is disabled and you are using old auth. Are there errors in the message log related to authentication?

  • fx8282

    38 Posts

    1605

    0

    Posted June 14th, 2012 05:00

    Hi Panwar,

    Have tried that for one client from backup server already.

    Let me know why I should delete it from the storage node???

  • Panwar

    79 Posts

    1605

    0

    Posted June 14th, 2012 05:00

    Hi,

    Kindly delete nsr peer information from NW server,all the Storage nodes configured on the NW server and NW client. Then try to browse the client.

    Regards

    Panwar

  • SurajPujari

    155 Posts

    1605

    0

    Posted June 14th, 2012 13:00

    Try adding a new instance for the client whose savesets u r not able to browse, also let me know what is the version of your Client and Server. Was there any recent change done in your environment that has caused this issue?

    Following are the possible reason for which we get the mentioned error:

    1. Either there is peer information mismatch

    2. Communication failure between Client and Server.

    3. Client-Server Version Mismatch.

    There might be something that is not known to me yet....

  • 1605

    0

    Posted June 21st, 2012 03:00

    Hi,

    Kindly delete the nsr peer information from the backup server, the client in question and the NMC server and the try to browse the file system. If you have firewall and restricted the ports, ensure that you have enough number of ports opened.

    HTH

  • ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    1605

    0

    Posted June 30th, 2012 08:00

    Just define it manually... the time and effort people spend on wizard problems does not stop to amaze me. You are way faster to define backup manually then using wizard (as it is really that simple... new client, save set, what group, what policy and click ok).

  • fx8282

    38 Posts

    551

    0

    Posted July 1st, 2012 23:00

    Very well said mate.. Thats how its been for so long and thats how it is right now..

    Its just a query a senior has raised and wants fixed for reason unknown