socket write failed(24)
Updated: 04 Nov 2009 | 5 comments
Today in my BLOG i would like to discuss the ""socket write failed(24)"" shown in the Activity Monitor in the result of a failed backup job
ENVIRONMENT
Server
Windows 2003 Server R2
Netbackup Server 6.5
Client
Windows2003 Server R2
PROBLEM
I was facing the error socket write failed(24) when i initiated a job and faced the mentioned error in Activity Monitor
RESOLUTION
I simply changed the property values from Enable to Disable from the NIC card properties. You can see the below picture for your help
Forum DIscussion
https://www-secure.symantec.com/connect/forums/bmr-backup-failed#comment-3196181
blog entry Filed Under:
About Backup & Archiving Community Blog
The Backup & Archiving Community Blog is the perfect place to share short, timely insights including product tips, news and other information relevant to the Backup & Archiving community. Any authenticated Connect member can contribute to this blog. Filter by:
Blog Tags
Enterprise Vault NetBackup Backup Exec 12.x Symantec System Recovery (formerly Backup Exec System Recovery) 2010 Tip/How to 11.x Basics 10.x and Earlier Best Practice NetBackup PureDisk Upgrade Agents OpsCenter Features BESR 8.x NetBackup RealTime Configuring Online Storage for Backup Exec Installing Online Backup BESR 2010 MS Exchange Replication Exec
Comments
This is one of those cases where the picture is worth alot less than a few well-chosen words. I'm going to guess that you changed the status of the two properties "Offload Checksum" and "OffLoad TCP largeSend" to 'disabled', since you drew a red rectangle around them. OTOH, the property "802.1Q/1pVlan Tagging" is highlighted, maybe that's the one you mean? I'll try that one 2nd...
Was this change done on the
Was this change done on the master server or the client?
Thanks
Good question rcmonis. I
First thanks to all
Good question rcmonis. I wrote this BLOG in 2009. I really forgot to mention the query which you raised. I might think that i did it on the Client Side.
Thanks for your input rcmonis
Any comment will be appreciated. Mark as Solution if your query is resolved
__________________
Thanks in Advance
Zahid Haseeb
zahidhaseeb.wordpress.com
Zahid also conveniently
Zahid also conveniently 'forgot' to give credit to the Symantec Technote where he got the information from....
It used to be: http://support.veritas.com/docs/304578
It is now: http://www.symantec.com/business/support/index?pag...
The TN contains examples for different network cards and then says the following below all the screen dumps:
"Symantec Support recommends setting all these values to Off/Disabled/None (or whatever value means "off") "
We disable TCP Chimney on media servers and clients.
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows.
Handy NBU links
Performance
Does this will affect the system performance on the client... Or will this change affect any other process/applications that are running on the client machine????
Would you like to reply?
Login or Register to post your comment.