Veritas-bu

[Veritas-bu] Re: Status 54 - how do you resolve this?

2004-02-24 09:38:39
Subject: [Veritas-bu] Re: Status 54 - how do you resolve this?
From: CJManders AT LBL DOT GOV (Christopher Jay Manders)
Date: Tue, 24 Feb 2004 06:38:39 -0800
 From the master server can you use 'bpdir -M systemname' and get a list 
of files? If not, the install *is* the issue.

Try to make sure the server names are all there, that the master is 
(current) and everything is CaSE SeNsiTiVE. Server names and especially 
client name. These will all give the 54 error...


HTH

Chris



Kelana Putra SETIA wrote:

> Hi All,
>
>      I happen to pick up this correspondence amongst yourselves, 
> through the Veritas website about the status 54 (see below):
>
> ############ Start of Correspondence ################
> Thanks Chris,
>
>      I greatly appreciate your response. I can telnet to port 13782 
> and do get a prompt as well but I initiate the backup from the server, 
> I can see "Connecting to client" then it times out. On one of the 
> other Windows 2000 client, it evens goes and says "Mounting media 
> xxxxxx" then it times out.
>
> It seems like a weird issue, isn't it?
>
> "Chris Manders" <cjmanders AT lbl DOT gov> wrote:
>
> We ahve seen the 54 error on clients that are not properly installed 
> (or just not installed). You can do:
>
> telnet hostinquestion 13782
> if the prompt hangs there, it is a good sign.
>
> On the client:
> netstat -an|grep 13782
> should show a LISTEN port...
> I hope this helps somehow...
>
> Chris
>
> >"Kumar Deuja" <kdeuja AT winstar DOT com> wrote:
>
> I am having the same problem while backing up Windows 2000 client with 
> Solaris Server. Hope you had some feedback regarding that..
>
> Thanks much.
>
> >>"Scott Lewis" <slewisNOSPAM AT questia DOT com> wrote:
>
> Use  ~/netbackup/bin/bpclntcmd on the client to check what kind of 
> connectivity NB is able to establish with the master. Could be 
> WINS/DNS server assignent issue on the client since it was recently 
> rebuilt. Also, Verify the SERVER value in bp.conf on the client.
>
> >>>"Garry Graves" <garry.graves AT nottinghamcity.gov DOT uk> wrote:
>
> I am running NBU Data Center 34_2 on AIX 4.3.3.The problem I am 
> getting is status code 54 when attempting to backup a Windows 2000 
> client.The messages posted to the bpcd log on the clinet is as follows :
>
>   bpcd peer_hostname: gethostbyaddr failed : The requested
>   name is valid and was found in the  (0)
>   bpcd peer_hostname: gethostbyaddr failed to return peer host, herrno 
> = 0 bpcd main: Couldn't get peer hostname.
>
> The client was previously backed up successfully until the client 
> machine was re-bulit recently.I am assured that nothing fundamental 
> has changed.I re-installed the NBU client software on the client 
> machine successfully.Both master server and client can be pinged 
> OK.Nothing has changed on the master server side in terms of host 
> files etc,Client Service Port and Request Service Port numbers are 
> correct.
>
> Has anybody come across theses sort of error messages before?
>
> ############ End of Correspondence ############
>
>
> The symtoms that I got are exactly the same that you guys encountered. 
> The checks that has been done are as follows:
>
> 1) bpclntcmd command on both server (solaris) and client (Windows NT). 
> -> Successful
> 2) We able to telnet from the server to the client through port 13782. 
> However, was not able to receive any LISTENING through port 13782 
> onthe client side. What does this imply?
>
> 3) We are able to ping from server to client and vice versa.
> 4) That the SERVER value on the client side is correct
> 5) We have also include the server name and IP address in the HOSTS 
> file on the client
> 6) The logs obtained from the client is exactly identical to the one 
> Garry Graves received (see below):
> *<2> bpcd main: setup_sockopts complete*
> *<8> bpcd peer_hostname: gethostbyaddr failed : NO_ADDRESS (0)*
> *<16> bpcd peer_hostname: gethostbyaddr failed to return peer host, 
> herrno = 0*
> *<16> bpcd main: Couldn't get peer hostname*
>
> How did you managed to solve the problem?
>
>
>       Kelana Putra Setia
>       StarHub
>       IT DC Ops
>       */~~~ Our People, Our Passion, Our StarHub ~~~/*
>       Email: _ [email protected]_
>
>
>
> This email is confidential and privileged.  If you are not the 
> intended recipient, you must not view, disseminate, use or copy this 
> email. Kindly notify the sender immediately, and delete this email 
> from your system. Thank you.
>
> Please visit our website at www.starhub.com
>


<Prev in Thread] Current Thread [Next in Thread>