Backup failing with RC 40

[sabby]

I have a Windows 2003 client backing up under Windows 2008 Master Server Ver NBU 7.0. The issue is the client is backing up approx 250-300 GB data in a differential incremental backup which is scheduled every weekday and the job is getting successful in 4-5 attempts everytime(after resuming it when failing with RC 40).

I have checked the connectivity between the master and the client(bpclntcmd -pn works fine).

Since the error is "Network Connection Broken", what might the issue be with the job failing 4-5 times after some time interval. Should I need to so some policy changes since the amount of data backing is so large?

[revarooo]

Seems like you probably have a network issue between the client and media server.

Have you tried increasing the CLIENT_READ_TIMEOUT on the media server. Goto Host Properties -> Media server -> media server name -> Timeouts and change the Client Read Timeout. If it's set to the default of 300, change it to 1800, if it's already set to a non-default setting, try doubling it.

[sabby]

Revaroo i'll try this workaround and post the results. Will this parameter be affecting the other clients hosted on the same media server?

One more thing I was thinking that is it correct to add a client in a policy which is backing 250-300 GB in just a DINC backup. Can we try changing the schedule of the policy, for say extending the backup window?

[revarooo]

Sabby, 

Yes it would, but if they are not erroring, then this change will have no affect on other clients.

As for your other question, it's not relevant to your initial issue. You can extend the backup if you want, but this is not the cause of the status 40. Any issues with clients falling outside of the schedule would result in a status 196

[sabby]

Revaroo,

The CLIENT_READ_TIMEOUT settings on the media server was previously set on 600 seconds, I doubled it to make it 1200. I then did a bprdreq -rereadconfig to refresh all the NBU daemons.

The job was still failing with RC 40.

Below is the child job log:

-----

7/16/2012 11:43:37 PM - estimated 312517820 Kbytes needed
7/16/2012 11:43:40 PM - started process bpbrm (2140)
7/16/2012 11:44:04 PM - mounting XYZ
7/16/2012 11:44:06 PM - connecting
7/16/2012 11:44:08 PM - connected; connect time: 00:00:02
7/16/2012 11:44:55 PM - mounted; mount time: 00:00:51
7/16/2012 11:44:58 PM - positioning XYZ to file 13
7/16/2012 11:45:30 PM - positioned XYZ; position time: 00:00:32
7/16/2012 11:45:30 PM - begin writing
network connection broken(40)
7/17/2012 1:12:01 AM - Critical bpbrm(pid=5172) from client ABCDE: FTL - socket write failed    
7/17/2012 1:12:02 AM - Error bpbrm(pid=5172) could not send server status message

"The job failed after writing approx 36 GB"