cancel
Showing results for 
Search instead for 
Did you mean: 

Restoration failing with status 5

dinesh_new
Level 3
Hi,

While restoring data , we are getting error : Cannot write data to socket, Broken pipe. Size of data to be restored is around 225 Gb and after restoring around 150 Gb data sucesfully, restoration is failing with status 5. We are using Netbackup 5.1 MP4. Master server , media server & client on which data is being restored all are Solaris servers. This is  very crucial restore for us. Please find logs:


Restore started 09/07/2009 06:46:15 PM

18:46:24 (2388884.xxx) Restore job id 2388884 will require 1 image.
18:46:24 (2388884.xxx) Media id D05174 is needed for the restore.

18:46:31 (2388884.001) Restoring from image created Wed 01 Jul 2009 08:59:38 BST
18:46:34 (2388884.001) INF - Waiting for mount of media id D05174 on server svaabackup02 for reading.
18:47:10 (2388884.001) INF - Waiting for positioning of media id D05174 on server svaabackup02 for reading.
18:49:01 (2388884.001) INF - Beginning restore from server svaabackup02 to client svaasun2-da-bkp.
18:49:03 (2388884.001) /databases/PROSML/data/PROSML_DAT_2009_ILC_01.dbf
18:52:07 (2388884.001) (2388884.001) INF - TAR EXITING WITH STATUS = 0
18:52:07 (2388884.001) (2388884.001) INF - TAR RESTORED 1 OF 1 FILES SUCCESSFULLY
18:52:07 (2388884.001) (2388884.001) INF - TAR KEPT 0 EXISTING FILES
18:52:07 (2388884.001) (2388884.001) INF - TAR PARTIALLY RESTORED 0 FILES

18:52:08 (2388884.001) The following files/folders were not restored:
18:52:08 (2388884.001) UTF - /databases/PROSML/data/PROSML_DAT_2009_ILC_01.dbf
18:52:09 (2388884.001) Status of restore from image created Wed Jul 01 08:59:38 2009 = socket write failed

18:52:12 (2388884.xxx) INF - Status = the restore failed to recover the requested files.

Please advise
11 REPLIES 11

Stumpr2
Level 6
Are you perhaps going through a firewall that is generating a timeout?

J_H_Is_gone
Level 6
Just checking do you have space for the restored file?

Radhakrishnan
Level 4
Employee Accredited Certified
Could you please create a tar directory netbackup logs. See any tar errors reported.  Also check the network connectivity. 

MariusD
Level 6
Hi there,

I have same problem like dinesh_new and my log it's

08.07.2009 11:06:12 - begin Restore
08.07.2009 11:06:46 - 1 images required
08.07.2009 11:06:46 - media U427L4 required
08.07.2009 11:06:46 - media U428L4 required
08.07.2009 11:06:46 - media U429L4 required
08.07.2009 11:06:46 - media U430L4 required
08.07.2009 11:06:46 - media U431L4 required
08.07.2009 11:06:46 - media U432L4 required
08.07.2009 11:06:46 - media U433L4 required
08.07.2009 11:06:46 - media U434L4 required
08.07.2009 11:06:46 - media U435L4 required
08.07.2009 11:06:46 - media U436L4 required
08.07.2009 11:06:46 - media U437L4 required
08.07.2009 11:06:46 - media U438L4 required
08.07.2009 11:06:46 - media U439L4 required
08.07.2009 11:06:46 - media U425L4 required
08.07.2009 11:06:46 - media U426L4 required
08.07.2009 11:06:46 - media 4764L4 required
08.07.2009 11:06:46 - media U440L4 required
08.07.2009 11:07:21 - restoring image kowi2_1244114683
08.07.2009 11:07:22 - requesting resource U429L4
08.07.2009 11:07:22 - granted resource U429L4
08.07.2009 11:07:22 - granted resource HP.ULTRIUM4-SCSI.001
08.07.2009 11:07:23 - connecting
08.07.2009 11:07:23 - Warning bpbrm(pid=6588) expected start message from kowi2; read: Unrecognized -J string priority=8000
08.07.2009 11:07:23 - connected; connect time: 00:00:00
08.07.2009 11:07:24 - mounted
08.07.2009 11:07:25 - positioning U429L4 to file 3
08.07.2009 11:08:08 - positioned U429L4; position time: 00:00:43
08.07.2009 11:08:08 - begin reading
08.07.2009 15:36:43 - positioning U429L4 to file 4
08.07.2009 15:36:43 - positioned U429L4; position time: 00:00:00
08.07.2009 23:09:56 - positioning U429L4 to file 5
08.07.2009 23:09:56 - positioned U429L4; position time: 00:00:00
08.07.2009 23:37:08 - current media U429L4 complete, requesting next resource HP.ULTRIUM4-SCSI.001:U430L4
08.07.2009 23:37:08 - awaiting resource HP.ULTRIUM4-SCSI.001:U430L4 Reason: Drives are in use, Media Server: ddcw1-m7002,
Robot Number: 0, Robot Type: TLD, Media ID: N/A, Drive Name: N/A,
Volume Pool: N/A, Storage Unit: N/A, Drive Scan Host: N/A

08.07.2009 23:38:15 - granted resource U430L4
08.07.2009 23:38:15 - granted resource HP.ULTRIUM4-SCSI.001
08.07.2009 23:38:16 - started process bptm (7208)
08.07.2009 23:38:16 - mounting U430L4
08.07.2009 23:39:24 - mounted; mount time: 00:01:08
08.07.2009 23:39:24 - positioning U430L4 to file 1
08.07.2009 23:39:24 - positioned U430L4; position time: 00:00:00
09.07.2009 01:30:37 - positioning U430L4 to file 2
09.07.2009 01:30:37 - positioned U430L4; position time: 00:00:00
09.07.2009 02:06:49 - Error bptm(pid=6220) The following files/folders were not restored:
09.07.2009 02:06:49 - Error bptm(pid=6220) UTF - /DATEN2/_Public/''Filme Deutsch Neu/NVA 720p-HDL.mkv
09.07.2009 02:06:49 - Error bptm(pid=6220) UTF - /DATEN2/_Public/''Filme Deutsch Neu/Natural Born Killers-iwok.m2ts
09.07.2009 02:06:49 - Error bptm(pid=6220) UTF - /DATEN2/_Public/''Filme Deutsch Neu/No Country For Old Men - GER ENG - AC3-iwok.m2ts
09.07.2009 02:06:49 - Error bptm(pid=6220) UTF - /DATEN2/_Public/''Filme Deutsch Neu/No Country For Old Men - GER ENG - AC3-iwok.srt
09.07.2009 02:06:49 - Error bptm(pid=6220) UTF - /DATEN2/_Public/''Filme Deutsch Neu/OldBoy-iwok.m2ts
09.07.2009 02:06:50 - Error bptm(pid=6220) UTF - /DATEN2/_Public/''Filme Deutsch Neu/Oxford Murders 720p DTS-SoW.mkv
09.07.2009 02:06:50 - Error bptm(pid=6220) UTF - /DATEN2/_Public/''Filme Deutsch Neu/P2 - Schreie im Parkhaus-iwok.m2ts
09.07.2009 02:06:50 - Error bptm(pid=6220) UTF - /DATEN2/_Public/''Filme Deutsch Neu/Pathology - GER ENG - DTS-MA-iwok.m2ts
09.07.2009 02:06:50 - Error bptm(pid=6220) UTF - /DATEN2/_Public/''Filme Deutsch Neu/Pathology - GER ENG - DTS-MA-iwok.srt
09.07.2009 02:06:50 - Error bptm(pid=6220) UTF - /DATEN2/_Public/''Filme Deutsch Neu/Patton-iwok.m2ts
09.07.2009 02:06:50 - Error bptm(pid=6220) more than 10 files were not restored, remaining ones are shown in the progress log.
09.07.2009 02:06:57 - restored image kowi2_1244114683 - (tar received an invalid archive(183)); restore time 14:59:36
09.07.2009 02:06:57 - end Restore; elapsed time: 15:00:45
the restore failed to recover the requested files(5)


What can be? I have a tar directory created and i have the restore job restarted ...end now I wait until come next error code :)
My restore size  is around 12 TB and hat the error after restoring around 1,4 TB.
Now I expect the next interruption. 


Regards,
Marius Demeter


dinesh_new
Level 3
Hi Marius,

I got the cause of the problem. Actually, the backup from which data was restored was done with Staus 1 i.e partially sucesful. Restoration was stucking at those files which were partailly backed up. After excluding those files during restore..restoration was sucesfull but at the cost of those files... :(

Anton_Panyushki
Level 6
Certified
I wonder how this issue could be resolved if they don't have a log for that backups job?
I suppose either bpflist or bpverify might help.

MariusD
Level 6
:)) ok, a exclude those files and restart the restore but come same error but now from another files.

nbjbets
Level 3
Hi Marius,

Can you clarify how the backups were taken for the files being restored? Also are you trying to restore the files to the original location or to an alternate location?

Have a look at this

ftp://exftpp.symantec.com/pub/support/products/NetBackup_Enterprise_Server/278567.pdf



MariusD
Level 6
How I have take the backu?? 

Normal. I have the linux client in one policy "standard" added and the "all local drives" backing up. Backup was completed successfully.

Now I look on this pdf,  probably I find something.


Regards,
Marius Demeter

MariusD
Level 6
I have also restore the files to the original location.

MariusD
Level 6
Hi all,

I have find the problem.

As per the technote: http://support.veritas.com/docs/297222
This is a known bug in Netbackup 6.5 client. And it has been resolved in Netbackup 6.5.2. Since the latest version of Netbackup is Netbackup 6.5.4, I have the last version updated and now the restore work fine.

This can be a solution when "restoration failing with status 5".


Regards,
Marius Demeter