2.4K Posts

September 19th, 2014 07:00

Your summary is fine although there are some issues which i want to clarify:

Q7/A7

   nsradmin is part of the NW client package that's why you can run it on each NW client.

Q2/A2

    With respect of the certificates - these are handled by the NW client daemon (nsrexecd) thats why you must run:

       nsradmin -p nsrexec   -s      

       nsradmin -p nsrexecd -s       will also be o.k.

   Of course, the NW server has also the client package installed.

Q6/A6

   Actually, the dot (like in ". type ...") is the command for a query of the resourse database.

   Run "help" to see a list of all commands.

Q4/A4

   I am not sure whether you must reboot the server - restarting NW should already do the job.

BTW

  - nsradmin -p nsrexec -s       connects to the 'client side resource db'  (/nsr/res/nsrladb)

  - nsradmin                   -s     connects to the 'server side resource db' (/nsr/res/nsrdb)

    Of course you must be an administrative NetWorker user.

  - Even if you deal with a NW server for UNIX/Linux i recommend to use nsradmin from a Windows machine.

    You will love the command buffer ... which even remains when you dropped the connection in the interim.

4 Operator

 • 

14.4K Posts

September 19th, 2014 07:00

A4 - you mean after restart of nsrexecd and not reboot of the server....

No Events found!

Top