11-14-2013 06:21 AM
Solved! Go to Solution.
11-15-2013 01:30 AM
If you have renamed a media servers host name via the registry it could lead to all sorts of issues i would have thought
I would be inclined to put it all back as it was and just add an alias for it
Again hosts files work nicely to eradicate things
11-15-2013 01:55 AM
11-15-2013 02:09 AM
or you can try adding alias...
11-15-2013 02:16 AM
I am only now reading this thread properly:
We had upgraded this server from 6.5.6 to 7.5.0.6 and configured it with the name i.e [eg xxxx.abc.com]. But now I changed it to use backup interface [xxxbu.abc.com].
I did the change in Registry in [client] key, and updated the master server using [nbemmcmd -updatehost] command.
Master:
<master public IP> master.fqdn
<backup-IP> masterbu.fqdn
<backup-IP xxxbu.abc.com
......
Media:
<public IP> xxxx.abc.com
<backup IP> xxxbu.abc.com
<backup IP> masterbu.fqdn
11-15-2013 03:14 AM
11-15-2013 03:15 AM
Thanks all for your supportive & valuable inputs.
11-15-2013 03:52 AM
Thanks for the solution.
As per my previous post - you should take special care when renaming media servers. NBU will see them as 2 different servers.
Old name should be properly decommissioned and new name configured as new.
Hope you have tested restores from backups done before the upgrade/rename?
11-18-2013 03:29 AM
No Marianne,
As of now I did not do any restore, but I'll try it later on. Hope that'll work.
Thanks for the suggestion.
Regards,
Vickie