cancel
Showing results for 
Search instead for 
Did you mean: 

Backup job is continously failing with EC:13.

Shyam_Prasad
Level 4
Certified

Hi All,

One of my windows 2003 client backup's are continously failing with EC:13.

connectivity between master, media and clinet is fine.
when i check the detailed job status i found the error like below:

01/21/2010 01:13:19 - begin writing
01/21/2010 02:27:05 - Error bpbrm (pid=13604) socket read failed: errno = 62 - Timer expired
01/21/2010 02:27:08 - end writing; write time: 1:13:49
file read failed (13)


bpcd is listening on the client and registry entries are fine. Services are up.
and the client netbackup version is 5.1 MP 5.
Master netbackup version is 6.5.1(Unix).

Can anyone help me to resolve this backup issue plsss!!

Thanks,
Shyam Prasad

1 ACCEPTED SOLUTION

Accepted Solutions

Nicolai
Moderator
Moderator
Partner    VIP   

You are seeing this error because something is taking too long time on the client. One step to see find the culprit is using the method described in the technote below.

Maybe the easiest way to solve the problem is upgrading the client  .......


Usage specifics of the bpbkar_path_tr touch file to enable enhanced debug logging of the bpbkar proc...


View solution in original post

3 REPLIES 3

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
Any reason why you haven't upgraded the client to 6.5 yet?
Although backing up 5.1 clients is still supported, things just work a lot better with servers and clients on the same level.

Shyam_Prasad
Level 4
Certified
we are planning it regional wise.....and it may take a while to upgrade this site !

Thanks,
Shyam Prasad

Nicolai
Moderator
Moderator
Partner    VIP   

You are seeing this error because something is taking too long time on the client. One step to see find the culprit is using the method described in the technote below.

Maybe the easiest way to solve the problem is upgrading the client  .......


Usage specifics of the bpbkar_path_tr touch file to enable enhanced debug logging of the bpbkar proc...