This post is more than 5 years old
2 Intern
•
161 Posts
0
7771
May 10th, 2016 01:00
How to rename NetWorker server running UNIX
Hi guys,
I found a couple of How Tos for renaming a NetWorker server under windows. I'm planning to rename our NetWorker server running SLES 11.3 with a NetWorker version of 8.2.2.4.
Here is how I imagine to do that:
1. Stop NetWorker services and do VMware snapshot
2. Rename the server and adjust the DNS name
3. Reboot the server
4. Edit the servers file (done that for all clients already)
5. Start up NetWorker services
6. Be happy
Did I miss something or is this way unsuitable?
Cheers
Jan
No Events found!
JayJay9882
2 Intern
•
161 Posts
2
May 13th, 2016 01:00
Tada, EMC provided a litte How To and it worked fine:
How to Rename a NetWorker Server - Linux/Unix
Assumptions:
-NOT migrating to new hardware
-NW version is 8.2 or later
1. Decide if you are going to use an FQDN or a shortname as the new name
2. Stop NW services and make a copy of the following directories:
/nsr/res
/nsr/mm
Afterwards, start NW services again
3. Create a file called merge.txt with the following text:
newname, oldname
*Where,
newname is the new name that you are renaming to
oldname is the existing name of the NW Server (as it appears in the clients tab of NMC)
4. Edit the hosts file on the NW Server to reflect the following:
x.x.x.x newFQDN newShortname oldname
*If you are using the shortname as the new name, reverse the order of the newFQDN and newShortname values
5. Use nsrclientfix to change the NW Server name to the new name:
> nsrclientfix -u merge.txt
6. Go to the following directory: /nsr/index
-Find the folder with the oldname
-Rename it to the newname
7. Confirm with mminfo that the newname owns the bootstraps:
> mminfo -avot | grep bootstrap
8. Stop NW Services
9. Use offline nsradmin to edit the nsr resource and the storage node resources:
> nsradmin -d "/nsr/res/nsrdb"
> p type: nsr
> delete
> y
> show name
> p type: nsr storage node
*Note the exact name of the storage node with the oldname and use it in the next command:
> p type: nsr storage node; name: oldname
> delete
> y
10. Rename the "/nsr/res/nsrladb" directory to "/nsr/res/nsrladb.old"
11. Start the NW Services and log into the NMC
12. Confirm everything is correct
JayJay9882
2 Intern
•
161 Posts
0
May 10th, 2016 03:00
Yes, backup server.
This procedure is described for a windows backup server as well but I don't get why you need to rename the backup server temporarily to a third name!? Can someone explain that to me?
ble1
2 Intern
•
14.3K Posts
0
May 10th, 2016 03:00
Server as client or server as backup server? If as backup server then you need 3 steps... where you rename backup server to temporary name first, under that name you do client name of old server to new one and finally you rename it from temporary name to new one. I believe, if I remember correctly, that was official procedure.
ble1
2 Intern
•
14.3K Posts
0
May 10th, 2016 03:00
I believe it is related to the fact that renaming takes care that DB link stuff (client clientid) is moved in correct order from old to new name.
bingo.1
2.4K Posts
0
May 10th, 2016 04:00
As the daemons/services will be started automatically after a reboot and changing the servers file requires a restart of the NetWorker client, I recommend the following procedure:
1. Add "*@new_name" to the administrator's list
2. Edit the servers file
3. Stop NetWorker services and do a VMware snapshot
4. Rename the server and adjust the DNS name
5. Use nsradmin on the resource directory to find and replace the existing servername wherever it was listed in the resources
Handle with care - this need some experience.
6. Reboot the server
7. Remove the old admin entry for the old server name from the administrator's list
(8. Add the old name as alias in the NW client resource)
9. Verify if you have replaced the old name in all resources
I think this is almost it
Do not forget for the clients that a new/changed servers file will only become effective once you restart the client service/daemons.
JayJay9882
2 Intern
•
161 Posts
0
May 10th, 2016 05:00
The attribute is read-only
I tried to change the name of the server doing "nsradmin -d /nsr/res/nsrdb", selecting NSR and change the name.
ble1
2 Intern
•
14.3K Posts
0
May 10th, 2016 05:00
You can't change it as it is ro attribute.
JayJay9882
2 Intern
•
161 Posts
0
May 10th, 2016 05:00
With
"5. Use nsradmin on the resource directory to find and replace the existing servername wherever it was listed in the resources
Handle with care - this need some experience."
you mean that I do a "nsradmin -d /nsr/res/nsrdb" while the server is down and just overwrite the old server name with the new server name under "NSR client"?
bingo.1
2.4K Posts
0
May 10th, 2016 05:00
Correct - but don 't do that globally as not all changes might make sense.
As I have not done such for a while I can't remember all details.
That's why I said "handle with care". Carefully check the resources first.
JayJay9882
2 Intern
•
161 Posts
0
May 10th, 2016 05:00
Yes, I got that.
So I renamed the server with a temporarily name but NetWorker won't come up:
86948 1462884863 5 3 17 2889148192 8241 0 nsrd RAP critical 51 Failed to initialize ports using nsrexecd on %s: %s 2 12 21 49 31 4199 23 Service not available.
86939 1462884863 5 3 17 2889148192 8241 0 nsrd RAP critical 48 Unable to get port range from local nsrexecd: %s 1 49 128 86948 51 Failed to initialize ports using nsrexecd on %s: %s 2 12 21 49 31 4199 23 Service not available.
12506 1462884863 5 5 0 2889148192 8241 0 nsrd NSR critical 38 nsrexecd is unavailable, cannot start. 0
ble1
2 Intern
•
14.3K Posts
0
May 10th, 2016 12:00
It seems to suggest portmapper could not be started. Check if something else is using it. If not, rename nsrladb and try again to start it (make sure no nsr process is active at the time you rename it).
bingo.1
2.4K Posts
0
May 10th, 2016 12:00
Obviously not even the client service could be started.
This points to the fact that the entries in the nsrladb resources are wrong as well.
Please go ahead and rename /nsr/res/nsrladb or delete it.
It will rebuild all missing resources whenever the NW server will reconnect to each client.
Then restart the NW daemons.
I just verified that the NW server will now start as usual.
JayJay9882
2 Intern
•
161 Posts
0
May 12th, 2016 00:00
After renaming the nsrladb only the nsrexecd comes up. That's weird! nsrd and some other processes are started but immediately shutdown and only the nsrexecd keeps being up.
bingo.1
2.4K Posts
0
May 12th, 2016 01:00
Look at the end of daemon.raw - it should tell you about the troublemaker.
JayJay9882
2 Intern
•
161 Posts
0
May 12th, 2016 02:00
I now tried to rename the backup server by using nsrclientfix, described here:
https://emcservice.force.com/CustomersPartners/kA5j00000008Tl4CAE
All daemons come up now but the name of the backup server is still the old one.
"Unable to connect to the nsrexecd process on host 'old.networker.name': Unknown host. Ensure that the host 'old.networker.name' can be reached. If required, restart the host."
It cannot be reached because the IP of old.networker.hostname now points to new.networker.hostname.
What I see during browsing through nsramin is that for all clients ressources the "server" fiield is filled with the new networker name. But under NSR ist still claimed that the old networker name is the name of the backup server.
I figured it would be easier!