cancel
Showing results for 
Search instead for 
Did you mean: 

Restorations failing with error 85

Sathisp83
Level 3
Certified

Backups are running fine but restorations are failing with 85. I dont think media issue, because almost all the restorations are failing. Please advice,

1/26/2013 03:58:35 - Info bptm (pid=20345) Waiting for mount of media id NO5751 (copy 1) on server orlsxbk01.
11/26/2013 03:58:35 - started process bptm (pid=20345)
11/26/2013 03:58:35 - mounting NO5751
11/26/2013 03:58:35 - Info bptm (pid=20345) INF - Waiting for mount of media id NO5751 on server orlsxbk01 for reading.
11/26/2013 03:58:35 - granted resource  NO5751
11/26/2013 03:58:35 - granted resource  HP.ULTRIUM4-SCSI.006
11/26/2013 03:59:35 - mounted NO5751; mount time: 0:01:00
11/26/2013 03:59:35 - Info bptm (pid=20345) NO5751
11/26/2013 03:59:35 - Info bptm (pid=20345) INF - Waiting for positioning of media id NO5751 on server orlsxbk01 for reading.
11/26/2013 03:59:35 - positioning NO5751 to file 163
11/26/2013 04:03:08 - positioned NO5751; position time: 0:03:33
11/26/2013 04:03:08 - begin reading
11/26/2013 04:03:08 - Error bptm (pid=20345) cannot read image from media id NO5751, drive index 9, Not enough space
11/26/2013 04:03:08 - Info bptm (pid=20345) EXITING with status 85 <----------
11/26/2013 04:03:24 - Error bpbrm (pid=20332) from client orlsxbk01: The following files/folders were not restored:
11/26/2013 04:03:24 - Error bpbrm (pid=20332) from client orlsxbk01: UTF - /emc/reale/bi_01/orlsxdp01.chk
11/26/2013 04:03:24 - Info tar (pid=20344) done. status: 0
11/26/2013 04:03:24 - Info tar (pid=20344) done. status: 85: media read error
11/26/2013 04:03:24 - Error bpbrm (pid=20332) client restore EXIT STATUS 85: media read error
11/26/2013 04:03:24 - end Restore; elapsed time 0:05:12

4 REPLIES 4

mph999
Level 6
Employee Accredited

This perhaps ...

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

Sathisp83
Level 3
Certified

backups which ran befor are MSEO enabled, but currently it's not. Can someone please confirm how to enable the MSEO

mph999
Level 6
Employee Accredited

What do you mean it is not enabled ?

Is this the same system, or another separate system that is NOT the system that made the backup.

Have you got the mseo keys ...

IS mseo running ?

 

mph999
Level 6
Employee Accredited

If the version of NBU is 7.1 or above, there is a problem with the asynchronous tape markls that were introduced at NBU 7.1

In a nutshell, they are not compatible with MSEO.

They can be turned off with the file :

/usr/openv/netbackup/db/config/DISABLE_IMMEDIATE_WEOF
 
Any MSEO backups taken at 7.1 or above, and BEFORE the file above was created (it is not there by default) will not restore.

If the file above WAS created at the time of the backups, they should be unaffected by the issue.