RC 13: file read failed

Status 13's are usually caused by one of the following:

*  An I/O error occurred during a read from the file system.
*  Read of an incomplete file or a corrupt file.
*  Socket read failure. A network problem or a problem with the process that writes to the socket can cause socket read failure.
*  A problem specific to NetBackup Snapshot Client (see recommended actions).

Is this one client or many? 
Are these new clients or were they previously backing up without issue?
Are these clients using snapshots or flashbackup in anyway?
Are there any firewalls between the client and master/media server that might be blocking ports?

If the clients are using snapshots then check your bpfis log for more detail on the cause of the failure.  You may also want to check the bpbkar log on the client side to determine if the error appears there. Or if the backup job never gets to the point that bpbkar on the client is logging than there are most likely issues with the network or port communication. 

Start with this:
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

Then search your web page for 60_7 amongst this long list for maintenace packs or for any status 13 technotes
http://seer.support.veritas.com/docs/NBUESVR_index.htm

Then search in the KB for RC 13
http://entsupport.symantec.com/nbucode/13

See if any newer NetBackup Maintenance Packs for your OS address RC 13 issues.

Is the RC 13 for a database agent?
I too am experiencing status 13  and 25 regularly.  (6.5.4)

Have you taken a look at the troubleshooting guide for Status 13 errors?

http://seer.entsupport.symantec.com/docs/278563.htm

Hi all,
thx for your support.

additional inforamtion about my issue:
- affected is only one client
- before this error all works corresctly
- client is using snapshot
- ports are not blocked
- on client is running aplication backup (SAP) witout any problems

i have tested backup with other configuration and if i allow data multiple stream on client all running correctly!!!!!
... but i need to fix it some other way because in policy are next 80 clients where i cant allow it :D

It is looks like a performance issue, isnt???

Restarting NB services on client sometimes resolves status 13 & 14