cancel
Showing results forΒ 
Search instead forΒ 
Did you mean:Β 

socket write failed(24)

O-a
Level 4

Hello all

i trying to run full backup and every timr the backup failed  with status 24.

the server virtual server ,vmware 5.02 platform

window server 2003 r2

backup client version is 6.5.6

from the bpbkar log

4:21:17.358 AM: [3020.2108] <4> V_Snapshot::V_Snapshot_AddMappings: INF - V_Snapshot_AddMappings input parameters:
 source path = "C:\"
 snap path = "\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy157\"
 mount path = "(null)"
4:21:17.358 AM: [3020.2108] <4> V_Snapshot::V_GetSourceVolume: INF - source = "C:\"
 snapshot = "\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy157\"
4:21:17.358 AM: [3020.2108] <4> V_Snapshot::V_Snapshot_AddMappings: INF - source volume name from V_GetSourceVolume = "\\?\Volume{707ec9d3-1c6e-11de-8922-806e6f6e6963}\"
4:21:17.358 AM: [3020.2108] <4> V_Snapshot::V_Snapshot_AddMappings: INF - snapshot volume name from V_GetSourceVolume = "GLOBALROOT\Device\HarddiskVolumeShadowCopy157"
4:21:17.358 AM: [3020.2108] <4> V_Snapshot::V_Snapshot_AddMappings: INF - Volume Snapshot Mapping: \\?\Volume{707ec9d3-1c6e-11de-8922-806e6f6e6963}\ --> GLOBALROOT\Device\HarddiskVolumeShadowCopy157
4:21:17.358 AM: [3020.2108] <4> V_Snapshot::V_Snapshot_ParseBpfisOutput: INF - Snapshot creation, FIS_ID: msrv1_1394485256
4:21:17.358 AM: [3020.2108] <4> V_Snapshot::V_Snapshot_CreateSnapshot: INF - Snapshot creation was successful
4:21:17.358 AM: [3020.2108] <4> V_Snapshot::V_Snapshot_CreateSnapshot: INF - Snapshot provider: VSS
4:21:17.358 AM: [3020.2108] <4> V_Snapshot::V_Snapshot_CreateSnapshot: INF - ======================================================================
4:21:17.358 AM: [3020.2108] <2> tar_base::V_vTarMsgW: INF - Volume snapshots enabled
4:21:17.358 AM: [3020.2108] <2> tar_base::V_vTarMsgW: WRN - old TIR info file 'C:\Program Files\Veritas\NetBackup\tir_info\C\NetBackup_file_info.WinCentral' is missing. Backing up everything in 'C:'
4:21:17.358 AM: [3020.2108] <2> tar_base::V_vTarMsgW: WRN - old TIR info file 'C:\Program Files\Veritas\NetBackup\tir_info\C\NetBackup_file_info.WinCentral' is missing. Backing up everything in 'C:'
4:21:21.998 AM: [3020.2108] <4> dos_backup::tfs_scannext: INF - Skipping file: C:\Documents and Settings\Administrator\NTUSER.DAT.LOG
4:21:29.326 AM: [3020.2108] <4> dos_backup::tfs_scannext: INF - Skipping file: C:\Documents and Settings\Administrator\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat.LOG
4:22:11.139 AM: [3020.2108] <4> dos_backup::tfs_scannext: INF - Skipping file: C:\Documents and Settings\LocalService\ntuser.dat.LOG
4:22:11.326 AM: [3020.2108] <4> dos_backup::tfs_scannext: INF - Skipping file: C:\Documents and Settings\LocalService\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat.LOG
4:22:11.436 AM: [3020.2108] <4> dos_backup::tfs_scannext: INF - Skipping file: C:\Documents and Settings\NetworkService\ntuser.dat.LOG
4:22:11.670 AM: [3020.2108] <4> dos_backup::tfs_scannext: INF - Skipping file: C:\Documents and Settings\NetworkService\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat.LOG
4:22:12.264 AM: [3020.2108] <4> tar_backup_tfi::backup_send_chkp_data_state: INF - checkpoint message: CPR - 339418422 3020 0 0 92947 0 0 0 12 909798400 161 9 127 142239 1 89 /C/Documents and Settings/ShlomiGa/Application Data/Microsoft/SystemCertificates/My/CTLs/
4:22:24.545 AM: [3020.2108] <4> dos_backup::tfs_include: INF - folder (OGTKv136) has been created recently (since 9/27/2013 1:39:10 PM).  It will be backed up in full.
4:22:24.545 AM: [3020.2108] <4> dos_backup::tfs_include: INF - folder (OGTKv136) has been created recently (since 9/27/2013 1:39:10 PM).  It will be backed up in full.
4:23:45.780 AM: [3020.2108] <32> TransporterRemote::write[2](): FTL - SocketWriteException: send() call failed, could not write data to the socket, possible broken connection.
4:23:45.780 AM: [3020.2108] <16> NBUException::traceException(): (
An Exception of type [Symantec::NetBackup::Ncf::OperationFailedException] was thrown. Details about the exception follow...:
Error code  = (-1008).
Src file    = (D:\656\src\cl\clientpc\util\tar_tfi.cpp).
Src Line    = (276).
Description = (%s getBuffer operation failed).
Operation type=().
)
4:23:45.780 AM: [3020.2108] <16> NBUException::traceException(): (
An Exception of type [Symantec::NetBackup::Ncf::SocketWriteException] was thrown. Details about the exception follow...:
Error code  = (-1027).
Src file    = (TransporterRemote.cpp).
Src Line    = (310).
Description = (send() call failed, could not write data to the socket, possible broken connection).
Local IP=(). Remote IP=(). Remote Port No.=(0).
No. of bytes to write=(131072) while No. of bytes written=(0).
)
4:23:45.780 AM: [3020.2108] <2> tar_base::V_vTarMsgW: FTL - socket write failed
4:23:45.780 AM: [3020.2108] <4> tar_backup::backup_done_state: INF - number of file directives not found: 0
4:23:45.780 AM: [3020.2108] <4> tar_backup::backup_done_state: INF -     number of file directives found: 12
4:23:45.780 AM: [3020.4288] <4> tar_base::keepaliveThread: INF - keepalive thread terminating (reason: WAIT_OBJECT_0)
4:23:45.780 AM: [3020.2108] <4> tar_base::stopKeepaliveThread: INF - keepalive thread has exited. (reason: WAIT_OBJECT_0)
4:23:45.780 AM: [3020.2108] <2> tar_base::V_vTarMsgW: INF - EXIT STATUS 24: socket write failed
4:23:45.780 AM: [3020.2108] <4> tar_backup::backup_done_state: INF - Not waiting for server status
4:23:46.905 AM: [3020.2108] <4> ov_log::OVLoop: INF - Cycling log file
4:23:46.905 AM: [3020.2108] <4> ov_log::OVClose: INF - Closing log file: C:\Program Files\Veritas\NetBackup\logs\BPBKAR\031014.LOG
 

 

 I followed this article-http://www.symantec.com/business/support/index?page=content&id=TECH150369&profileURL=https%3A%2F%2Fs...

and stil getting the same error

i googled this error and follwed the advices from several blogs(include  symantec blogs) and nothing seems working

 

appreciate any help

 

6 REPLIES 6

revarooo
Level 6
Employee

for the record, NetBackup 6.5 is no longer supported.

As for status 24, these come up all the time and are rarely ever anything to do with Netbackup.

When was the last time the backup worked?

Check these technotes

http://www.symantec.com/business/support/index?page=content&id=TECH150369

http://www.symantec.com/business/support/index?page=content&id=TECH34183

http://www.symantec.com/business/support/index?page=content&id=HOWTO90453

 

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Status 24 on W2003 clients is most often caused by TCP Chimney.

See: http://www.symantec.com/docs/TECH197934

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

sri_vani
Level 6
Partner

BPBKAR Error:

<32> TransporterRemote::write[2](): FTL - SocketWriteException: send() call failed, could not write data to the socket, possible broken connection.
4:23:45.780 AM: [3020.2108] <16> NBUException::traceException(): (
An Exception of type [Symantec::NetBackup::Ncf::OperationFailedException] was thrown. Details about the exception follow...:
Error code  = (-1008).
Src file    = (D:\656\src\cl\clientpc\util\tar_tfi.cpp).
Src Line    = (276).
Description = (%s getBuffer operation failed).
Operation type=().
)
4:23:45.780 AM: [3020.2108] <16> NBUException::traceException(): (
An Exception of type [Symantec::NetBackup::Ncf::SocketWriteException] was thrown. Details about the exception follow...:

Error code  = (-1027).
Src file    = (TransporterRemote.cpp).
Src Line    = (310).
Description = (send() call failed, could not write data to the socket, possible broken connection).
Local IP=(). Remote IP=(). Remote Port No.=(0).
No. of bytes to write=(131072) while No. of bytes written=(0).

Environemt:

6.5.x and windows 2003

To resolve this please verify below TN:

http://www.symantec.com/business/support/index?page=content&id=TECH130730

 

Open a command prompt as Administrator and enter vssadmin list providers command. This eventually returned to the command prompt with no information displayed. The customer was able to use the Windows/SysInternals process explorer to discover which process(es) (svchost) were dependent on these failed provider(s) and after terminating the process(es) was able to reregister all the required components/providers. This allowed the client to be backed up without further incident.
 
Note that netstat -a did not show abnormal socket usage and client was not exceeding memory, processor, or network utilization. Name resolution was confirmed through bpclntcmd and valid communication confirmed through bptestbpcd. Backups would start and a small amount of data would transfer before failing.

 

 

O-a
Level 4

thanks all for your help

i changed the TCP Chimney settings and did all other recommendations but the job is still failed with the same eror

last time the job succeeded was few weeks ago.

 

do you have more ideas?

sri_vani
Level 6
Partner

please provide us the vssadmin list providers and bptestbpcd and bpclntcmd outputs

O-a
Level 4

bptestbpcd from master/media server(same machine)-hope this this is the right options

C:\bptestbpcd -client myoram2
1 1 1
10.10.1.82:2698 -> 10.11.100.2:13724
10.10.1.82:2699 -> 10.11.100.2:13724
10.10.1.82:2700 -> 10.11.100.2:13724

vss admin output

C:\WINDOWS\system32>vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.

Provider name: 'Microsoft Software Shadow Copy provider 1.0'
   Provider type: System
   Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Version: 1.0.0.7

bpclntcmd output

C:\>bpclntcmd -pn
expecting response from server backupsrv
backupsrv.mada.co.il backupsrv 10.10.1.82 2731

C:\>bpclntcmd -self
gethostname() returned: backupsrv
host backupsrv: backupsrv.mada.co.il at 10.10.1.82 (0x52010a0a)
aliases:

C:\>bpclntcmd -ip 10.11.100.2
checkhaddr: host   : |MYoram2: |MYoram2 at 10.11.100.2 (0x2640b0a)
checkhaddr: aliases:.

 

 

thanks