Unsolved
This post is more than 5 years old
13 Posts
0
1530
June 3rd, 2015 05:00
Networker Instance name remains the same after Networker server host migration with different hostname
Hi,
I have recently migrated a networker server with Data Domain devices from an old host with Windows 2008 R2 to a new host with Windows 2012 i followed the document generated by Solve Desktop and after the migration when you check the Networker instance name from the properties of the Networker server in NMC i still see the old server hostname although the backup and everything is running on the new hostname without any problems.
But when i try to reinstall the Networker software or upgrade the software the instance name is changed to the new hostname and all the the configuration disappear from NMC (Like clients - Groups - Devices)
and i have to run the command "mmrecov" to recover the bootstrap and all the configuration back.
Below is the output in NSRLA record:
nsradmin> print type: NSRLA
type: NSRLA;
name: old_hostname;
nsrmmd version: 8.2.1.0.Build.681;
nsrsnmd version: 8.2.1.0.Build.681;
NW instance info operations: ;
NW instance info file: ;
installed products: ;
auth methods: "0.0.0.0/0,nsrauth/oldauth";
max auth attempts: 8;
administrator: \
"group=Administrators,host=old_hostname",
"group=Administrators,host=localhost",
"isroot,host=old_hostname",
"isroot,host=new_hostname";
arch: Windows Server 2012 R2;
kernel arch: AMD_X8664;
CPU type: AMD_X8664;
machine type: server;
OS: Windows Server 2012 R2 6.3;
NetWorker version: 8.2.1.0.Build.681;
client OS type: Windows NT Server on Intel;
CPUs: 6;
MB used: 21300;
IP address: "fe80::e048:ffa1:a3bb:179f", 10.11.10.51;
nsradmin>
I replaced the original hostnames with old_hostname and new_hostname
I will upload a screenshot of the NMC to explain what i see.
how to fix that?
Thanks,
Ahmed Amin
crazyrov
4 Operator
•
1.3K Posts
0
June 3rd, 2015 06:00
Ok, since you are recovering the entire res folder you also recovering the nsrladb also. Do the following steps:
- Stop the NetWorker services.
- rename the folder nsr\res\nsrladb to something else. Ensure you are renaming the correct folder as the nsrdb also resides under the same directory.
- start the service and check.
P.S : You forgot to hide your NetWorker server name in one of the images
ble1
4 Operator
•
14.3K Posts
1
June 3rd, 2015 06:00
Most likely the quickest fix would be:
- stop NW
- rename nsrladb folder
- start NW
This will create new nsrladb with instance name of new server.
ble1
4 Operator
•
14.3K Posts
0
June 3rd, 2015 07:00
I'm not sure exactly where do you see that - can you post screenshot?
ahmed_amin
13 Posts
0
June 3rd, 2015 07:00
Thanks Hrvoje,
I tried and now the instance name appears correct in the nsradmin output and all the configuration appears ok, but still the old hostname appears in NMC. Is that ok?
ble1
4 Operator
•
14.3K Posts
0
June 3rd, 2015 07:00
It will still see it as that part is under nsrdb folder - don't touch that one.
ble1
4 Operator
•
14.3K Posts
0
June 3rd, 2015 07:00
That name normally is how server does it itself based on name on OS. Is it possible that you have /etc/hosts where old server is referenced with new IP?
ahmed_amin
13 Posts
0
June 3rd, 2015 07:00
It appears in the screenshot i attached to the original post, you can see the new hostname on the left of the screenshot and the old hostname on the right.
ahmed_amin
13 Posts
0
June 3rd, 2015 07:00
Thanks guys for your support.
So after renaming the nsrladb will the networker still see the old configurations (Clients - Groups - Devices - Pools) or will it appear as a new installation?
ble1
4 Operator
•
14.3K Posts
0
June 3rd, 2015 07:00
Or... go to /nsr/res/nsrdb and do:
grep 'old_name' */* anc check where it appears. Don't change it as it is live data, but rather with cat check each file to see which resource it is exactly.