Firstly, welcome to the forums and above all, thank you for being an EMC customer.

Please consider moving this question as-is (no need to recreate) to the proper forum for maximum visibility.  Questions written to the users' own "Discussions" space don't get the same amount of attention and can go unanswered for a long time.

You can do so by selecting "Move" under ACTIONS along the upper-right.  Then search for and select: "NetWorker Support Forum".

Thanks.

Sometimes DNS is not reliable enough and it is recommanded to use the Hosts file. You can also add the IP address to Globals (1 of 2), "Aliases". I have not heard any drawbacks to do this. Of course you need to remember change the IP address in the Hosts file and "Aliases" is IP address changes.

Thank you for everyone's input.

I needed input to make sure there is not something I am missing.

This question came up in a support call when the technician requested that they be removed.  In our environment we commonly have failure due to DNS (as most :-) ), so we have a host file in place for both server and client in some cases.  Configuring host files is a "work around" that I try to stay away from.  Combining the IP configuration in the "Aliases" section with host files is just another gotcha during the troubleshooting process.

As we touch our NetWorker Clients it would be a good idea to add the NetWorker Server in the host file:

#x.x.x.x     NetworkerServer.com     NetWorkerServer

Then if we have issues we could have the entry enabled by removing the #.

Just a thought.

You should make sure you have DNS which works fine.  I rarely have seen issues with DNS caused by DNS itself (apart from human error in configuration) so it is possible to have it   However, you are right that keeping an eye on this things is must so this is why I always have standby hosts table ready with all my clients which I can deploy whenever and wherever necessary.

Your idea is good and this is what a lot of other NetWorker administrators are doing.