File Read Failed (13) for F:/ drive of a windows client

[abhishekKum]

Hello Everyone,

I'm getting (13) file read failed error during the backup of F:/ drive of a windows client while the rest of the drives are being backed up successfully.

Master, Media and Client are on Windows 2008 R2 and netbackup 7.7.2

10/01/2018 07:51:51 - begin writing
10/01/2018 08:21:44 - Error bpbrm (pid=176912) socket read failed, An existing connection was forcibly closed by the remote host. (10054)
10/01/2018 08:21:44 - Error bptm (pid=174536) socket operation failed - 10054 (at ../child.c.1306)
10/01/2018 08:21:44 - Error bptm (pid=174536) unable to perform read from client socket, connection may have been broken
10/01/2018 08:21:50 - Info dt3asbprobkp02 (pid=176732) StorageServer=PureDisk:dt3asbprobkp02; Report=PDDO Stats for (dt3asbprobkp02): scanned: 10006277 KB, CR sent: 435110 KB, CR sent over FC: 0 KB, dedup: 95.7%, cache disabled
10/01/2018 08:21:51 - Error bpbrm (pid=176912) could not send server status message
10/01/2018 08:21:54 - Info bpbkar32 (pid=28440) done. status: 13: file read failed
10/01/2018 08:21:54 - end writing; write time: 0:30:03
file read failed (13)

 Appreciate your help in advance.

[Marianne]

You need logs to find out what happened between these 2 timestamps:

10/01/2018 07:51:51 - begin writing
10/01/2018 08:21:44 - Error bpbrm (pid=176912) socket read failed, An existing connection was forcibly closed by the remote host. (10054)

Firstly, bpbkar on the client. 
This will give information about each file that is read and sent to the media server.

Secondly, bpbrm and bptm on the media server.
bptm will show files and data received from the client and up to when.
bpbrm will show metadata received from the client and if timeout occurred due to no updates received within Client Read Timeout.

Logging level 3 will be good.