john.riordan

updated

12 years ago

0

4333

April 1st, 2015 06:00

Must have the operate networker privilege???

Hi

I am trying to do a restore of an exchange database but I am getting "must have the operate networker or recover local data privilege for the client".

I have *@* in the remote tab  + username @client

the user logged in is a domain user can someone help me - I think this user needs to be added to the networker admin group but I do not have any idea how to do this

even though it is a domain account will username@client suffice ?

many thanks

john

  • nmc2

    268 Posts

    3488

    0

    Posted April 1st, 2015 06:00

    Use 'nsraddadmin' command to add the user to NetWorker server administrator group.

    syntax : nsraddadmin -u user@client

  • CarlosRojas

    1 Rookie

    •

    1693 Posts

    3488

    1

    Posted April 1st, 2015 06:00

    Hello johnrio1 

     

    This means that inside NetWorker, that user do NOT have the "Operate NetWorker" privilege, and in the documentation it is explained.

     

    So, in order to do that you would need to go to NMC (NetWorker Management Console), and add the user (the same user you have configured as logon in the Exchange server, for the Replication Manager Exchange Interface service) to the following NetWorker groups:

     

    Database administrator

    Application Administration

    Backup Operators

     

    Enough by adding *@hostname  of all Exchange nodes, including the DAG

     

    That should be enough for you to perform the restore.

     

    Thank you,

    Carlos

  • 3488

    0

    Posted April 1st, 2015 06:00

    Thanks Guys

    working now

  • MeemerK

    3 Posts

    3223

    0

    Posted August 15th, 2019 07:00

    Related is when you get permission errors like this while simply adding a client to networker server. You can get this error (privilege "Operate Networker" missing) from simply having connectivity issues to port 7937 for example. And you can also get errors like "No File or Directory" or something to that effect as well. Bottom line is the developers of this software need to do a MUCH better job of error handling. They're clearly swallowing real java exceptions and causing cascading error conditions that don't make sense to the end user. < > Never swallow java exceptions. Throw them up and terminate the **bleep** process if needed, but don't swallow them please -- for the user's sake!! Hire more skilled Java programmers if you need to. This is just nuts and makes learning and using Networker much more difficult.