Renaming or migration of a NetWorker server

[@montriconet]

Thanks for your videos, they have helped me a lot to learn more about networker and to be able to give answers in my daily support tasks

[@crazyrov]

Great to hear! Thank you.

[@kripalp9186]

Awesome ✌

[@crazyrov]

Thanks 🤗e

[@vpabloca]

Good material Rov. Quick one: once you rename or migrate NW server, you don’t need to migrate/move all volumes ? No need to change the ‘bootstrap’? So this renaming migrating do not affect it? Or we should use separately NW volume mover? Thanks in advance Super NW 👍🏻👍🏻👍🏻👍🏻👍🏻👍🏻

[@crazyrov]

Hi Victor !! The No need to do a separte move of volumes because the resdb contains all this information. So once resdb is moved incase you are using a separate server the volume configuration move with it. Incase of a tape library, the TL and the Tape drive will need to be deleted and the reconfigured. But in case of DD since the access is over the LAN there is no change required.

[@vpabloca]

@@crazyrov Alright, thanks for the clarification Super Rov. Make sense. Thanks and have a great day my friend.

[@montriconet]

I have a Networker server that was previously physical and was migrated to virtual in a VMware farm, now every so often the server times out and we have to restart it. This server only manages backup tasks, the Networker console is installed on another server and there are other servers that work as storage node to control the devices. We have been like this for several months and we have not been able to solve the problem, an SR was even opened but it was not solved, the Networker server version has been updated several times and nothing, there is no Firewall between this and the other servers, the antivirus has a exception to Networker server, the resources are sufficient, the network is 10Gb, I don't know what else it could be, any suggestions? I only have a DPA agent there to collect data in version 19.4

[@crazyrov]

Thanks for the query Oscar! Can you elaborate a little more when you mention that the server timesout. There is no response to nsradmin or nsrwatch or any commands. Or is the NMC not able to connect to the NetWorker server.

[@montriconet]

​@@crazyrov Thanks for replying, sorry for the delay. The nsrwatch does not work, the backup server can be accessed remotely, but the networker resources or services are not available, and the only recourse we have left is to restart the server again. There are no resource or performance issues at the windows level. Let me see if I can send you a photo with the error.

[@nowonmai7818]

How about if NetWorker is installed on Windows and migrating to a newer environment?

[@crazyrov]

Similar behavior, there are some additonal steps required. You can follow the steps that can be generated using the solve online tool.

[@eramitmcsa]

Awesome

[@crazyrov]

Thanks !

[@bartoque2]

how did you you prevent running into a conflicting nsrladb entry as that would still contain the old networker server name? Hence after you would start up NW, it would not really continue as it would contain a conflict still referring to the old name, offering to "solve" this by deleting NSRLADB. Might you not have omitted some intermediate steps? Also what to do with the authc that would still contain the refrence to the old NW server name? Also when starting the NMC in between, one would have to define dummy as an entry as I assume connecting to the old name wouldn't work anymore as that was changed already in the local host file of the local nmc...

[@crazyrov]

Hi, yes the nsrladb does give issues most of the time when you change the hostname of a server. In the case of the demo I dint get that issue. But if you delete you can simply rename the nsrladb when the services are down. authc will continue with the new hostname but for the NMC to work you will have to run the nmc config script to redirect it to the new hostname for the authc server. But in an Enterprise environment you will always have a separate NMC and authc server.

[@bartoque2]

@@crazyrov and then it went south from there when I did as after I ram the reconfiguration script for the nmc (as it was now called dummy), it would no longer show any settings. Nsradmin showed for example the original client defs to be there, but the nmc itself wouldn't. As it was just a test env, I simply removed everything from nw underneath /nsr and the references underneath /opt and renamed the nw server from short name to fqdn and started fresh. Maybe also good to state that officially Dell does not support any nw server rename from nw9+ onwards. Will be reaching out to them to see what the state about this nowadays... No biggy for me now, but will stay away from renaming a production server. Too much the original name is everywhere nowadays with also authc underneath /opt.

[@crazyrov]

@@bartoque2 The reason for the NMC to be blank after running the NMC configuration script is because the NMC looses the permission to the NetWorker server's resources. You will need to run a nsraddadmin again to get this permission back. And sometime as backup admin we have very little to no say on renaming or moving a backup server to new hostname/fqdn.

[@crazyrov]

I avoid putting in all these details in the video because it makes the video super lengthy and viewers start complaining. May be I will add a topic in detail to my blog and link it here or create a separate troubleshooting video.

[@bartoque2]

@@crazyrov a blog stating the steps (*) or a description beneath the video of the steps performed, might indeed help. (*) also makes for easier copy/paste...

[@ratmcoreable]

Thanks for the great video. I stop networker service daemon, added dummy to /etc/hostname, and added dummy IP to the hosts file as shown below. (original ip ) dummy (fake ip)backupserver When you start the daemon later, the networker still starts with the old hostname. Is there any other work needed beforehand? Did I miss something?

[@crazyrov]

This is because the hostname is not changed. If you run the command `hostname` you still get the old hostname and that is what networker picks up as well. What you are following is valid for a change in clients hostname not the servers.

[@AmitSingh-kb4xr]

Very good

[@crazyrov]

Thanks Amit !! :)

[@damodarreddy8806]

Hi Rov, can you make a video explaining integration of ecs with Networker and data movement from NW to ECS.

[@crazyrov]

Do you mean Cloud Boost using ECS?

[@damodarreddy8806]

@@crazyrov yes

[@mhmdmageid9041]

Hello My friend, I have gone through your valuable channel, it contains massive information that is extremely priceless. I would like to ask if you have done any "Networker Migration" from Hardware to another Hardware, i didn't find any video for the same. I'll be doing that task, migrate one server "Storage Node + NMC" into 2 servers. Any advise?

[@crazyrov]

Thanks for your comment! Storage node is stateless - does not contain or store any configuration. So you can simply install the storage node binaries on a new host, delete the peer information on the server if using the same hostname and then start using it. NMC on the other hand will need the NMC database to be restored on the destination server where ever you want new NMC to be on