07-14-2015 07:11 AM
Hi I'm getting this error while backking up one of my client..Need a solution for this.will some one help me in it....
7/14/2015 3:39:51 AM - Info nbjm(pid=6864) starting backup job (jobid=1470955) for client ETW-DBS000261.testeis.tweis.net, policy PROD_Win_Physical, schedule Full
7/14/2015 3:39:51 AM - Info nbjm(pid=6864) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=1470955, request id:{0D0F81F0-D79F-4322-8782-C54293937F2A})
7/14/2015 3:39:51 AM - requesting resource OSTBackup
7/14/2015 3:39:51 AM - requesting resource epw-inf000048.tw.tweis.net.NBU_CLIENT.MAXJOBS.ETW-DBS000261.testeis.tweis.net
7/14/2015 3:39:51 AM - requesting resource epw-inf000048.tw.tweis.net.NBU_POLICY.MAXJOBS.PROD_Win_Physical
7/14/2015 3:39:51 AM - granted resource epw-inf000048.tw.tweis.net.NBU_CLIENT.MAXJOBS.ETW-DBS000261.testeis.tweis.net
7/14/2015 3:39:51 AM - granted resource epw-inf000048.tw.tweis.net.NBU_POLICY.MAXJOBS.PROD_Win_Physical
7/14/2015 3:39:51 AM - granted resource MediaID=@aaaab;DiskVolume=ost_emcdd01_stu;DiskPool=OSTBackupPool;Path=ost_emcdd01_stu;StorageServer=usw_eib_emcdd01_9021.tweis.net;MediaServer=epw-inf000048.tw.tweis.net
7/14/2015 3:39:51 AM - granted resource OSTBackup
7/14/2015 3:39:51 AM - estimated 0 Kbytes needed
7/14/2015 3:39:51 AM - begin Parent Job
7/14/2015 3:39:51 AM - begin Snapshot, Start Notify Script
7/14/2015 3:39:51 AM - Info RUNCMD(pid=33876) started
7/14/2015 3:39:51 AM - Info RUNCMD(pid=33876) exiting with status: 0
Status 0
7/14/2015 3:39:51 AM - end Snapshot, Start Notify Script; elapsed time: 0:00:00
7/14/2015 3:39:51 AM - begin Snapshot, Step By Condition
Status 0
7/14/2015 3:39:51 AM - end Snapshot, Step By Condition; elapsed time: 0:00:00
7/14/2015 3:39:51 AM - begin Snapshot, Stream Discovery
Status 0
7/14/2015 3:39:51 AM - end Snapshot, Stream Discovery; elapsed time: 0:00:00
7/14/2015 3:39:51 AM - begin Snapshot, Read File List
Status 0
7/14/2015 3:39:51 AM - end Snapshot, Read File List; elapsed time: 0:00:00
7/14/2015 3:39:51 AM - begin Snapshot, Create Snapshot
7/14/2015 3:39:51 AM - started process bpbrm (26140)
7/14/2015 4:09:52 AM - Error bpbrm(pid=26140) bpcd on ETW-DBS000261.testeis.tweis.net exited with status 23: socket read failed
7/14/2015 4:09:52 AM - Info bpbkar32(pid=0) done. status: 23: socket read failed
7/14/2015 4:09:52 AM - end writing
Status 23
7/14/2015 4:09:52 AM - end Snapshot, Create Snapshot; elapsed time: 0:30:01
7/14/2015 4:09:52 AM - begin Snapshot, Stop On Error
Status 0
7/14/2015 4:09:52 AM - end Snapshot, Stop On Error; elapsed time: 0:00:00
7/14/2015 4:09:52 AM - begin Snapshot, End Notify Script
7/14/2015 4:09:53 AM - Info RUNCMD(pid=17276) started
7/14/2015 4:09:53 AM - Info RUNCMD(pid=17276) exiting with status: 0
Status 0
7/14/2015 4:09:53 AM - end Snapshot, End Notify Script; elapsed time: 0:00:01
Status 23
7/14/2015 4:09:53 AM - end Parent Job; elapsed time: 0:30:02
socket read failed(23)
Solved! Go to Solution.
07-20-2015 09:58 AM
I describe the 23/24/25 status codes as follows:
RC=23: Server A sent a IP packet to valid server B, and is waiting for a response packet. It fails to get the response packet within the TIMEOUT window and raises the rc=23.
RC=25: Server A tried to sent IP packet to invalid server B. No connection made so Server A sets rc=25.
RC=24: Server A sends packet to server B and get a response within the TIMEOUT window. But something happens that drops connection between them.
I make an analogy of this communication environment using phone calls:
Person on Phone A calls to phone number B, which connects and they leave a voice mail to call them back. They wait for a call back that does not come and after a specified time, they quit. RC=23.
Person A calls phone number for what he thinks is a valid Phone B. The call does not go through and they hear the message "The number you have dialed is not a working number". RC=25.
Person A calls Person B, they call is picked up but the line connection somehow gets dropped unexpectedly.while communications is in progress. RC=24.
All of these are communication errors of some kind.
For RC=25, the sourtce server may have the wrong target server name in its environment or an invalid/wrong IP address for the target server.
For RC=23, A can talk to B but B cannot talk to A. Could be a source server it does not recognize or it is using the wrong IP address t respond to. Possible bad host name to IP resolution.
RC 24: The toughest of the bunch. A and B know each other correctly. They just can't keep the call going.
Anyway, that's how I try to explain these things.
07-14-2015 10:54 AM
A classic culprit is backup client NIC left in auto-negotiate mode which sometimes selects 10Mb/hdx and causes all sorts of strange socket errors. Check that first for a quick win.
If you can confirm that both the backup client's NIC port - and - the LAN switch port really are fixed 1 Gbs and neither side (client or switch) is in auto-negotiate mode - then get the network admin to also check for port errors too, e.g. high counts of link-up/link-down for the backup client.
If you get these checked and still have problems, then come back for some advice on how to trouble shoot using the logs.
07-14-2015 01:01 PM
07-14-2015 01:20 PM
Is this ever worked or a new client?
Is this failing after writing some data?
Please provide the bptestbpcd output and bpcd logs from client.
07-14-2015 11:45 PM
If this is newly added client the check with below command are these ports open:-
From Master server:-
Run->cmd->telnet <client ip address or name> 1556
Run->cmd->telnet <client ip address or name> 13724
Run->cmd->telnet <client ip address or name> 13782
From client:-
Run->cmd->telnet <master ip address or name> 1556
Run->cmd->telnet <master ip address or name> 13724
Run->cmd->telnet <master ip address or name> 13782
If any ports is not open then you will need to open that port vice versa
07-15-2015 12:58 AM
07-20-2015 09:58 AM
I describe the 23/24/25 status codes as follows:
RC=23: Server A sent a IP packet to valid server B, and is waiting for a response packet. It fails to get the response packet within the TIMEOUT window and raises the rc=23.
RC=25: Server A tried to sent IP packet to invalid server B. No connection made so Server A sets rc=25.
RC=24: Server A sends packet to server B and get a response within the TIMEOUT window. But something happens that drops connection between them.
I make an analogy of this communication environment using phone calls:
Person on Phone A calls to phone number B, which connects and they leave a voice mail to call them back. They wait for a call back that does not come and after a specified time, they quit. RC=23.
Person A calls phone number for what he thinks is a valid Phone B. The call does not go through and they hear the message "The number you have dialed is not a working number". RC=25.
Person A calls Person B, they call is picked up but the line connection somehow gets dropped unexpectedly.while communications is in progress. RC=24.
All of these are communication errors of some kind.
For RC=25, the sourtce server may have the wrong target server name in its environment or an invalid/wrong IP address for the target server.
For RC=23, A can talk to B but B cannot talk to A. Could be a source server it does not recognize or it is using the wrong IP address t respond to. Possible bad host name to IP resolution.
RC 24: The toughest of the bunch. A and B know each other correctly. They just can't keep the call going.
Anyway, that's how I try to explain these things.
07-20-2015 12:07 PM
That Jaime, is an excellent explanation ...