BACKUP FAILING WITH STATUC CODE 13

[Dolapo1223]

Hello,

My name is Dolapo. Kindly help me with below errors which is really urgent on my behalf. Thank you.

05/31/2011 16:20:39 - requesting resource TSS-dtb1-backup-to-disk1

05/31/2011 16:20:39 - requesting resource TSS-NBU.NBU_CLIENT.MAXJOBS.dataloader

05/31/2011 16:20:39 - requesting resource TSS-NBU.NBU_POLICY.MAXJOBS.redhatclients-os-01

05/31/2011 16:20:40 - granted resource  TSS-NBU.NBU_CLIENT.MAXJOBS.dataloader

05/31/2011 16:20:40 - granted resource  TSS-NBU.NBU_POLICY.MAXJOBS.redhatclients-os-01

05/31/2011 16:20:40 - granted resource  MediaID=@aaaak;Path=/backup1;MediaServer=TSS-dtb1

05/31/2011 16:20:40 - granted resource  TSS-dtb1-backup-to-disk1

05/31/2011 16:20:43 - estimated 0 kbytes needed

05/31/2011 16:20:47 - started process bpbrm (pid=5697)

05/31/2011 16:20:50 - connecting

05/31/2011 16:20:51 - connected; connect time: 0:00:00

05/31/2011 16:20:54 - begin writing

05/31/2011 15:45:37 - Error bpbrm (pid=5697) socket read failed: errno = 62 - Timer expired

05/31/2011 15:45:39 - Error bptm (pid=5721) media manager terminated by parent process

05/31/2011 16:34:28 - end writing; write time: 0:13:34

file read failed  (13)

[Marianne · Accepted solution]

PLEASE always supply ALL relevant info -

NBU version on Master, Media server and client

OS version (including bit version) on Master, Media server and client.

Please ensure that all of these log directories exist:

On media server: bpbrm and bptm

On client: bpbkar

See:  http://www.symantec.com/docs/TECH71821
Increasing the Client Read Timeout on Media Server to 1800 seconds might help. Some clients with very large filesystems / active filesystems / lots of small files may need a value of 3600, 7200, 10800 or higher.
    
 

[Nathan_Kippen]

also turn up your logging to 5 on bpbkar while troubleshooting this error.

[Marianne]

Did you come right with this problem?

We tried to help but unfortunately there's no 'quick fix' for this type of error and analyzing logs is the only way to troubleshoot....

[ram619]

As Marianne stated we need to analyze the logs to narrow down the issue..

Below are the possible cause of the error..

A socket read failure caused by a network problem or a problem with the process that writes to the socket.

[Dolapo1223]

Thank you all for your response so far. I have increased the client Read time out to 10800 as i still have two file systems failing with status code 13 and initiated the backup again. i'll get back to you guys on the outcome. thank you once again.

[Dolapo1223]

hello all,

i have been able to record a successful backup and subsequent successfull backup after increasing the Client Read Timeout on Media Server. You guys are the best. Thank you all.

[pikachu]

Please mark this case as closed!

[pikachu]

I didn't solve it. You should have selected the post, which fixed the issue, but thx for the points my bday is coming up! :)

[Marianne]

Mine too!!! I thought that I was the one to mention Client Read Timeout...

https://www-secure.symantec.com/connect/forums/backup-failing-statuc-code-13#comment-5632511

[Dolapo1223]

Hi Pikachu, This problem was basically solved as a result of Ma'am Marianne van den Berg's suggestion....the point must have been a fault from my side. never the less, happy birthday..