Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

network read failed

Updated: 21 May 2010 | 7 comments
rrosario's picture
0 0 Votes
Login to vote

Hello all,

I am gettint the following error:

1/16/2009 15:37:44 - Error bptm (pid=22908) system call failed - Connection reset by peer (at child.c.1296)
11/16/2009 15:37:44 - Error bptm (pid=22908) unable to perform read from client socket, connection may have been broken
11/16/2009 15:37:44 - Error bpbrm (pid=22903) socket read failed: errno = 131 - Connection reset by peer
11/16/2009 15:37:44 - Error bpbrm (pid=22903) could not send server status message
11/16/2009 15:37:46 - end writing; write time: 0:22:30
network read failed (42)

the client is being a windows 2003 and master is solaris 9.

this was working fine till 2days and suddenly its failing with this error.

Please help me resolve this

thanks and regards,
rrosario

discussion Filed Under:

Comments

gavrilov's picture
16
Nov
2009
1 Vote +1
Login to vote

try to connect to clients

try to connect to clients bpcd port from server: telnet <client_name> bpcd

rrosario's picture
16
Nov
2009
0 Votes 0
Login to vote

its all working

everything is working and i am able to get some data also..but ultimatly its failing with this error..

Marianne van den Berg's picture
16
Nov
2009
0 Votes 0
Login to vote

See if this TechNote

See if this TechNote helps:
http://seer.entsupport.symantec.com/docs/304578.htm

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows.
Handy NBU links

rrosario's picture
16
Nov
2009
0 Votes 0
Login to vote

this is my last hope

but i checked and that was diabled....so there isnt anything else i can do about it....i had to get a gud backup of these

NavA's picture
16
Nov
2009
0 Votes 0
Login to vote

reboot client or re-install nic driver

These 2 helped me.

1. reboot client [ if it is safe to do so]

2. re-install/update NIC driver

Stuart Green's picture
17
Nov
2009
0 Votes 0
Login to vote

Is this a timeout issue? Your

Is this a timeout issue?

Your not backing up directories with 10/100 thousands of files and small ones at that?

I have had timeouts/socket problems when this was the issue.

bpbkar logs should be reviewed at VERBOSE = 5 level on the client

Also use the Technote that describes how to use bpbkar_path_tr touch file

http://seer.entsupport.symantec.com/docs/267292.htm

Tip: Get overview/document your NBU environment. Run 'nbsu' and review the output.

• If this provides help, please vote or mark appropriate solution.

rrosario's picture
17
Nov
2009
0 Votes 0
Login to vote

its only ~5.2gigs

i have got only 5.2 gigs.. this thing is i am unable to get the shadow copy components backedup as it fails with 13 error. but other server with the same error is getting backedup...i do not know why this is failing with 42 error...i need to check the NIC on that server...but this is a VM..will try to get this backup through VCB....