Networker backup reverse DNS error when multiple NICs on backup client

 

Have you ever came across this scenario?

If you have a backup client with multiple NICs , backup server may be able to reach only one of the NIC and if you ping the host name you will be getting reply from IP configured on other NIC

See the image below

Here Networker give you a reverse DNS lookup error while it try for a reverse lookup with the IP 172.16.10.22 as the hostname resolution is on IP 10.10.100.22.

If you are facing above issue then configure backup as below;

Step 1: On client SQLSERVER create a hosts file (or on DNS) entry as below

This way the IP 172.16.10.22 will have a dummy hostname

Step 2: On Networker server create host file (or on DNS) entry as below

Now if you ping SQLSERVER or SQLSERVER_bkp you will get reply from 172.16.10.22

Step 3: On Networker configuration

Create a client with name SQLSERVR

Step 4: On Globals (1 of 2) tab add aliases as below

You can run the backup successfully now.

If your client is on a Cluster then add the backup IP(172.16.10.22) as a cluster resource and add the dummy hostname on both cluster nodes.