Not able to import LTO4 tape by using LTO5 drive.

[NBU_13]

Hi,

I need a help, I have 2 master servers, A and B,

Master server (MasterA) is V6.5 and using LTO4 tapes for backup, master server (MasterB) is V7.1 and using LTO5 tapes and drives, Now, I want to use LTO4 tapes in masterB with LTO5 drives, So I put LTO4 tapes in masterB and run Robot inventory, tapes are updated in masterB and I ran import to update catalog, I updated density type as HCART2 for LTO4, LTO5 tapes, drives and storage unit is also in HCART,  but tapes are not mounting, its giving error  as below :

Any one please help me to find solution for this issue.

Error :

8/17/2012 12:23:33 PM - begin Import

8/17/2012 12:23:34 PM - Info bptm(pid=7684) start           

8/17/2012 12:23:34 PM - started process bptm (7684)

8/17/2012 12:23:34 PM - Info bptm(pid=7684) Waiting for mount of media id 0073L2 (copy 1) on server nbk-svs.

8/17/2012 12:23:34 PM - started process bptm (7684)

8/17/2012 12:23:34 PM - mounting 0073L2

8/17/2012 12:23:34 PM - Info bptm(pid=7684) INF - Waiting for mount of media id 0073L2 on server nbk-svs for reading.

8/17/2012 12:23:34 PM - requesting resource 0073L2

8/17/2012 12:23:34 PM - granted resource 0073L2

8/17/2012 12:23:34 PM - granted resource HP.ULTRIUM5-SCSI.002

8/17/2012 12:23:38 PM - Error bptm(pid=7684) error requesting media, TpErrno = Robot operation failed    

8/17/2012 12:23:38 PM - current media 0073L2 complete, requesting next resource HP.ULTRIUM5-SCSI.002:LTO4tapes:0073L2

8/17/2012 12:23:41 PM - Info bptm(pid=7684) Waiting for mount of media id 0073L2 (copy 1) on server nbk-svs.

8/17/2012 12:23:41 PM - started process bptm (7684)

8/17/2012 12:23:41 PM - mounting 0073L2

8/17/2012 12:23:41 PM - Info bptm(pid=7684) INF - Waiting for mount of media id 0073L2 on server nbk-svs for reading.

8/17/2012 12:23:41 PM - granted resource 0073L2

8/17/2012 12:23:41 PM - granted resource HP.ULTRIUM5-SCSI.001

8/17/2012 12:23:45 PM - Error bptm(pid=7684) error requesting media, TpErrno = Robot operation failed    

8/17/2012 12:23:45 PM - current media 0073L2 complete, requesting next resource HP.ULTRIUM5-SCSI.001:LTO4tapes:0073L2

8/17/2012 12:23:48 PM - awaiting resource HP.ULTRIUM5-SCSI.001:LTO4tapes:0073L2 A pending request has been generated for this resource request.

  Operator action may be required. Pending Action: Tape is unmountable.,

  Media ID: 0073L2, Barcode: 000073L2, Density: hcart2, Access Mode: Read,

  Action Drive Name: N/A, Action Media Server: N/A, Robot Number: 0, Robot Type: TLD,

  Volume Group: 000_00000_TLD, Action Acs: N/A, Action Lsm: N/A

[Marianne · Accepted solution]

We have previously done this where internal and external media id's do not match:

vmadd -m 0070L2 -mt <media_type>  -b <new-barcode>  -p <pool_number>
This should add the media as standalone. Manually load the tape in a slot in the robot (e.g. robtest). 
Inventory the robot to update media id 0070L2 with the correct slot # in the robot.

ONE MORE thing - how sure are you that 0070L2 is an LTO4 tape?
Same way that the robot refuses to load L2 tape into LTO5 drive, L2 tape can only be loaded into LTO4 drive for restore, not for backup. Mount request for backup to L2 tape on LTO4 drive should have been rejected. 

[NBU_13]

Hi,

Iam sure about tape 0070L2 is an LTO4 tape, because I was used the same tape in LTO4 drive previously, Now I decommission that server and build new server with new netbackup version with LTO5 drive library, but no I want to use tape 0070L2, LTO4 tape in LTO5 tape library.

So, now I want to change barcode label 0070L2 in to 0070L4, put in to LTO5 tape library and run robot inventory and try for import the tape.

[Marianne]

This is why incorrect labels on tapes is never a good idea - even if barcode reader / robot does not check (as was apparently the case with old library). Using valid LTO4 tape with LTO2 label is a big headache in new robot....

What we need to determine is what the media id's were in your old environment - last 6 characters  or 1st 6 characters?

Last 6 means internal label is 0070L2  - perfectly fine to use my 'vmadd' suggestion above.

First 6 means internal label is ##0070 (see physical barcode for ## values).

Hopefully you won't need to restore lots of data from these L2 tapes - headache, headache, headache....

It might be easier to have a standalone LTO4 drive for these restores...

[mph999]

No, do not run a robot inventory.

This would create a 'new' mediaid - which will not match the mediaid on the tape.

You need to run a vmphyinv command, this will cause NBU to read the media id on the tape, and give the tape 'that' mediaid in NBU, which is exactly what you want.

Martin

[NBU_13]

Hi,

I put new barcode label with L4 in the tape and run inventry, its mounting now, but giving error code 176,

because in old server media id is 1st 6 digit, that is 000070, but in new server media id is last 6 digit, that is 0080L5

Anyone help me, its very urgent issue.

Thanks in Advanced.

[NBU_13]

now my need id is IFB380L4 and only medi id is 000070L2

can you please give physical inventory command with option

which i need execute.

[Mark_Solutions]

based on your first message:

vmphyinv -rn 0 -rh mediaservername -ml 0080L5

not esure what you mean in the second message ... what ever the media ID is shown as current put that at the end of the command to make it read that piece of media and update EMM with the media id found on the tape header

[sksujeet]

Nice learning here:)

I do see you already ran the inventory, do the below steps from GUI:

1) Write down the slot # & the tape number from the Inventory wizard.
2) Go to the media & right click it & delete the media.
3) Right click anywhere or any other media & select “New”

4) Update the following fields on the next window
a. Media Type – verify the tape type (hcart2)
b. Robot # - robot # the tape is inserted into
c. Media Id – Original NetBackup media id
d. First Slot # - Slot # the media got imported into.

4)OK & the deleted tape number will again be visible on the console.

5)vmphyinv –rn 0 – ml 0070L2

6)Initiate import

[Marianne]

Did you not believe us when we told you: 

No, do not run a robot inventory.   ?

If you ran vmadd command as per my suggestion above before inventory, all would have been fine.

The steps suggested by sazz should also work.

[mph999]

Or if you had run my vmphyinv command you would have been ok ...

vmphyinv -rn <robot name> -rh <robot control host> -slot_list <slot num containing tape> -ml <media label that is written on the tape>

All you need do is delete the tape, the run the command above with the 'variables' substituted in.

Martin

[Marianne]

Correct - Martin was first to suggest vmphinv.

Mark's process would possibly work as well: https://www-secure.symantec.com/connect/forums/not-able-import-lto4-tape-using-lto5-drive#comment-75...

[NBU_13]

Hi,

Thank you so much to all, I done it, issue resolved, I can able to read media and import has also completed.

once again, Thank you to all :)

[Marianne]

Please let us know which method you used, then mark the post that has helped you most as Solution.

[mph999]

Mark came up with the simple idea of changing the tapes barcode, so I think you should mark his post as the solution. , or if you disagree, please mark the post that you felt helped the most as the answer.

Many thanks,

martin

[NBU_13]

Hi,

I changed new barcode with L4 and added volume manually as below command:

C:\Program Files\Veritas\Volmgr\bin>vmadd -m 000070 -mt HCART2 -h masters -verbo
se -b AA0380L4 -rt TLD -rn 0 -rh masters -p 2 rc1 5

and then,

ran import phase 1 and phase 2