10-13-2014 08:40 AM
Hi All,
I am running with NetBackup 7.5.0.6 version in winodws environment.
Cluster backup is getting failed continuously since sep-23rd, backups were successfully completed till Sep-22nd. However the backups are successfully completing when we give the physical node. Below mentioned is the error message.
9/23/2014 8:21:51 PM - Error bpbrm(pid=2264) socket read failed, An existing connection was forcibly closed by the remote host. (10054)
9/23/2014 8:21:59 PM - end writing
9/23/2014 8:22:00 PM - Info bpbkar32(pid=0) done. status: 13: file read failed
file read failed(13)
This is the problem...
I have tried increasing the client read and file browse time out to 900 but no luck.
If some one faced similar issue, kindly advise how it got resovled.
Please let me know if any more informations required.
Solved! Go to Solution.
10-24-2014 06:28 AM
this issue resolved after upgrading the netbackup from 7.5.0.6 to 7.5.0.7
10-13-2014 09:00 AM
Please help me to understand the actual cause...
10-13-2014 09:52 AM
10054 is a winsock error. The remote host is your cluster node. For some reason the node is dropping out during the backup. Increasing the timeout is good, but to get the full picture, review the bpbkar log.
Also what version of NetBackup and what OS is the servers?
If windows 2003 check to make sure TCP chimney offload is disabled.
10-13-2014 10:17 AM
NetBackup 7.5.0.6
OS: 2003 datacenter edition
TCP chimney offload is disabled.
If TCP chimney issue is causing the backup error, then the node backup also should fail i believe. I think something else is the problem.
10-13-2014 12:40 PM
10-23-2014 07:08 AM
You will need to check logs.
bptm and bpbrm on media server
bpcd and bpbkar on client.
10-24-2014 06:28 AM
this issue resolved after upgrading the netbackup from 7.5.0.6 to 7.5.0.7
10-24-2014 09:46 AM
Update is good but not likely the true fix. Perhaps a reboot or some other change fixed the network problem.
10-24-2014 10:44 AM