17 Posts
0
1134
November 20th, 2019 19:00
Missing Microsoft Exchange Server on Available Application, NW 18.1
Hi all,
I was checking out my configuration of Networker Server Client when I discover the Microsoft Exchange Server is missing on the Client Backup Configuration.
When I testing to run configure new client for all of the DAG Client, None of the DAG member client have the Microsoft Exchange Server selection on the Available Application column.
The backup is already running and there is no failure in backup and restoration testing during the time of discovery of this incident.
The only changes so far was a reboot of the Exchange Server that cause the nsrexecd on the primary NMM client to be down ( another reboot to resolve it) and authentication issue ( resolved by delete the peer information between client and server )
crazyrov
4 Operator
•
1.3K Posts
1
November 22nd, 2019 19:00
Renaming the nsrladb folder that is inside the res folder is never recommend. Bring back the old and delete the peer information again, this should help.
crazyrov
4 Operator
•
1.3K Posts
1
November 21st, 2019 00:00
@AL_IST
By any chance did you delete/rename the nsrladb on the client during your troubleshooting of other issues ?
bingo.1
2.4K Posts
1
November 21st, 2019 02:00
I just wonder what has happened for this issue to occur.
Anyway - if a resource has been deleted may I suggest that you open the file rap.log which should contain the last configuration.
To start/stop/restart the NetWorker services you must not necessarily reboot the system.Just do it from the services.msc Windows admin GUI or from the command line: net stop|start nsrexecd.
AL_IST
17 Posts
0
November 21st, 2019 18:00
To start/stop/restart the NetWorker services you must not necessarily reboot the system.Just do it from the services.msc Windows admin GUI or from the command line: net stop|start nsrexecd.
I did try the above but the error the services failed to start up. Only by rebooting the Client, the nsrexecd manage to start up again.
AL_IST
17 Posts
0
November 21st, 2019 18:00
Well, I actually rename the res and tmp folder when the nsrexecd having the issue. This itself that cause the
Authentication error = invalid client credential
And I resolve this by going to the following on client and server. However the client side was already empty "p type:nsr peer information"
nsradmin -p nsrexec
nsradmin>p type:nsr peer information
nsradmin>delete
Delete?y
nsradmin>q
AL_IST
17 Posts
0
November 24th, 2019 20:00
Sure. I will try it out on after I secure an appointment