Showing results for 
Search instead for 
Did you mean: 

Windows client with error 13

We have master server 6.5.3 and windows 2003 cleint with 6.5.3 version
The client is failig with the error code 13 and below is the error
12/8/2009 10:33:51 PM - Error bpbrm(pid=27150) socket read failed: errno = 62 - Timer expired   
12/8/2009 10:34:02 PM - end writing; write time: 01:59:51
file read failed(13)

with the client read time out : 900 seconds
Please let me know what can be checked and rectified
The main probem is sometimes the backups fails and sometimes it gets successfull without any changes made on client or server end.
11 Replies

Do you use a SAN client ?

Do you use a SAN client ?

No we dont

No we dont

could be network issues or...

I know this technote is for version 5.1, but it is still worth reading:

Also, there's this about antivirus sw causing problems:


<duplicate entry deleted>

<duplicate entry deleted>


Check the above technote if it helps

Or maybe the TCP

Or maybe the TCP "keepalivetime" is too low in your registry

Worked for me

I go to client configuration set the time out to 3000
and the interface.. (my server has 3 ethernet)  I put just one IP there

Increase timeout

I have had the same issue  on some of my "smaller" or "busy" servers.

If I had too many jobs running at once they would fail.
or if the server was busy doing something else it just would not respond to NB fast enough so it would fail.

If you are running more then one concurrent job on that client you could also try limiting the number of jobs (just on that client) to 1 or 2.

Another Issue

Another one,

I have some problems like that over a Linux and Solaris

there was some file systems w/ problems.
usually a mounted nfs over solaris stuck the df -hk  try umount -f /filesystem

over windows
some mapped drive that is not available over network.

The default value is 7200000

The default value is 7200000 (ms) = 2 hours. You should try at least with 300000.

Symantec suggests

Symantec suggests

as already given by rilwan dawodu

if you still have the same issue, try netbackup restart on client once, it might be a trick ;)