Move a NetWorker clients from one NetWorker Server to another

Question

Hi we made a second NetWorker Data Zone for SAP Hana, because we are at the limit with saveset per day.

Now we have the Problem, that we can't move the NetWorker Clients to the new NetWorker Server.

We get in the Log from the client we try to backup the error

97512:savefs: Cannot access NetWorker server 'NW Server': Remote system error - Connection timed out

savefs Nw Server: failed.

we installed on one test windows client the NW Client totaly new and tried to open the Networker. When we choose the new Server we get following: "auhentication error why = server rejected credential"

Any idea what we made wrong, and how we can solve it.

Thanks and best regards

Martin

dean7 · Accepted Answer

Thanks for all of your answers! The problem was, that there SELinux was enabled... When we disabled that, NetWorker runs like we expected. Thanks again! dean

crazyrov · Answer

Hi @dean ,

First is there any firewall between the backup server and the client machine, if so start with applying rules on the FW.

If no FW then test communication using rpcinfo and nsradmin.

From client : rpcinfo -p backup_server_hostname

From Backup server : rpcinfo -p client_hostname

From client :nsradmin -s backup_server_hostname -p nsrexecd

From Backup server : nsradmin -s client_hostname -p nsrexecd

The output/error from the above commands should be able help you find the cause of failures.

Also, what version of NetWorker are you on. If 8.x, try renaming /nsr/res/nsrladb on the client while the services are down.

bingo.1 · Answer

Also make sure that the /nsr/res/servers file needs to be adjusted and the NW daemons must be restarted. I know the error message should be different but you never know ...

ble1 · Answer

auth error suggests issue with nsrla most likely which means you must clear that issue first.  Normally, if you stop nsr on client and delete nsrladb and then start it - that should do the trick (or you remove offending entry on the server).  As for timeout issue, check if client can communicate with server (network/firewall).

dean7 · Answer

Hi cracyrov

I tried your suggestions, the rpcinfo, looks good from both sides.

with the nsradmin I struggle a bit.

If i do on the client nsradmin -s backup_server_hostname -p nsrexecd

"NetWorker administrator program

Use the help cor command for help

when I try nsradmin then server backup_server_hostname i get following.

can't bind to

hostname: ^backup_server_hostname

onc program number: 390109;

onc version number : 2;

42503:nsadmin: Remote system error- Unknown error

when i do server backup_server_name -p nsrexecd I get
can't bind to

onc program number:390109;

onc version number: 2;

type: backup_server_name -p nsrexecd;

who this is helping me?

thanks

PS: Client is 8.2.1.6

dean7 · Answer

Hi Hrvoje i tried with de deletion of the folder, and i tried with the reinstallation of the NW client, but both things didn't helped. the servers file is correct.

dean7 · Answer

short update. we see in on the NW Server tcp6 when we make a netstat -tulpe is there any way to put that back tcp (tcp V4) Thanks

ble1 · Answer

That would be the case only if on OS level IPv4 is disabled and only IPv6 is enabled on client.  I doubt that as then you would most likely connect to it via IPv6 fow which you need appropriate DNS and so on... ofc, it is possible but I doubt it. If you suspect IPv6 is somewhat related to your issue, you can disabled at OS level (need to reboot after most likely).  I suspect most likely none of this is related to real cause, but normally this kind of problems are easy to fix via webex so you should just file a ticket with your support and should be fixed quickly.

NetWorker

Move a NetWorker clients from one NetWorker Server to another

Was this post helpful?