Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

STATUS 13: file read failed

Created: 02 Jul 2013 | 6 comments

I am backing up a server with all local drives. Drives c:\ an d:\ get backed up but drive e:\ gives me status 13 error. I have attached the bpbkar log. It seems to be a file corruption error but the bpbkar log does not tell me which file. Is there any way to find out. The backups were fine for this server till today.

Operating Systems:

Comments 6 CommentsJump to latest comment

inn_kam's picture

Solution

 Increasing client read timeout on Media server host properties to be more than 15 minutes solved this issue.

NetBackup backup jobs fails with Status Code 13 - "file read failed" and bpbrm logs reports an error "socket read failed: errno = 62 - Timer expired"
Article:TECH182605  |  Created: 2012-02-28  |  Updated: 2012-07-28  |  Article URL http://www.symantec.com/docs/TECH182605
snawaz3's picture

bpbrm logs not created on the client. I get the same error when i resume the job. it backs up to certain point then fails. How can i find which file maybe corrupt that it fails on

watsons's picture

Enable bpbkar verbose=5 logs on the affected client and it may tell you which file having problem. Remember to set it back to verbose=0 afterwards as the logs can grow significantly.

snawaz3's picture

I am fairly new to NBU. Can you guide me on how to set this. Thanks

inn_kam's picture

snawaz

on Netbackup gui

click on Host Properties

then Master Server then IN Master Server Properties 

click on Time outs

then change Client Read out time to 1800 sec

then do the same steps for Media Server Properties

inn_kam's picture

waiting fro snawaz to reply

is above one helpful