cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Veritas.com
Support

Restore failing with error : Error bptm ... cannot write data to socket, Broken pipe

Rohit_new
Level 4
Certified

‎04-06-2009 01:02 PM

Hello,

While restoring data of a unix client we faced the error : Cannot write data to socket, Broken pipe.
We are having Netbackup 6.5.3.1 master server ( Solaris ) , client is also Solaris.
Please find the below logs :. This is a very critical restore for us. Please suggest

04/06/2009 14:10:03 - begin Restore
04/06/2009 14:10:08 - number of images required: 1
04/06/2009 14:10:08 - media needed: 330078
04/06/2009 14:10:08 - media needed: 330068
04/06/2009 14:10:47 - restoring from image cbzls13.ced.corp.cummins.com_1233864606
04/06/2009 12:06:56 - connecting
04/06/2009 12:06:57 - connected; connect time: 0:00:00
04/06/2009 14:11:06 - requesting resource 330078
04/06/2009 14:11:07 - granted resource  330078
04/06/2009 14:11:07 - granted resource  HP.ULTRIUM4-SCSI.000
04/06/2009 12:07:07 - started process bptm (pid=74058)
04/06/2009 12:07:09 - mounting 330078
04/06/2009 12:08:09 - mounted 330078; mount time: 0:01:00
04/06/2009 12:08:15 - positioning 330078 to file 816
04/06/2009 12:08:50 - positioned 330078; position time: 0:00:35
04/06/2009 12:08:50 - begin reading
04/06/2009 12:09:20 - positioning 330078 to file 817
04/06/2009 12:09:20 - positioned 330078; position time: 0:00:00
04/06/2009 12:09:41 - positioning 330078 to file 818
04/06/2009 12:09:41 - positioned 330078; position time: 0:00:00
04/06/2009 12:10:00 - positioning 330078 to file 819
04/06/2009 12:10:00 - positioned 330078; position time: 0:00:00
04/06/2009 12:10:20 - positioning 330078 to file 820
04/06/2009 12:10:20 - positioned 330078; position time: 0:00:00
04/06/2009 12:10:39 - positioning 330078 to file 821
04/06/2009 12:10:39 - positioned 330078; position time: 0:00:00
04/06/2009 12:11:01 - positioning 330078 to file 822
04/06/2009 12:11:01 - positioned 330078; position time: 0:00:00
04/06/2009 12:11:22 - positioning 330078 to file 823
04/06/2009 12:11:22 - positioned 330078; position time: 0:00:00
04/06/2009 12:11:42 - positioning 330078 to file 824
04/06/2009 12:11:42 - positioned 330078; position time: 0:00:00
04/06/2009 12:19:17 - positioned 330078; position time: 0:00:00
04/06/2009 12:19:29 - Error bptm (pid=74059) cannot write data to socket, Broken pipe
04/06/2009 12:19:36 - Error bptm (pid=74059) The following files/folders were not restored:
04/06/2009 12:19:40 - Error bptm (pid=74059) UTF - /db01/giea/dbi01/oradata/giea/cmm_indices06.dbf
04/06/2009 14:23:46 - restored from image cbzls13.ced.corp.cummins.com_1233864606; restore time: 0:12:59
04/06/2009 14:23:48 - Warning bprd (pid=29879) Restore must be resumed prior to first image expiration on Tue 09 Jun 2009 04:10:06 PM EDT
04/06/2009 14:23:48 - end Restore; elapsed time 0:13:45
the restore failed to recover the requested files (5)
3 REPLIES 3

scorpy_582
Level 6

‎04-06-2009 09:59 PM

http://support.veritas.com/docs/245111
0 Kudos

Gerald_W__Gitau
Level 6
Certified

‎04-07-2009 12:20 AM

Are you doing a redirected restore or from the client itself? You can also try a redirected restore to a different client.
0 Kudos

Taqadus_Rehman
Level 6

‎04-07-2009 01:11 AM

  1. Did you chcange any of the buffer sizes? This could be the problem...
  2. Do check bptm logs for further analysis.
  3. Check any logs on client.
  4. Problem could be the high network load or with the switch/LAN Card or IP configurations as well.
  5. Check tcp_time_wait_interval settings on netbackup, the default 60000 (60 Seconds) you can bring it down to 20000 or less.

Please check the following technotes
http://seer.entsupport.symantec.com/docs/264886.htm
http://seer.entsupport.symantec.com/docs/245111.htm
0 Kudos