Server XYZ is failing with a error code 13 ( file read error)

[Robert_R_A]

Hi All,

Backup of server is failing with 13 error code after few KiloBytes of data backed up.

Restarted several times and failed continuosly. Need Help!!!!!

The detailed status of Job failed is given below,

Master server Name : Master1

Policy : win_sql_gp4

12/10/2013 04:00:01 - Info nbjm (pid=9699672) starting backup job (jobid=10168611) for client XYZ, policy win_sql_gp4, schedule Win_Diff

12/10/2013 05:41:02 - Info nbjm (pid=9699672) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=10168611, request id:{540F5914-6198-11E3-A805-48CFDD7A0000})

12/10/2013 05:41:02 - requesting resource nw-hcart-robot-tld-group

12/10/2013 05:41:02 - requesting resource Master1.NBU_CLIENT.MAXJOBS.XYZ

12/10/2013 05:41:02 - requesting resource Master1.NBU_POLICY.MAXJOBS.win_sql_gp4

12/10/2013 05:41:17 - granted resource  Master1.NBU_CLIENT.MAXJOBS.XYZ

12/10/2013 05:41:17 - granted resource  Master1.NBU_POLICY.MAXJOBS.win_sql_gp4

12/10/2013 05:41:17 - granted resource  110668

12/10/2013 05:41:17 - granted resource  nw-hcart-03

12/10/2013 05:41:17 - granted resource  nw-hcart-robot-tld-11

12/10/2013 05:41:17 - estimated 0 kbytes needed

12/10/2013 05:41:17 - Info nbjm (pid=9699672) resumed backup job for client XYZ, policy win_sql_gp4, schedule Win_Diff on storage unit nw-hcart-robot-tld-11

12/10/2013 05:41:21 - Info bpbrm (pid=5316) XYZ is the host to backup data from

12/10/2013 05:41:21 - Info bpbrm (pid=5316) telling media manager to start backup on client

12/10/2013 05:41:21 - Info bptm (pid=3004) using 65536 data buffer size

12/10/2013 05:41:21 - Info bptm (pid=3004) using 1024 data buffers

12/10/2013 05:41:34 - Info bpbrm (pid=3304) sending bpsched msg: CONNECTING TO CLIENT FOR XYZ_1386673213

12/10/2013 05:41:34 - connecting

12/10/2013 05:41:37 - Info bpbrm (pid=3304) start bpbkar32 on client

12/10/2013 05:41:37 - Info bptm (pid=5100) setting receive network buffer to 524288 bytes

12/10/2013 05:41:37 - connected; connect time: 0:00:00

12/10/2013 05:41:37 - begin writing

12/10/2013 05:41:39 - Info bpbkar32 (pid=0) Backup started

12/10/2013 05:41:39 - Info bpbrm (pid=3304) Sending the file list to the client

12/10/2013 05:41:59 - Warning bpbrm (pid=3304) from client XYZ: WRN - can't open directory: System State:\Task Scheduler Writer (WIN32 536935992: Unknown error)

12/10/2013 05:41:59 - Error bpbrm (pid=3304) from client XYZ: ERR - Error encountered while attempting to get additional files for System State:\

12/10/2013 05:41:59 - Warning bpbrm (pid=3304) from client XYZ: WRN - can't open directory: System State:\VSS Metadata Store Writer (WIN32 536935992: Unknown error)

12/10/2013 05:41:59 - Warning bpbrm (pid=3304) from client XYZ: WRN - can't open directory: System State:\Performance Counters Writer (WIN32 536935992: Unknown error)

12/10/2013 05:53:26 - Error bpbrm (pid=3304) socket read failed, An existing connection was forcibly closed by the remote host.  (10054)

12/10/2013 05:53:26 - Error bptm (pid=5100) socket operation failed - 10054 (at child.c.1294)

12/10/2013 05:53:26 - Error bpbrm (pid=3304) could not send server status message

12/10/2013 05:53:26 - Error bptm (pid=5100) unable to perform read from client socket, connection may have been broken

12/10/2013 05:53:26 - Info bpbrm (pid=5316) child done, status 13

12/10/2013 05:53:26 - Info bpbrm (pid=5316) sending message to media manager: STOP BACKUP XYZ_1386673213

12/10/2013 05:53:27 - Info bpbrm (pid=5316) media manager for backup id XYZ_1386673213 exited with status 150: termination requested by administrator

12/10/2013 05:53:27 - end writing; write time: 0:11:50

file read failed  (13)

Plz suggest some troubleshooting procedures for these.. Thanks a lot in advance

Rob :)

[Mark_Solutions]

A couple of issues here - first it has failures but looks to carry on - second it times out

This appears to be the first time it has done an incremental so may need three things doing to sort this out

1. On the media servers host properties change the client connect and client read timeouts to 3600

2. On the Master Server host properties - client attributes section locate this client (or add it) and set it to use VSS for its snapshots - individual drive snapshots - disable and continue on error

3. run vssadmin list writer on the client - it looks like some writers have issues - you will need to reboot it to clear these

Once you have done all of the above retry the job

hope this helps

[Yasuhisa_Ishika]

Please tell us more about you environment like OS version, NetBackup version, etc.

Unsuppoerted configuration may lead to this issue.

http://www.symantec.com/docs/TECH77271

[inn_kam]

As it is SQL Agent 

so enable dbclient logs on Agent as well as Master server

and also check the sa password on Netbackup GUI SQL Agent 

STATUS CODE 13: Backups fail with Status Code 13 "file read failed", indicating that a read of a file or socket has failed. Winsock errors 10054 and 10053 may also be seen in the bpbkar log on the client.

Article:TECH37372

|

Created: 2005-01-11

|

Updated: 2013-10-24

|

Article URL http://www.symantec.com/docs/TECH37372

[Marianne]

As per Yasuhisa's request - please provide all details of client being backed up:

OS version and patch level.
NBU version and patch level.
Information about backup policy -  What is Policy Type? What is Backup Selection? Is 'Allow Multiple data streams' selected inpolicy attributes?

We need to know OS and NBU versions as different issues have been seen that are OS and/or NBU related.

[Robert_R_A]

Hi guys,

Sorry for the delay...

As requested the details are,

Master server OS/NBU version :AIX6.1 / 7.1.0.4

Client server OS/NBU Version : Windows 2008 / 6.5.4

Policy Type : Differential Incremental

Backup Selection : ALL LOCAL DRIVES

"And allow multiple data streams is not selected in Policy attributes"

This issue is not resolved yet!!

[Robert_R_A]

@Mark_Solutions :

I have tried ur steps and it dint work then also...

It keeps on failing with 13 error after few data being backed up....!

Thank You

[Marianne · Accepted solution]

Master server OS/NBU version :AIX6.1 / 7.1.0.4

Client server OS/NBU Version : Windows 2008 / 6.5.4

PLEASE upgrade this client to 7.1.0.4!

There have been MANY fixes for Shadow Copy Components in 7.1.0.x patches.

Also a good idea to select 'allow multiple data streams' when the next FULL backup is due.
This will ensure that only problematic stream will fail and rest will go through.

Add SQL database files (*.mdf *.ldf) to Cleint's Exclude List.