cancel
Showing results for 
Search instead for 
Did you mean: 

network read failed(42) restoring large windows 2008 R2 file server

Slartybardfast
Level 4

Hello Forum,

We are trying to migrate to new storage and restores in our environment is faster. When I attempt a restore of a large area eg 22 million files plus. This the output from the details tab:

12-Jul-2018 21:05:09 - begin Restore
12-Jul-2018 21:05:10 - Info bprd (pid=17524) Found (22,079,589) files in (39) images for Restore Job ID 524622.xxx
12-Jul-2018 21:36:57 - Info bprd (pid=17524) Estimated time to assemble file list: (0) days, (6) hours, (10) min, (20) sec
12-Jul-2018 23:45:57 - Info bprd (pid=17524) Searched (   250,000) files of (22,079,589) files for Restore Job ID 524622.xxx
13-Jul-2018 01:05:16 - Info bprd (pid=17524) Searched (   500,000) files of (22,079,589) files for Restore Job ID 524622.xxx
13-Jul-2018 02:59:47 - Info bprd (pid=17524) Searched (   750,000) files of (22,079,589) files for Restore Job ID 524622.xxx
13-Jul-2018 04:04:26 - Info bprd (pid=17524) Searched ( 1,000,000) files of (22,079,589) files for Restore Job ID 524622.xxx
13-Jul-2018 06:11:57 - Info bprd (pid=17524) Searched ( 1,250,000) files of (22,079,589) files for Restore Job ID 524622.xxx
13-Jul-2018 07:00:59 - end Restore; elapsed time 9:55:50
network read failed  (42)

Will increasing the client timeouts on the client and media servers help?

Kind regards

 

1 REPLY 1

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

This looks like bprd on the master timing out while trying to build the file list.

It initially estimated that it will take just over 6 hours  :
 Estimated time to assemble file list: (0) days, (6) hours, (10) min, (20) sec

After 10 hours, bprd timed out (gave up?). 
No child processes (bpbrm, bptm, tar, etc) was even started.

The amount of processing that is needed for a single restore job seems to be too high for your master server. 
My suggestion is to break up the restore into smaller 'chunks'.