Window2003 failing with the socket error 24
Updated: 23 May 2010 | 4 comments
The backups for the windows server is failing witht the error " socket write failed 24 " " could not send server status message"
The windows client is having NB 6.5.3. and master server NB is 6.5.3.
When is reraned manully the backup complete fine,, but many times it fails with this error which is scheduled.
discussion Filed Under:
Comments
Have a look at this TechNote:
Have a look at this TechNote: seer.entsupport.symantec.com/docs/304578.htm
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows.
Handy NBU links
All the parameters given in
All the parameters given in this tech note is same as in my environment..
Stil the backups is failing
Can someone explain what else can be checked and done?
Please post errors seen in
Please post errors seen in bpbkar log on client?
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows.
Handy NBU links
Multiple Parameters need to be checked
Socket Error points to connectivity issues and hence mutiple parameters are required to be checked .
/etc/host entries for all media and master servers
bp.conf entires for all media and master servers
was this backup running before ?
is there any chnages done lately on the master or client ?
time out entires in host properties like "client connect" and "client read"
is mutiplexing enabled? , try backups without multiplexing, if multiplexing is enabled try backups without multiplexing ,
if possible try re-installig the netbackup client
try changing the connect options in client attributes tab in host properties of master server
try telnet to bpcd port from client media server and master server
Would you like to reply?
Login or Register to post your comment.