cancel
Showing results for 
Search instead for 
Did you mean: 

socet write failed (24)

d-stearns
Level 3
all pc servers back up fine except one, keep getting above error.  Running Netbackup 6.5 on Solaris 10 box trying to back up a PC Server 2003.  Anyone see this before?
1 ACCEPTED SOLUTION

Accepted Solutions

d-stearns
Level 3
Thank you all for your help.  I did a simple thing this weekend and it solved the problem.  I switched the network cable with another PC Client that was backing up.  Finally got a full backup completed and the PC Client I switched to is now receiving the write socket errors, so I will turn this over to the network team to figure out.

View solution in original post

11 REPLIES 11

Wiriadi_Wangsa
Level 4
Employee Accredited

Hi D-stearns,

Ouch, socket write failed is a generic usually-network-related error and can happen any time during backup.

A couple of questions:
- Has it been working before?
- What are you backing up for this client?
- At which point does it fail? right away or somewhere in between/random?
- Any difference in terms of network/NIC setup and NetBackup version between this one and working W2k3 clients?
- Is TCP Chimney Offload enabled? I recommend to disable it.
http://support.veritas.com/docs/296341

http://support.veritas.com/docs/304578


Logs to enable on the media server:
/usr/openv/netbackup/logs/bpbrm/
/usr/openv/netbackup/logs/bpcd/

Logs to enable on the affected client:
- <install dir>\Veritas\NetBackup\logs\bpbkar\
- <install dir>\Veritas\NetBackup\logs\bpcd\
- <install dir>\Veritas\NetBackup\logs\bpfis\

We look at mainly bpbrm and bpbkar logs.

Cheers,
Wiriadi

d-stearns
Level 3

It actually only worked once.  We have this problem on 3 of our servers and they all have a huge amount of data and wondering if that is problem.  It dies very quickly.  The dailies run with no problem, just dies on the fulls, so once again wondering if it can't handle the amount of data?  No problem with other servers running the same OS, but than again no as much data on them.  If we break up the data meaning not backing up the entire c:\ it will work, just a pain to do it that way, have to check for new directories added.

I will look into the chimney stuff, saw that in another post and was curious what that was all about, will read your documentation.  Thanks for suggestions and will respond once I find out.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

TCP Chimney seems if it could be relevant to your situation.
The 1st TN mentioned by Wiriadi has this title:
Windows 2003 client backups exit with status 24 when the network is heavily loaded.

More TN's:
http://seer.entsupport.symantec.com/docs/336452.htm
http://seer.entsupport.symantec.com/docs/329371.htm (should also be relevent to Solaris/Windows combination)

d-stearns
Level 3
Tried running
Netsh int ip set chimney DISABLED
It did not work for me, so maybe it was disabled.  My network people are not familiar with this command.  I was able to get into help and get all the way into the commands up to netsh int ip set -- after set there was not a chimney option available?

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Please ask your network people to read the Microsoft Kb aritcle that is referenced in the 1st TN:
 http://support.microsoft.com/kb/942861

Please also refer them to the Kb Articles as well as the NIC settings mentioned in this TN:
http://seer.entsupport.symantec.com/docs/304578.htm

I  have also posted 2 TN's in me previous post that could be relevant.....

d-stearns
Level 3
I browsed through the first article and I maybe I am missing something.  When getting in the register there is no Services under the CurrentControlSet

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

d-stearns
Level 3
Marianne
After looking around some more my client is running 2003 SP1 and the network card shows to be HPNC362i.  Maybe this has something to do with it?

d-stearns
Level 3
Thank you all for your help.  I did a simple thing this weekend and it solved the problem.  I switched the network cable with another PC Client that was backing up.  Finally got a full backup completed and the PC Client I switched to is now receiving the write socket errors, so I will turn this over to the network team to figure out.

View solution in original post

CRZ
Level 6
Employee Accredited Certified

Do you really need to turn this over to the network team?  It sure sounds like you already figured out that there's a bad cable that needs to be replaced.  :)

Ulhas
Not applicable

I was wondering why only full backup was failing . if the issue is really the cable, even incr should have show network related problems.

 

we too have error codes 24. still trying to get solution.

sudu_mlk
Level 5

We had this kind of issues on the Netbackup server side and when verified the Ethernet card statistics we found huge number of CRC errors and Later we completely relaced the Cables and also connection to switch port and later it went fine without any issues.

These socket write failed issues are generally occur when there is any network related issues. We need monitor network traffic between the Netbackup server/client and switch port.

--SUDU