cancel
Showing results for 
Search instead for 
Did you mean: 

socket read failed, An existing connection was forcibly closed by the remote host. (10054)

Planters
Level 5

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.

 

1 ACCEPTED SOLUTION

Accepted Solutions

Planters
Level 5

this issue resolved after upgrading the netbackup from 7.5.0.6 to 7.5.0.7

View solution in original post

8 REPLIES 8

Planters
Level 5

Please help me to understand the actual cause...

SymTerry
Level 6
Employee Accredited

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.

Planters
Level 5

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.

Michael_G_Ander
Level 6
Certified
Could be the antivirus, had that experience with an update of the trend micro anti virus
The standard questions: Have you checked: 1) What has changed. 2) The manual 3) If there are any tech notes or VOX posts regarding the issue

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

You will need to check logs.
bptm and bpbrm on media server
bpcd and bpbkar on client.

Planters
Level 5

this issue resolved after upgrading the netbackup from 7.5.0.6 to 7.5.0.7

Will_Restore
Level 6

Update is good but not likely the true fix.  Perhaps a reboot or some other change fixed the network problem.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
I agree. 10054 is a TCP error. Not NBU error.