Restore is failing with misplaced tape error

[Chidananda91]

Hi All,

 Its sounds strange, I am trying to restore data from same media on which backup happened a month ago, Nothing has changed since but getting misplaced media error tried differeent date tapes on different drives but no luck.

One thing happened is drives were unable to mount media as bptm was hung we resolved by taking service recycle and reboot of the server.

Please suggest solution as it is critical restore pending.

Here is the job detail

02/07/2016 05:54:50 - begin Restore

02/07/2016 05:54:51 - number of images required: 1

02/07/2016 05:54:51 - media needed: 0083L5

02/07/2016 05:54:51 - media needed: 0085L5

02/07/2016 05:54:52 - restoring from image enkwfpsprd01_1452920879

02/07/2016 05:54:52 - Info bpbrm (pid=2640) enkwfpsprd01 is the host to restore to

02/07/2016 05:54:52 - Info bpbrm (pid=2640) telling media manager to start restore on client

02/07/2016 05:54:52 - Info bpbrm (pid=6996) enkwfpsprd01 is the host to restore to

02/07/2016 05:54:52 - connecting

02/07/2016 05:54:52 - Info bpbrm (pid=6996) start tar32 on client

02/07/2016 05:54:54 - requesting resource 0085L5

02/07/2016 05:54:54 - awaiting resource 0085L5. Waiting for resources. 
          Reason: Drives are in use, Media server: enkwfpsprd01, 
          Robot Type(Number): TLD(0), Media ID: N/A, Drive Name: N/A, 
          Volume Pool: N/A, Storage Unit: N/A, Drive Scan Host: N/A, 
          Disk Pool: N/A, Disk Volume: N/A 

02/07/2016 05:54:56 - Info tar32 (pid=6892) Restore started.

02/07/2016 05:54:56 - connected; connect time: 0:00:00

02/07/2016 05:59:36 - Info bptm (pid=8744) Waiting for mount of media id 0085L5 (copy 1) on server enkwfpsprd01.

02/07/2016 05:59:36 - started process bptm (pid=8744)

02/07/2016 05:59:36 - mounting 0085L5

02/07/2016 05:59:36 - Info bptm (pid=8744) INF - Waiting for mount of media id 0085L5 on server enkwfpsprd01 for reading.

02/07/2016 05:59:36 - granted resource  0085L5

02/07/2016 05:59:36 - granted resource  IBM.ULT3580-HH5.000

02/07/2016 05:59:38 - Error bptm (pid=8744) error requesting media, TpErrno = Robot operation failed

02/07/2016 05:59:39 - current media 0085L5 complete, requesting next media IBM.ULT3580-HH5.000:NetBackup:0085L5

02/07/2016 05:59:42 - awaiting resource IBM.ULT3580-HH5.000:NetBackup:0085L5. 
          A pending request has been generated for this resource request. 
          Operator action may be required. Pending Action: Misplaced tape, 
          Media ID: 0085L5, Barcode: 000085L5, Density: hcart3, Access Mode: Read, 
          Action Drive Name: N/A, Action Media Server: enkwfpsprd01, Robot Type(Number): 8(0), 
          Volume Group: 000_00000_TLD, Action Acs: N/A, Action Lsm: N/A

[Marianne]

So, where exactly is tape 000085L5? Have you loaded it manually in a tape drive? It must simply be in robot 0 in the slot where NBU expects it to be. NBU will mount the tape in the drive that it selects for the restore. If the tape has been moved manually, please put it back in its slot and then run an Inventory just to be sure that NBU and the robot are 100% in sync about the tape location.

[nbutech]

There is a pending request generated

Just allow the pend request from device monitor or run command vmoprcmd

https://www.veritas.com/support/en_US/article.000043713

A pending request has been generated for this resource request. 
          Operator action may be required. Pending Action: Misplaced tape, 

[nbutech · Accepted solution]

You can also run mcontent report and verify if the media is getting mounted correctly.. ?

[Marianne]

Just wondering if tape and drive is in the same 'ill' library of last week's post? https://www.veritas.com/community/forums/unable-inventory-robot-inventory-failed-unable-initialize-robot-204-0

[Chidananda91]

Hi Guys,

Sorry for the delay. This issue has been resolved now the tape was corrupt

[Marianne]

Corrupt tape will give 'media read error'. Not 'misplaced' error.

[AlBahr]

As Marianne said, it is very true, because today we have experienced same issue having exact error as mentioned in this post, basically seems like Netbackup issue misplaced error may be due to restore job was started, and by the time restore job get drive, media were ejected and that specific slot were replaced with another media, and no library inventory has done, so when Netbackup goes and read that slot to mount the media, it could not find the media it expected, so then it issue misplaced error.

Solution : Inventory the library or placed the media back in to same slot

On the robotic host, under Windows system logs, you may see such errors description in detailed