08-18-2012 09:40 PM
Hi Experts,
Yesterday we have changed IP address of a CLIENT MACHINE right from that the backup is failing for that CLIENT with error 48, Can anybody help me plzz.
Thanks
Nayab
Solved! Go to Solution.
08-21-2012 05:34 AM
If your network guys cannot sort it out and you need to get the backups done then just use hosts files all round ...
master and media servers ip addresses on the client
clients ip address on the master and media servers
then do the bpclntcmd -clear_host_cache on them all to flush out any old IP addresses held anywhere
As NetBackup uses only tcpip you backups will then work successfully regardless of any DNS issues
08-18-2012 09:53 PM
Sorry FOLKS im in hurry i made a typo its not 47 its 48 error
08-18-2012 10:47 PM
bperror -S 48 -rclient hostname could not be foundThe system function gethostbyname() failed to find the client's host name.Verify that the client name is correct in the following:* The NetBackup policy configuration on the master server.* The General tab in the following dialog boxes: NetBackup Client Properties and Specify NetBackup Machines and Policy Type (on Microsoft Windows and NetWare nontarget clients). To display these dialog boxes, start the Backup, Archive, and Restore interface on the client. For the General tab, click NetBackup Client Properties on the File menu; click Specify NetBackup Machines and Policy Type on the File menu.* The bp.conf file on UNIX, Linux, and Macintosh clients.* The bp.ini file on NetWare target clients.* On clients and servers, verify that the name service is set up to resolve the NetBackup client names correctly.On UNIX and Linux clients, verify that the client's host name is in the /etc/hosts file or the YP hosts file or NIS maps
08-18-2012 11:46 PM
Yes ping is fine the client is pinging fine from both MEDIA and MASTER server.
08-18-2012 11:53 PM
whenever i go to CLIENTS TAB in master server and select that particular client and see the properties it says like --> PING FAILED ON HOST (<IPADDRE>)
please check the screen shot.
08-18-2012 11:56 PM
Please check the detailed staus in the below Screen Shot
08-19-2012 12:02 AM
Hi Maria ,
And i checked with my windows admin he sed everything fine at the DNS side. So please help me to resolve this issue.
Thanks
Nayab
08-19-2012 12:41 AM
What does "bptestbpcd -client <client name> -debug -verbose" show?
From both teh master and the media serves.
08-19-2012 01:33 AM
Please show us output of the following on media server svaubk02:
nslookup svausec01
Do the same on the master server.
Which OS is Master? Media server? Client?
08-19-2012 02:02 AM
O.S of MASTER, MEDIA, CLIENT servers is WINDOWS 2008 R2
let me check with that command
08-19-2012 02:09 AM
On master server
c:\>nslookup svausec01
DNS request timed out.
timeout was 2 seconds.
server: Unknown
Address: 10.10.6.11
DNS request timed out
timeout was 2 seconds
DNS request timed out.
timeout was 2 seconds
*** Request to unknown timed-out
On Media server
c:\>nslookup svausec01
DNS request timed out.
timeout was 2 seconds.
server: Unknown
Address: 4.4.2.2
DNS request timed out
timeout was 2 seconds
DNS request timed out.
timeout was 2 seconds
*** Request to unknown timed-out
08-19-2012 02:25 AM
Doesn't really look like DNS is working to me.
Think you need to go and poke your Windows Admin with a DNS manual.
Martin
08-19-2012 02:40 AM
Do you mean to say that this problem raised as we have changed the ip address on this CLIENT coz backups for other clients running succesfully and completed with no errors
or this is a problem with DNS for this particular CLIENT
08-19-2012 03:00 AM
I think the cause of the issue is fairly clear.
"Yesterday we have changed IP address of a CLIENT MACHINE right from that the backup is failing for that CLIENT with error 48"
You could ensure that the master and media server have the correct entry for the cllient in the hosts file.
If DNS is meant to be used, then there would be no need for hosts file entries, but only you know what should be being used in your environment.
Persoanlly, if DNS is used, it would be good to have hosts file entries as well, so that if there is a DNS issue, the servers fail back (*) to using the hosts file, to prevent backup failures.
(* On unix, the resolv.conf file controls the order name resolution is done, eg. use dns, if that fails use /etc/hosts file)
I am not a windows admin, and I am not sure how you control this in windows. but your windows admin should know this.
Martin
08-19-2012 03:10 AM
Yes, we are using DNS only and i do have knowledge about HOSTS file let me check this myself
08-19-2012 03:20 AM
Sure - a requirement for NBU to work is that the servers (master/ media/ cllient) can fully resolve (forwards and backwards) the names of the machines that contact them.
Martin
08-20-2012 03:41 AM
Deadly silence today....
I'm wondering how ping was working 'fine'?
Please show us output of the following on master and media server:
ping svausec01
08-20-2012 11:24 AM
Can you please let us know the OS of your master and media ? I am assuming your master & media server is running on windows machine ,
Check the host file entries in your master and media server, as you mentioned in your post that you have changed the ip of a client and after that started facing issues. As per your post it is sure that ip address is not properly matched with the client name , i.e. some where it is reffering to the old ip address.
On the Master and media server go to the path "windows\system32\drivers\etc" and open the hosts file.
Assuming that you client name is "ABC" and old ip address of ABC client is 10.122.125.150. Check on the host file entires is any of this client name of ip address is persent with name ABC or IP address 10.122.125.150 , if so remove it and change it to proper ip address which you newly assigned. Else the new ip which you changed for cleint "ABC" may be using by another client and it was present in the host file.
If all your machines are in DNS then you can try pinging the client name form any other machines and check whether the changed ip is reflecting properly for the client " ABC" over there also. If every where IP address and client name matches properly then your client should communicate.
Then on the master and media server run the below command this will clear the old cache entires i.e previous entries of the client, bpclntcmd -clear_host_cache
and then try the "bptestbpcd -client <client name>" on master and media server . It should resolve the ips properly.
08-20-2012 08:44 PM
Hi All,
Mark suggested me to CLEAR the host cache with the below command to be run on both MASTER & MEDIA server , i am gonna try this today will this cause any Impact or downtime, as per my knowledge when i clear the cache it will rebuild again referring to DNS or HOSTS file. Correct me if i am wrong
experts guide me accordingly???
bpclntcmd -clear_host_cache
08-20-2012 09:29 PM
Please tell us first - is nslookup now working?
Can you ping the client using hostname (not IP address)?
There is no use clearing NBU host_cache when name lookup at OS level is not working.
Clear host_cache when OS lookup works. This will refresh NBU own cache, otherwise wait about 1 hour, after which NBU will automatically refresh host cache. No restart needed.
See this TN: http://www.symantec.com/docs/TECH136792