cancel
Showing results for 
Search instead for 
Did you mean: 

Restore done with Status Code (1) the requested operation was partially successful

Alfins
Not applicable
Partner Accredited

Hi all, 

Can I have a suggestion what I have to do if the restore has done with status code (1) as reffer to the logs below ? Thanks 

08 Jan 15 16:55:20 - begin Restore
08 Jan 15 17:06:42 - Info bpbrm (pid=29679) elapp3 is the host to restore to
08 Jan 15 17:06:42 - Info bpbrm (pid=29679) reading file list from client
08 Jan 15 17:06:43 - Info bpbrm (pid=29679) connecting to bprd to get file list
08 Jan 15 17:06:43 - connecting
08 Jan 15 17:06:43 - Info bpbrm (pid=29679) starting bptm
08 Jan 15 17:06:43 - Info tar (pid=29716) Restore started
08 Jan 15 17:06:43 - connected; connect time: 0:00:00
08 Jan 15 17:06:43 - Info bpbrm (pid=29679) bptm pid: 29717
08 Jan 15 17:06:44 - Info bptm (pid=29717) start
08 Jan 15 17:06:44 - started process bptm (pid=29717)
08 Jan 15 17:06:44 - Info bpdm (pid=29717) reading backup image
08 Jan 15 17:06:44 - Info bptm (pid=29717) using 64 data buffers
08 Jan 15 17:06:46 - Info bptm (pid=29717) Waiting for mount of media id M01580 (copy 1) on server elapp3.
08 Jan 15 17:06:46 - started process bptm (pid=29717)
08 Jan 15 17:06:46 - mounting M01580
08 Jan 15 17:06:46 - Info bptm (pid=29717) INF - Waiting for mount of media id M01580 on server elapp3 for reading.
08 Jan 15 17:07:18 - mounted M01580; mount time: 0:00:32
08 Jan 15 17:07:18 - Info bptm (pid=29717) M01580
08 Jan 15 17:07:18 - Info bptm (pid=29717) INF - Waiting for positioning of media id M01580 on server elapp3 for reading.
08 Jan 15 17:07:18 - positioning M01580 to file 3
08 Jan 15 17:08:40 - positioned M01580; position time: 0:01:22
08 Jan 15 17:10:03 - begin reading
08 Jan 15 17:10:13 - media needed: M01580
08 Jan 15 17:10:13 - media needed: M01767
08 Jan 15 17:10:13 - media needed: M01766
08 Jan 15 17:10:13 - media needed: M01769
08 Jan 15 17:10:13 - media needed: M01770
08 Jan 15 17:10:13 - media needed: M01771
08 Jan 15 17:10:13 - media needed: M01775
08 Jan 15 17:10:13 - media needed: M01776
08 Jan 15 17:10:13 - restoring from image elapp3_1419139530
08 Jan 15 17:10:16 - requesting resource M01580
08 Jan 15 17:10:17 - Waiting for scan drive stop IBMULTRIUM4-TD15, Media server: elapp3
08 Jan 15 17:10:17 - granted resource  M01580
08 Jan 15 17:10:17 - granted resource  IBMULTRIUM4-TD15
08 Jan 15 17:17:58 - Info bptm (pid=29717) waited for empty buffer 1861 times, delayed 13052 times
08 Jan 15 17:17:58 - end reading; read time: 0:07:55
08 Jan 15 17:17:59 - Info tar (pid=29716) done. status: 0
08 Jan 15 17:17:59 - Info bptm (pid=29717) completed reading backup image
08 Jan 15 17:17:59 - Info tar (pid=29716) done. status: 0: the requested operation was successfully completed
08 Jan 15 17:17:59 - Info bptm (pid=29717) EXITING with status 0 <----------
08 Jan 15 17:18:00 - Info bpbrm (pid=12501) elapp3 is the host to restore to
08 Jan 15 17:18:01 - Info bpbrm (pid=12501) reading file list from client
08 Jan 15 17:18:01 - Info bpbrm (pid=12501) connecting to bprd to get file list
08 Jan 15 17:18:01 - connecting
08 Jan 15 17:18:01 - Info bpbrm (pid=12501) starting bptm
08 Jan 15 17:18:01 - Info tar (pid=12554) Restore started
08 Jan 15 17:18:01 - connected; connect time: 0:00:00
08 Jan 15 17:18:01 - Info bpbrm (pid=12501) bptm pid: 12555
08 Jan 15 17:18:02 - Info bptm (pid=12555) start
08 Jan 15 17:18:02 - started process bptm (pid=12555)
08 Jan 15 17:18:02 - Info bpdm (pid=12555) reading backup image
08 Jan 15 17:18:02 - Info bptm (pid=12555) using 64 data buffers
08 Jan 15 17:18:04 - Info bptm (pid=12555) Waiting for mount of media id M01769 (copy 1) on server elapp3.
08 Jan 15 17:18:04 - started process bptm (pid=12555)
08 Jan 15 17:18:04 - mounting M01769
08 Jan 15 17:18:05 - Info bptm (pid=12555) INF - Waiting for mount of media id M01769 on server elapp3 for reading.
08 Jan 15 17:18:33 - mounted M01769; mount time: 0:00:29
08 Jan 15 17:18:33 - Info bptm (pid=12555) M01769
08 Jan 15 17:18:34 - Info bptm (pid=12555) INF - Waiting for positioning of media id M01769 on server elapp3 for reading.
08 Jan 15 17:18:34 - positioning M01769 to file 1
08 Jan 15 17:18:34 - positioned M01769; position time: 0:00:00
08 Jan 15 17:19:35 - begin reading
08 Jan 15 17:21:31 - restored from image elapp3_1419139530; restore time: 0:11:18
08 Jan 15 17:21:31 - restoring from image elapp3_1419212034
08 Jan 15 17:21:35 - requesting resource M01769
08 Jan 15 17:21:35 - Waiting for scan drive stop IBMULTRIUM4-TD04, Media server: elapp3
08 Jan 15 17:21:35 - granted resource  M01769
08 Jan 15 17:21:35 - granted resource  IBMULTRIUM4-TD04
08 Jan 15 19:20:25 - Error bpbrm (pid=12501) socket read failed: errno = 52 - Stream ioctl timeout
08 Jan 15 19:20:27 - Error bptm (pid=12555) media manager terminated by parent process
08 Jan 15 19:20:58 - Info tar (pid=12554) done. status: 13: file read failed
08 Jan 15 19:20:58 - Error bpbrm (pid=12501) client restore EXIT STATUS 13: file read failed
08 Jan 15 19:21:00 - Info bpbrm (pid=18870) elapp3 is the host to restore to
08 Jan 15 19:21:00 - Info bpbrm (pid=18870) reading file list from client
08 Jan 15 19:21:00 - Info bpbrm (pid=18870) connecting to bprd to get file list
08 Jan 15 19:21:00 - connecting
08 Jan 15 19:21:00 - Info bpbrm (pid=18870) starting bptm
08 Jan 15 19:21:00 - Info tar (pid=18917) Restore started
08 Jan 15 19:21:00 - connected; connect time: 0:00:00
08 Jan 15 19:21:00 - Info bpbrm (pid=18870) bptm pid: 18920
08 Jan 15 19:21:01 - Info bptm (pid=18920) start
08 Jan 15 19:21:01 - started process bptm (pid=18920)
08 Jan 15 19:21:02 - Info bpdm (pid=18920) reading backup image
08 Jan 15 19:21:02 - Info bptm (pid=18920) using 64 data buffers
08 Jan 15 19:21:04 - Info bptm (pid=18920) Waiting for mount of media id M01776 (copy 1) on server elapp3.
08 Jan 15 19:21:04 - started process bptm (pid=18920)
08 Jan 15 19:21:04 - mounting M01776
08 Jan 15 19:21:04 - Info bptm (pid=18920) INF - Waiting for mount of media id M01776 on server elapp3 for reading.
08 Jan 15 19:21:37 - mounted M01776; mount time: 0:00:33
08 Jan 15 19:21:37 - Info bptm (pid=18920) M01776
08 Jan 15 19:21:38 - Info bptm (pid=18920) INF - Waiting for positioning of media id M01776 on server elapp3 for reading.
08 Jan 15 19:21:38 - positioning M01776 to file 1
08 Jan 15 19:21:38 - positioned M01776; position time: 0:00:00
08 Jan 15 19:22:31 - begin reading
08 Jan 15 19:24:30 - restored from image elapp3_1419212034; restore time: 2:02:59
08 Jan 15 19:24:30 - restoring from image elapp3_1419470368
08 Jan 15 19:24:34 - requesting resource M01776
08 Jan 15 19:24:35 - Waiting for scan drive stop IBMULTRIUM4-TD01, Media server: elapp3
08 Jan 15 19:24:36 - granted resource  M01776
08 Jan 15 19:24:36 - granted resource  IBMULTRIUM4-TD01
08 Jan 15 19:35:37 - Info bptm (pid=18920) waited for empty buffer 2014 times, delayed 19889 times
08 Jan 15 19:35:37 - end reading; read time: 0:13:06
08 Jan 15 19:35:37 - Info tar (pid=18917) done. status: 0
08 Jan 15 19:35:37 - Info bptm (pid=18920) completed reading backup image
08 Jan 15 19:35:37 - Info bptm (pid=18920) EXITING with status 0 <----------
08 Jan 15 19:35:37 - Info tar (pid=18917) done. status: 0: the requested operation was successfully completed
08 Jan 15 19:39:10 - restored from image elapp3_1419470368; restore time: 0:14:40
08 Jan 15 19:39:10 - Warning bprd (pid=24837) Restore must be resumed prior to first image expiration on INFINITY      
08 Jan 15 19:39:11 - end Restore; elapsed time 2:43:51
the requested operation was partially successful  (1)

 

 

1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Level 6
Partner    VIP    Accredited Certified

We have for some reason missed your post...

We see a 2-hour gap here:

08 Jan 15 17:21:35 - granted resource  IBMULTRIUM4-TD04
08 Jan 15 19:20:25 - Error bpbrm (pid=12501) socket read failed: errno = 52 - Stream ioctl timeout

If you are still having issues with large file restores, have a look at firewall timeouts and KeepAlive settings on client and media server.

Create all of the following logs before you attempt another restore:

On master: bprd (restart NBU after creating the folder)

On media server: bptm and bpbrm

On client: bpcd and tar

View solution in original post

2 REPLIES 2

cruisen
Level 6
Partner Accredited

Hello, 

I did not really find useful information on the connect forum than this, http://www.symantec.com/connect/forums/could-not-restore-huge-data-hpux-1131-ia64-netbackup-656

because you mention to have a HP-UX system I would give it a try.

best regards, 

cruisen

 

 

Marianne
Level 6
Partner    VIP    Accredited Certified

We have for some reason missed your post...

We see a 2-hour gap here:

08 Jan 15 17:21:35 - granted resource  IBMULTRIUM4-TD04
08 Jan 15 19:20:25 - Error bpbrm (pid=12501) socket read failed: errno = 52 - Stream ioctl timeout

If you are still having issues with large file restores, have a look at firewall timeouts and KeepAlive settings on client and media server.

Create all of the following logs before you attempt another restore:

On master: bprd (restart NBU after creating the folder)

On media server: bptm and bpbrm

On client: bpcd and tar