File Read Failed (13) on Windows client

[WayneLackey]

I have a Windows Server 2003 client (w/NBU 7.0 client installed) that had been backing up successfully until a couple of nights ago, when it failed with the status 13 error after backing up for 45 minutes. The job details follow below:

4/12/2012 9:19:20 PM - requesting resource poseidon-hcart2-robot-tld-0
4/12/2012 9:19:20 PM - requesting resource poseidon.NBU_CLIENT.MAXJOBS.bkusoluspsdfs02
4/12/2012 9:19:20 PM - requesting resource poseidon.NBU_POLICY.MAXJOBS.bkusolusps
4/12/2012 9:19:20 PM - awaiting resource poseidon-hcart2-robot-tld-0 - No drives are available
4/12/2012 9:33:10 PM - granted resource poseidon.NBU_CLIENT.MAXJOBS.bkusoluspsdfs02
4/12/2012 9:33:10 PM - granted resource poseidon.NBU_POLICY.MAXJOBS.bkusolusps
4/12/2012 9:33:10 PM - granted resource QUA050
4/12/2012 9:33:10 PM - granted resource HP.ULTRIUM2-SCSI.003
4/12/2012 9:33:10 PM - granted resource poseidon-hcart2-robot-tld-0
4/12/2012 9:33:10 PM - estimated 18096987 Kbytes needed
4/12/2012 9:33:10 PM - started
4/12/2012 9:33:11 PM - started process bpbrm (3912)
4/12/2012 9:33:15 PM - connecting
4/12/2012 9:33:18 PM - connected; connect time: 00:00:03
4/12/2012 9:33:22 PM - mounted
4/12/2012 9:33:22 PM - positioning QUA050 to file 2
4/12/2012 9:33:24 PM - positioned QUA050; position time: 00:00:02
4/12/2012 9:33:24 PM - begin writing
4/12/2012 10:18:12 PM - Error bpbrm(pid=3912) socket read failed, An existing connection was forcibly closed by the remote host.  (10054)
4/12/2012 10:18:12 PM - Error bptm(pid=6072) socket operation failed - 10054 (at child.c.1294)     
4/12/2012 10:18:12 PM - Error bptm(pid=6072) unable to perform read from client socket, connection may have been broken
4/12/2012 10:19:17 PM - Error bpbrm(pid=3912) could not send server status message      
4/12/2012 10:19:19 PM - end writing; write time: 00:45:55
file read failed(13)

Not sure what any of that 'socket read failed' stuff means, does anyone have any suggestions about what I should look at first?

Thanks,

Wayne

[Will_Restore]

Resolution:
The following things can all help prevent Status 13 errors:
 

• Ensure that the latest service packs for all products and components (SQL, Exchange, Notes, etc.) have been installed.
• Ensure that all the network settings throughout the environment (NICs, hubs, switches, routers, etc.) are set to full duplex, not half duplex
• Increase the timeout settings on the NIC, if available.
• Try a different NIC, if available.
• If NIC teaming is implemented, deactivate for testing purposes.  Refer to Microsoft Knowledge Base Q Article 254101.

 http://support.microsoft.com/default.aspx?scid=kb;en-us;254101
 

• For mailbox backups, it is not recommended to run anti-virus software against the mail directories due to database locking issues.  Verify if the anti-virus runs during this time frame and exclude the mail directories from being scanned if necessary.
• For database backups, review the file system and database backups and ensure that schedules do not overlap.  Also, review any database maintenance schedules and ensure that they do not overlap with backup schedules.

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

[Will_Restore]

Connection reset by peer.

An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, the host or remote network interface is disabled, or the remote host uses a hard close (see setsockopt for more information on the SO_LINGER option on the remote socket). This error may also result if a connection was broken due to keep-alive activity detecting a failure while one or more operations are in progress. Operations that were in progress fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET

http://msdn.microsoft.com/en-us/library/windows/desktop/ms740668(v=vs.85).aspx

[Marianne]

This seems like a 'break in communication' from the client's side. Ensure that you have the following log folders on the media server for troubleshooting: bpbrm and bptm. The logs needed on the client depends on the backup type. For Exchange and MS-Windows, bpbkar. For SQL, dbclient. If you have a set of logs that covers the failure, please rename to process name (e.g bpbkar.txt) and post as attachment. See if you can find out what else is happening on the client at the same time as the backup. Event Viewer Application log might be helpful.