Forum Discussion

flavor4real's avatar
14 years ago

file read failed(13)


Godd Morning,
I have following error msg after the bkup job ran for at least 2 days.  any ideas? thanks


9/10/2010 8:03:48 AM - Error bpbrm(pid=7736) socket read failed, An existing connection was forcibly closed by the remote host.  (10054)
9/10/2010 8:03:50 AM - Error bptm(pid=2572) socket operation failed - 10054 (at child.c.1285)     
9/10/2010 8:03:55 AM - Error bptm(pid=2572) unable to perform read from client socket, connection may have been broken
9/10/2010 8:04:34 AM - Error bpbrm(pid=7736) could not send server status message      
9/10/2010 8:04:50 AM - end writing; write time: 01:58:54
file read failed(13)
  • KnowledgeBase

    (***EDIT*** If you haven't already, you may want to bookmark the above URL and the following one:
    This Technote contains a table for NetBackup's Status Codes, with links to potential resolutions for each.
    http://seer.entsupport.symantec.com/docs/301522.htm
    end of EDIT)

    They may assist?

    Backups are failing on Windows clients. The following error message will appear in the bpbkar log file on the client: "(TCP 10054: Connection reset by peer)" or "FTL - tar file write error (10054) ".
    http://seer.entsupport.symantec.com/docs/200380.htm

    STATUS CODE 13: Backups fail with Status Code 13 "file read failed", indicating that a read of a file or socket has failed. Winsock errors 10054 and 10053 may also be seen in the bpbkar log on the client.
    http://seer.entsupport.symantec.com/docs/275189.htm

    Does this relate to your other post?
    https://www-secure.symantec.com/connect/forums/file-read-failed-13-full-bkup-no-issues-diff-bkup

    ***EDIT #2***
    In-depth Troubleshooting Guide for Exit Status Code 13 in NetBackup Server (tm) / NetBackup Enterprise Server (tm) 6.0
    http://seer.entsupport.symantec.com/docs/278563.htm

4 Replies

  • KnowledgeBase

    (***EDIT*** If you haven't already, you may want to bookmark the above URL and the following one:
    This Technote contains a table for NetBackup's Status Codes, with links to potential resolutions for each.
    http://seer.entsupport.symantec.com/docs/301522.htm
    end of EDIT)

    They may assist?

    Backups are failing on Windows clients. The following error message will appear in the bpbkar log file on the client: "(TCP 10054: Connection reset by peer)" or "FTL - tar file write error (10054) ".
    http://seer.entsupport.symantec.com/docs/200380.htm

    STATUS CODE 13: Backups fail with Status Code 13 "file read failed", indicating that a read of a file or socket has failed. Winsock errors 10054 and 10053 may also be seen in the bpbkar log on the client.
    http://seer.entsupport.symantec.com/docs/275189.htm

    Does this relate to your other post?
    https://www-secure.symantec.com/connect/forums/file-read-failed-13-full-bkup-no-issues-diff-bkup

    ***EDIT #2***
    In-depth Troubleshooting Guide for Exit Status Code 13 in NetBackup Server (tm) / NetBackup Enterprise Server (tm) 6.0
    http://seer.entsupport.symantec.com/docs/278563.htm
  • well,.. i have to work for my answeres at time so u pointed me to the right direction and i will read... best way to learn, ain;t it ;)