Restore is failing

[OracleDBA2]

Hi,

I am really in a bad situation now. We had a server with no space left on storage connected it.

So my manager wanted to move some archive files (and they were important) to netbackup and delete files on storage to free up space. 

After purchasing new storage we will restore it. I said ok. And it was 4 TB important files.

Now we purchased new storage after 1.5 years and when we Restore it is failing with error

1: (85) media read error 

The funny thing is, if i select the top folder it exits with error after resoring say 300 GB out of 1.5 TB. Then i go to each sub folder and restored sub folders some restored fine and some failing with error.

Then again i am going inside failed sub fiolders (here there 1000 folders) i tried to restore, some sucessfully restored and some not.

How can i know which files in subfolders can be resored. and please i need help on this to restore.

Detailed error is

11/16/2017 14:19:38 - begin Restore
11/16/2017 14:19:42 - restoring from image xyz-xc.someorg_1493111563
11/16/2017 14:19:42 - requesting resource @aaaak
11/16/2017 14:19:43 - Info bprd (pid=6012) Restoring from copy 1 of image created Tue Apr 25 12:19:47 2017
11/16/2017 14:19:43 - granted resource MediaID=@aaaak;DiskVolume=PureDiskVolume;DiskPool=dp_disk_symentbkp;Path=PureDiskVolume;StorageServer=symentbkp;MediaServer=symentbkp
11/16/2017 14:19:44 - Info bpbrm (pid=6037) xyz-xc.someorg is the host to restore to
11/16/2017 14:19:44 - Info bpbrm (pid=6037) reading file list from client
11/16/2017 14:19:45 - connecting
11/16/2017 14:19:45 - Info bpbrm (pid=6037) starting bptm
11/16/2017 14:19:51 - Info tar (pid=14920) Restore started
11/16/2017 14:19:51 - connected; connect time: 0:00:00
11/16/2017 14:19:51 - Info bpbrm (pid=6037) bptm pid: 6057
11/16/2017 14:19:51 - Info bptm (pid=6057) start
11/16/2017 14:19:51 - started process bptm (pid=6057)
11/16/2017 14:19:51 - Info bpdm (pid=6057) reading backup image
11/16/2017 14:19:51 - Info bptm (pid=6057) using 30 data buffers
11/16/2017 14:19:51 - Info bptm (pid=6057) spawning a child process
11/16/2017 14:19:51 - Info bptm (pid=6057) child pid: 6101
11/16/2017 14:19:55 - begin reading
11/16/2017 14:19:55 - Critical bptm (pid=6057) Storage Server Error: (Storage server: PureDisk:symentbkp) PdvfsRead: Failed to read from spoold (No such file or directory). Ensure storage server services are running and operational. V-454-19
11/16/2017 14:19:55 - Critical bptm (pid=6057) sts_read_image failed: error 2060018 file not found
11/16/2017 14:19:55 - Critical bptm (pid=6057) image read failed: error 2060018: file not found
11/16/2017 14:19:55 - Error bptm (pid=6057) cannot read image from disk, Invalid argument
11/16/2017 14:19:55 - Info bptm (pid=6057) EXITING with status 85 <----------
11/16/2017 14:19:55 - Error bptm (pid=6101) The following files/folders were not restored:
11/16/2017 14:19:55 - Error bptm (pid=6101) UTF - /K/Arc_01/Oct2012/SOMEFILE201210021738430000c29a373d2/
11/16/2017 14:19:55 - Error bptm (pid=6101) UTF - /K/Arc_01/Oct2012/SOMEFILE201210021738430000c29a373d2/CSD94FMX
11/16/2017 14:19:55 - Error bptm (pid=6101) UTF - /K/Arc_01/Oct2012/SOMEFILE201210021738430000c29a373d2/CSD94FNE
11/16/2017 14:19:55 - Error bptm (pid=6101) UTF - /K/Arc_01/Oct2012/SOMEFILE201210021738430000c29a373d2/Thumbs00.mul
11/16/2017 14:19:55 - Error bptm (pid=6101) UTF - /K/Arc_01/Oct2012/SOMEFILE201210031219540000c29a373d2/
11/16/2017 14:19:55 - Error bptm (pid=6101) UTF - /K/Arc_01/Oct2012/SOMEFILE201210031219540000c29a373d2/CSTS6S0O
11/16/2017 14:19:55 - Error bptm (pid=6101) UTF - /K/Arc_01/Oct2012/SOMEFILE201210031219540000c29a373d2/CSTS6S0T
11/16/2017 14:19:55 - Error bptm (pid=6101) UTF - /K/Arc_01/Oct2012/SOMEFILE201210031219540000c29a373d2/CSTS6S0X
11/16/2017 14:19:55 - Error bptm (pid=6101) UTF - /K/Arc_01/Oct2012/SOMEFILE201210031219540000c29a373d2/CSTS6S12
11/16/2017 14:19:55 - Error bptm (pid=6101) UTF - /K/Arc_01/Oct2012/SOMEFILE201210031219540000c29a373d2/CSTS6S17
11/16/2017 14:19:56 - Error bptm (pid=6101) more than 10 files were not restored, remaining ones are shown in the progress log.
11/16/2017 14:19:56 - Info symentbkp (pid=6057) StorageServer=PureDisk:symentbkp; Report=PDDO Stats for (symentbkp): read: 204 KB, CR received: 330 KB, CR received over FC: 0 KB, dedup: 0.0%
11/16/2017 14:19:56 - Info tar (pid=14920) done. status 0
11/16/2017 14:19:57 - Info tar (pid=14920) done. status: 85: media read error
11/16/2017 14:19:57 - Error bpbrm (pid=6037) client restore EXIT STATUS 85: media read error
11/16/2017 14:19:57 - restored from image xyz-xc.someorg_1493111563; restore time: 0:00:15
11/16/2017 14:19:57 - Warning bprd (pid=6012) Restore must be resumed prior to first image expiration on Fri 24 Apr 2020 12:19:47 PM zzz
11/16/2017 14:19:57 - end Restore; elapsed time 0:00:19
media read error (85)

[Marianne]

I agree. You are really in a bad situation.

It seems there is something wrong with the disk location (MSDP or old PureDisk?) where your backup was written:

 Critical bptm (pid=6057) Storage Server Error: (Storage server: PureDisk:symentbkp) PdvfsRead: Failed to read from spoold (No such file or directory). Ensure storage server services are running and operational. V-454-19

What is especially bad about your situation is that you are running a NetBackup version that is no longer supported, which means that you cannot log a Support call.
EOSL software is like a lapsed insurance policy.... Sorry.... 

I found 2 posts with similar errors for backup  - not sure if they will be of any use:

https://vox.veritas.com/t5/NetBackup/Backup-jobs-failed/m-p/746408

https://vox.veritas.com/t5/NetBackup/Media-Open-Error-83/td-p/747950

[Lowell_Palecek]

>How can i know which files in subfolders can be restored?

Can you script a test restore? You could use bplist with the -R option to get a file list, then script restores on branches to isolate which folders you can't get.

If your NetBackup version was supported when you made the backup, I would ask Support if they can help you.