Unsolved
This post is more than 5 years old
1 Rookie
•
25 Posts
1
1502
August 29th, 2018 07:00
Using a different NMC
Hi,
In our NetWorker datazone we have two NMC's, one which was installed locally on the backup server at installation time and a separate NMC installed on a dedicated VM. The intention at the time was to use the NMC on the VM, this can currently see the production backup server, however as it happened it was the local NMC on the Backup Server which was used to manage the backups.
We are now looking at installing a second backup server and want to use the dedicated NMC VM to manage both servers.
When connecting to the Backup server via the dedicated NMC all the jobs show as never run. How can we start using the dedicated NMC while retaining all the information of the jobs previously run from the locally installed NMC? Is it just a mater of coping the relevant DB's across to the dedicated NMC?
Thanks in advance
Deb_PS
156 Posts
2
August 30th, 2018 05:00
I am under impression that you are using NetWorker 9.x family if so the NMC Authentication is handled by the AuthC server, and AuthC installed by default with NetWorker Server binaries in Windows, in Linux you cannot install NetWorker Server without AuthC as well.
As a result, both the NetWorker Server is having AuthC installed and running, so the when you have a single dedicated NMC to handle authentication it is not known which AuthC will handle the authentication request, so this issue is happening.
1. Customer is having two Networker servers one in location A named nw1 and another in B location named nw2. He wants to setup a dedicated NMC server NMCsvr on another server to monitor/operate the two networker servers nw1 and nw2.
2. Customer runs the following command on both the Networker servers
nsrauthtrust -H nwserver_name -P 9090
But after doing step 2 he is only able to manage one Networker server at any point in time. He gets the pop up saying failed to authenticate security token.
RESOLUTION:
Customer first needs to decide one Networker server which will act as the Networker Authentication Service host. In our case we choose nw1 as the Networker Authentication Server host
The issue was that
- Server nw2 does not trust (and does not know how to decode) the token issued by the server nw1.
- So on the server nw2 they need to run nsrauthtrust -H nw1 -P 9090. Then the token issued to NMC by logging in to authc on nw1 will be trusted and readable by nsrd on nw2.
After that we need to use the nsraddadmin command to grant the NetWorker Authentication Service user groups access to the NetWorker server.
nsraddadmin -H Authentication_service_host -P Authentication_service_port_number
In our case nw1 is the Authentication service host and the command should look like
nsraddadmin -H nw1 -P 9090