Socket write failed (24)

[ram619]

Hi all,

Am running on issue with my Win2003 client backup with the error of "Socket write failed (24)"

Below is the scenario:

Full backup for a win2003 client D: drive getting failed with the error code 24. Other C: & system state for the same client completing without any issue. Diff backup for D: getting complete without any issue. The full backup get's failed once it's reached the size of 127GB.

 Below trouble shooting steps has been performed:

* Checked the communication between client & Master server and media server. telnet also working fine.(Since other drives and diff backup's are completing).

* Changed the duplex settings to 1000mbps full.

* Excluded some access denied files.

Still we are geeting the error.

Master,Media & client NBU version: 6.5.6

Master,Media & client OS: win 2003.

[ram619]

Also we have enabled VSS for windows open file backup. Previous it was VSP.

One more point. We have created Storage unit group for this client policy.Hence the backup routed via all the media server's still it's failed with the same error. So no issue with media server also.

[Marianne]

I can see that you have done a good deal of troubleshooting already.

Please try to disable TCP chimney and see if that makes a difference.

See http://www.symantec.com/docs/TECH56950 and

http://www.symantec.com/docs/TECH60844

[ram619]

Marianne,

TCP chimney is in disable mode only.

[ram619]

Hi,

Below is the findings from bpbkar logs by my vendor support. Am not able to get any thing pls review and advice..

  ILC-9th Fl. Location 1,LocalsplOnly ILC-9th Fl. Location 1

It appears to because the backup to fail:

11:54:12.050 PM: [3620.7856] <16> dtcp_read: TCP - failure: recv socket (528) (TCP 10053: Software caused connection abort)"


1:54:11.894 PM: [3620.7856] <4> dos_backup::OVDeInitSpecialInfo: INF - Special Folder: 3 D:\Data Data$
11:54:11.894 PM: [3620.7856] <4> dos_backup::OVDeInitSpecialInfo: INF - Special Folder: 3 D:\Desktop Desktop
11:54:11.894 PM: [3620.7856] <4> dos_backup::OVDeInitSpecialInfo: INF - Special Folder: 3 D:\Images Images
11:54:11.894 PM: [3620.7856] <4> dos_backup::OVDeInitSpecialInfo: INF - Special Folder: 3 D:\IT IT$
11:54:11.894 PM: [3620.7856] <4> dos_backup::OVDeInitSpecialInfo: INF - Special Folder: 3 D:\Logs Logs
11:54:11.894 PM: [3620.7856] <4> dos_backup::OVDeInitSpecialInfo: INF - Special Folder: 3 D:\Printer Printer
11:54:11.894 PM: [3620.7856] <4> dos_backup::OVDeInitSpecialInfo: INF - Special Folder: 3 D:\printer drivers printer drivers
11:54:11.894 PM: [3620.7856] <4> dos_backup::OVDeInitSpecialInfo: INF - Special Folder: 3 D:\RoamingProfiles RoamingProfiles$
11:54:11.894 PM: [3620.7856] <4> dos_backup::OVDeInitSpecialInfo: INF - Special Folder: 3 D:\SOP SOP
11:54:11.894 PM: [3620.7856] <4> dos_backup::OVDeInitSpecialInfo: INF - Special Folder: 3 D:\users users$
11:54:11.894 PM: [3620.7856] <4> dos_backup::OVDeInitSpecialInfo: INF - Special Folder: 3 ILC-10th Fl. Location 1,LocalsplOnly ILC-10th Fl. Location 1
11:54:11.894 PM: [3620.7856] <4> dos_backup::OVDeInitSpecialInfo: INF - Special Folder: 3 ILC-10th Fl. Location 2,LocalsplOnly ILC-10th Fl. Location 2
11:54:11.894 PM: [3620.7856] <4> dos_backup::OVDeInitSpecialInfo: INF - Special Folder: 3 ILC-10th Fl. Location 3,LocalsplOnly ILC-10th Fl. Location 3
11:54:11.894 PM: [3620.7856] <4> dos_backup::OVDeInitSpecialInfo: INF - Special Folder: 3 ILC-10th Fl. Location 4,LocalsplOnly ILC-10th Fl. Location 4
11:54:11.894 PM: [3620.7856] <4> dos_backup::OVDeInitSpecialInfo: INF - Special Folder: 3 ILC-11th Fl. Location 1,LocalsplOnly ILC-11th Fl. Location 1
11:54:11.894 PM: [3620.7856] <4> dos_backup::OVDeInitSpecialInfo: INF - Special Folder: 3 ILC-11th Fl. Location 2,LocalsplOnly ILC-11th Fl. Location 2
11:54:11.894 PM: [3620.7856] <4> dos_backup::OVDeInitSpecialInfo: INF - Special Folder: 3 ILC-11th Fl. Location 3,LocalsplOnly ILC-11th Fl. Location 3
11:54:11.894 PM: [3620.7856] <4> dos_backup::OVDeInitSpecialInfo: INF - Special Folder: 3 ILC-11th Fl. Location 4,LocalsplOnly ILC-11th Fl. Location 4
11:54:11.894 PM: [3620.7856] <4> dos_backup::OVDeInitSpecialInfo: INF - Special Folder: 3 ILC-12th Fl. Location 1,LocalsplOnly ILC-12th Fl. Location 1
11:54:11.894 PM: [3620.7856] <4> dos_backup::OVDeInitSpecialInfo: INF - Special Folder: 3 ILC-9th Fl. Location 1,LocalsplOnly ILC-9th Fl. Location 1
11:54:11.894 PM: [3620.7856] <4> dos_backup::OVDeInitSpecialInfo: INF - Special Folder: 3 ILC-9th Fl. Location 2,LocalsplOnly ILC-9th Fl. Location 2
11:54:11.894 PM: [3620.7856] <4> dos_backup::OVDeInitSpecialInfo: INF - Special Folder: 3 ILC-9th Fl. Location 3,LocalsplOnly ILC-9th Fl. Location 3
11:54:11.894 PM: [3620.7856] <4> dos_backup::OVDeInitSpecialInfo: INF - Special Folder: 3 ILC-9th Fl. Location 4,LocalsplOnly ILC-9th Fl. Location 4
11:54:11.894 PM: [3620.7856] <4> V_LNBackup_End: INF - V_LNBackup_End <Enter> ExitStatus:1 Recycle Logs:0


11:54:12.050 PM: [3620.7856] <16> dtcp_read: TCP - failure: recv socket (528) (TCP 10053: Software caused connection abort)
11:54:13.050 PM: [3620.7856] <16> dtcp_read: TCP - failure: recv socket (528) (TCP 10053: Software caused connection abort)
11:54:14.050 PM: [3620.7856] <16> dtcp_read: TCP - failure: recv socket (528) (TCP 10053: Software caused connection abort)
11:54:15.050 PM: [3620.7856] <16> dtcp_read: TCP - failure: recv socket (528) (TCP 10053: Software caused connection abort)

 

[Marianne]

What is happening prior to the 1st 10053? The lines preceding the first <16> normally contains debug <2> info that could be relevant. How long since start of backup until the <16>  is seen at 11:54:12.050 PM ?

[ram619]

Marianne, We have tunneld down and found the folder where the backup getting fail. The folder contains arround 100 PDF files with 6GB of size. We thought of increasing the file read timeout value in Master server from 1500sec to 3000sec, will this workout. (FYI until june we had a backup for the same folder with same size of content)

[Marianne]

You have not showed us anything that points to File Read Timeout.

That what I had in mind when I responded in my previous post - more info should reveal if this is timeout-related.