Changing master server name cause issues for restores?

[ROrp]

Hello All:

We have an old NetBackup server (NBU 5MP6) that we are no longer using in production but would like to keep around for legacy catalog searches and restores. I am interested in changing the name of the server to uniquely identify its current use, for example, "server" to "server-legacy". Will simply changing the name of the server compromise our ability to perform catalog searches and restores? 

[Mark_Solutions · Accepted solution]

Changing its name will cause you a huge amount of issues - for NetBackup to work at all it would need a lot of changes making that would need professional services.

However, if this is just for restores you could use the cheat we sometime use for DR testing

This just needs a hosts file entry for "server" (short and FQDN) against it IP address so that it can still resolve the old name to itself

If you came to do restores to clients though you would need to put a hosts file entry temporarily on those clients to resolve server as the IP address of server-legacy

Hope this helps - best advice is do not change its name

[ROrp]

That is good to know Mark. I can see how the host entry file will be a viable workaround to the name change issues that will follow since restores will be the only use of this legacy system if needed. Thanks for the quick reply and solution.