Backup Image FORCE_RESTORE option is failing for basic disk STU

[hariharan24]

Hi

I have a media server name XYZ which is having Basic Disk STU - /mount1

I had taken the backup through that Media server., & it was successful.

While restoring I tried to restore it via Master server ABC - but it is failing with 83 error code.,

04/18/2015 07:31:38 - Critical bptm (pid=12849) sts_get_lsu_prop_byname on LSU /mount1 failed: 2060013 no more entries
04/18/2015 07:31:38 - Critical bptm (pid=12849) Invalid storage device: /mount1 no more entries
04/18/2015 07:31:38 - Critical bptm (pid=12849) failure to open disk at path /mount1: plug-in reports error 2060013  
04/18/2015 07:31:38 - Info bptm (pid=12849) EXITING with status 83 <----------
04/18/2015 07:31:43 - Info tar (pid=12848) done. status: 83: media open error

Is it possible to add the master server entry in the Basic disk STU ?? ANy idea

Since when am restoring via backup taken media server then it is getting sucessful/.,

Any idea how to restore the basic disk images from alternate Master/Media Servers?

[GulzarShaikhAUS]

The restore should work without any issues in your case.

Can you please share bptm? It will be located on media server XYZ

[hariharan24]

Am Forcing the restore to happen via master using FORCE_RESTORE option in bp.conf file.,

Without Force restore option restore is working fine via media server but If i give for_restore option to happen the restore via master - then at that time restoration is failing with 83 error code.,

Also please note, the basic disk where the backup resides is mounted only in Media server.,

[hariharan24]

Can anyone share the basic disk limitations .,?? seems Medias server mount cant be accessed by master server - that is the reason it is giving 83 - Media Open error.,

[sdo · Accepted solution]

IMO the word limitation is perhaps a little bit unfair.  Truely shared disk is usually a feature of quite expensive (or very expensive) highly available storage arrays and complex storage presentation (multi-pathing) and complex clustering.

A basic disk storage unit can only be owned and managed by one media server.  Another NetBackup server cannot see the storage, and cannot access the storage, no matter whether it is a master or master/media or media - so there's no point trying to force_restore via another NetBackup server.

AFAIK there is no longer any 'shared disk'.  See this response from Nicolai:

https://www-secure.symantec.com/connect/forums/san-shared-storage-unit-disk-netbackup

.

Anyway, save a copy of this:

http://www.netpp.rs/pdf/implementacija_minimalnih_standarda/Symantec_NetBackup.pdf

...and have a look at the head-line features of the different target storage options.

.

Why do you think you need some kind of 'shared disk'?

If you are worried about single point of failure, as most sites are, then the apporach has always been to take multiple copies, using either backup in-line, or SLP managed duplication, or NetBackup Vault duplication or SLP managed NetBackup AIR replication.

[Marianne]

Have you presented the disk to the master server and mounted it on /mount1? Can you cd into /mount1 on the master server and see the backup images? There may be more steps needed if this does not work. Ensure that all of these log folders exist: On master : bprd (restart NBU after creating the folder ) On original media server and master: bpbrm, bptm, bpdm We will first of all need bprd log on the master. Depending on what we see in this log, we will know which log to look at next. Copy log to bprd.txt and upload as File attachment.