Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

socket write failed (24)

Created: 06 Nov 2013 • Updated: 06 Nov 2013 | 13 comments

I have try to restore a server, but it give me this in the log file. Did search for help, but could not find help on this.

11/07/2013 07:56:24 - begin Restore
11/07/2013 07:57:11 - number of images required: 1
11/07/2013 07:57:11 - media needed: CTB384
11/07/2013 07:57:47 - restoring from image inter-apps-1.ipms.co.za_1380474963
11/07/2013 07:57:50 - Info bpbrm (pid=6616) telling media manager to start restore on client
11/07/2013 07:57:53 - connecting
11/07/2013 07:57:54 - Info bptm (pid=5496) Waiting for mount of media id CTB384 (copy 1) on server prasagppbck02.prasa.com.
11/07/2013 07:57:54 - started process bptm (pid=5496)
11/07/2013 07:57:54 - mounting CTB384
11/07/2013 07:57:54 - requesting resource CTB384
11/07/2013 07:57:54 - granted resource  CTB384
11/07/2013 07:57:54 - granted resource  HP.ULTRIUM5-SCSI.002
11/07/2013 07:57:55 - Info bpbrm (pid=2060) start tar32 on client
11/07/2013 07:57:56 - Info bptm (pid=5496) INF - Waiting for mount of media id CTB384 on server prasagppbck02.prasa.com for reading.
11/07/2013 07:58:02 - Info tar32 (pid=5948) Restore started.
11/07/2013 07:58:02 - connected; connect time: 0:00:00
11/07/2013 07:59:07 - mounted CTB384; mount time: 0:01:13
11/07/2013 07:59:07 - Info bptm (pid=5496) CTB384
11/07/2013 07:59:09 - Info bptm (pid=5496) INF - Waiting for positioning of media id CTB384 on server prasagppbck02.prasa.com for reading.
11/07/2013 07:59:09 - positioning CTB384 to file 149
11/07/2013 08:00:43 - positioned CTB384; position time: 0:01:34
11/07/2013 08:00:43 - begin reading
11/07/2013 08:00:46 - Info bpbrm (pid=6616) sending media manager msg: CONTINUE RESTORE
11/07/2013 08:03:20 - Critical bpbrm (pid=2060) from client inter-apps-1.ipms.co.za: FTL - tar received an invalid archive
11/07/2013 08:03:20 - Info tar32 (pid=5948) done. status: 13
11/07/2013 08:03:20 - Error bptm (pid=4836) cannot write data to socket, 10053
11/07/2013 08:03:20 - Info tar32 (pid=5948) done. status: 13 - file read failed
11/07/2013 08:03:20 - Info bpbrm (pid=6616) child done, status 13
11/07/2013 08:03:20 - Info bpbrm (pid=6616) sending media manager msg: STOP RESTORE inter-apps-1.ipms.co.za_1380474963
11/07/2013 08:03:22 - Error bptm (pid=4836) The following files/folders were not restored:
11/07/2013 08:03:22 - Error bptm (pid=4836) UTF - /F/OraApp/Apache/Apache/bin/osslpassword.exe
11/07/2013 08:03:23 - Error bptm (pid=4836) UTF - /F/OraApp/Apache/Apache/bin/osso1013
11/07/2013 08:03:23 - Error bptm (pid=4836) UTF - /F/OraApp/Apache/Apache/bin/pconvert.exe
11/07/2013 08:03:24 - Error bptm (pid=4836) UTF - /F/OraApp/Apache/Apache/bin/rotatelogs.exe
11/07/2013 08:03:24 - Error bptm (pid=4836) UTF - /F/OraApp/Apache/Apache/bin/ssomigrate.exe
11/07/2013 08:03:25 - Error bptm (pid=4836) UTF - /F/OraApp/Apache/Apache/bin/ssotransfer.bat
11/07/2013 08:03:25 - Error bptm (pid=4836) UTF - /F/OraApp/Apache/Apache/bin/startapache.exe
11/07/2013 08:03:25 - Error bptm (pid=4836) UTF - /F/OraApp/Apache/Apache/cgi-bin/
11/07/2013 08:03:26 - Error bptm (pid=4836) UTF - /F/OraApp/Apache/Apache/conf/
11/07/2013 08:03:26 - Error bptm (pid=4836) UTF - /F/OraApp/Apache/Apache/conf/Copy of httpd.conf
11/07/2013 08:03:27 - Error bptm (pid=4836) more than 10 files were not restored, remaining ones are shown in the progress log.
11/07/2013 08:04:21 - Warning bprd (pid=5184) Restore must be resumed prior to first image expiration on 2014/09/29 07:16:03 PM
11/07/2013 08:04:21 - end Restore; elapsed time 0:07:57
socket write failed  (24)
 

Operating Systems:

Comments 13 CommentsJump to latest comment

Jaydeep S's picture

There could be a lot of reasons that you could get status 24. Here are some links that could help

https://www-secure.symantec.com/connect/forums/socket-write-failed24-0

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

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

VJware's picture

bptm, bprd etc look like Netbackup daemons. Would you confirm if you are using Backup Exec or Netbackup. If Netbackup, their forum is @ https://www-secure.symantec.com/connect/backup-and...

Marianne's picture

I have try to restore a server...... 

Does this mean that you have tried a full system restore? To same or different hardware?

These HOWTO TN contains step-by-step instructions for full system restore:

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

Ensure all log folders exist on the client as per the TN as well as bptm and bpbrm logs on the media server.

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

Hendrikbez's picture

I am new to this, still waiting to go on a course for it, were just ask to do backup.

I am trying to restore only 3 folders to the client.

First time I do a restore to client self.  No one here knows how to do it.

Hendrikbez's picture

I am read this in a ohter post, do I run this on the backupserver or on the client.

4- In case there is an Antivirus running, turn it off for troubleshooting proposes.

5- Disable autotuning and chimney features, from command prompt run:

netsh int tcp set global autotuning=disabled

netsh int tcp set global chimney=disabled

sri vani's picture

can u plz provide us more details like -

master/media/client netbackup versions.

also plz specify your policy type

Marianne's picture

Apologies for the silence...

The fact that you are new to NBU makes me think that you may be doing something wrong with the setup and selection of restore parameters.

Firstly - are you doing the restore from the master or the client?

On the master - are you starting with File -> Specify NetBackup Machines... ?

If you don't mind, please take screenshots of the steps you are performing and paste them in a Word doc that you can upload here as File Attachment.

TCP Chimney should only be disabled on Windows 2003 servers and clients. Leave it on for W2008 servers and clients.

Before running another restore attempt, create the following log folders:

On master: bprd (Restart NBU Request Service to enable log)

On media server: bpbrm and bptm

On client: bpcd and tar

(Create folders under ...\veritas\netbackup\logs)

If restore fails again, copy logs to reflect process name (e.g. bprd.txt) and upload as File attachments.

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

Hendrikbez's picture

Hi Marianne

Ok here are the screenshots in a word doc.

Wil wait for you before I try the other things that you have given me.

AttachmentSize
A1.doc 126 KB
Marianne's picture

Nothing wrong with the way you are doing the restore.

We need the logs that I have listed above....

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

Hendrikbez's picture

Will get the logs, then I will upload them

Hendrikbez's picture

I am getting this error, I can not see if chimney is disabled.

AttachmentSize
A2.doc 25.5 KB
Marianne's picture

So, does this mean that this is a W2003 client?

See this TN for various ways to disable TCP Chimney: http://www.symantec.com/docs/TECH60844

'Netsh int ....' should be typed all in one line. Seems you pressed Enter after netsh?

Hope you have in the meantime enabled all the logs?

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