Incorrect media found in drive

[imashu]

*** Moved to new discussion from https://www-secure.symantec.com/connect/forums/media-server-ip-has-changed-and-not-working ***

Hi,

After this IP was chnaged and library was shifted from 1 place to another. Duplications and backup's are failing with the below error;

07/06/2013 10:41:47 - Info bptm(pid=2244) media id A00026 mounted on drive index 0, drivepath {3,7,0,0}, drivename HP.ULTRIUM4-SCSI.000, copy 2
07/06/2013 10:41:54 - Error bptm(pid=2244) incorrect media found in drive index 0, expected A00026, found F569L4, FREEZING A00026
07/06/2013 10:41:54 - current media A00026 complete, requesting next resource Any
07/06/2013 10:42:41 - Info bptm(pid=2244) EXITING with status 96 <----------       
07/06/2013 10:42:41 - Error nbjm(pid=5296) NBU status: 96, EMM status: No media is available   
 

After running the inventory for the 1st time the tape labels are showing different labels as we had previously.

Tried re-running the inventory and relablleing the media by un-ticking the "Verify media label before performing operation" box. but that is also failing,

I am not sure what has changed which is causing the media's to show up different labels.

Please help!!

Windows 2008
NetBackup 7.1.0.3

[Nicolai]

If labels are showing up different you need to configure a bar code rules in Netbackup. It's quite important you fix this ASAP as you may overwrite tape with active backup on them.

See:

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

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

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

Also verify that the mapping device driver and physical drives matches. If device driver point to drive 2 but it actual drive 1 in the robot everything will stop working. In doubt use storage configuration wizard in Netbackup.

[Marianne]

library was shifted from 1 place to another.
 

Please share steps that were taken?
Were all tapes removed prior to the move? Robot arm secured for the move?
How was robot tested for proper operation after power up?

Please share all steps that were taken from NBU point of view?
Hopefully devices were removed and re-added as device mapping would have changed?

Is A00026 an actual barcode or unlabelled tape?
Or something wrong with the barcode reader?

Please use robtest and show us output of 
s s 

[imashu]

Hello,

Thanks Marianne!!

I have just asked the steps from the touch labor team who shifted the library from one place to another. Will let you know shortly the steps taken.

After the library was connected the robot and drive was not visible at OS so we rebooted the library and server and then reconfigured the storage devices. After this library and drives were visible but it was showing different barcode of the availble media's when we ran the inventory of the available media's.

A00026 is not the actual barcode of this media.

Please find the output of S S command in robtest;

Enter choice: 1
1

Robot selected: TLD(1)   robotic path = {3,7,0,1}

Invoking robotic test utility:
D:\Program Files\Veritas\Volmgr\bin\tldtest.exe -rn 1 -r {3,7,0,1}

Opening {3,7,0,1}
MODE_SENSE complete
Enter tld commands (? returns help information)
s s
slot 1 (addr 32) contains Cartridge = yes
Source address = 32
slot 2 (addr 33) contains Cartridge = yes
slot 3 (addr 34) contains Cartridge = yes
slot 4 (addr 35) contains Cartridge = yes
slot 5 (addr 36) contains Cartridge = yes
Source address = 36
slot 6 (addr 37) contains Cartridge = yes
slot 7 (addr 38) contains Cartridge = yes
slot 8 (addr 39) contains Cartridge = yes
slot 9 (addr 40) contains Cartridge = yes
slot 10 (addr 41) contains Cartridge = yes
slot 11 (addr 42) contains Cartridge = yes
slot 12 (addr 43) contains Cartridge = yes
slot 13 (addr 44) contains Cartridge = yes
slot 14 (addr 45) contains Cartridge = yes
slot 15 (addr 46) contains Cartridge = yes
slot 16 (addr 47) contains Cartridge = yes
slot 17 (addr 48) contains Cartridge = yes
slot 18 (addr 49) contains Cartridge = yes
slot 19 (addr 50) contains Cartridge = yes
<< Press return to continue, or q and return to stop >>

slot 20 (addr 51) contains Cartridge = yes
slot 21 (addr 52) contains Cartridge = yes
slot 22 (addr 53) contains Cartridge = yes
slot 23 (addr 54) contains Cartridge = yes
slot 24 (addr 55) contains Cartridge = yes
slot 25 (addr 56) contains Cartridge = yes
slot 26 (addr 57) contains Cartridge = yes
slot 27 (addr 58) contains Cartridge = yes
slot 28 (addr 59) contains Cartridge = yes
slot 29 (addr 60) contains Cartridge = yes
READ_ELEMENT_STATUS complete

Nothing was changed in terms of barcode at netbackup end. But still not sure what was the issue.

Also, can you please suggest what is the correct procedure that should have been followed while moving the library from one place to another.

[mph999]

Something is wrong on the library.

Look at my s s output from robtest

Opening /dev/sg2

MODE_SENSE complete

Enter tld commands (? returns help information)

s s

slot 1 (addr 1024) contains Cartridge = yes

Barcode = E01001L4

slot 2 (addr 1025) contains Cartridge = yes

Barcode = E01002L4

Look at the same from your library :

s s
slot 1 (addr 32) contains Cartridge = yes
Source address = 32
slot 2 (addr 33) contains Cartridge = yes
slot 3 (addr 34) contains Cartridge = yes
slot 4 (addr 35) contains Cartridge = yes

See how yours is not showing the barcode info ...

So it looks like your library has somehow forgotten it has a barcode reader.

Martin

[Marianne · Accepted solution]

Seems the robot arm was not secured during the move and the camera got damaged.

Log a call with your hardware vendor and DO NOT use the tapes with these auto-generated media-id's.

In the meantime, move all the A.... tapes to non-robotic (just logically, not eject), then do a physical inventory from cmd using vmphinv. 
This will take a long time as each tape has to be mounted, internal label read in order to update inventory.

See NetBackup Commands Reference Guide  http://www.symantec.com/docs/DOC3684 for details.

[imashu]

Thanks Martin,

But how can we correct it. Does it something to do with Netbackup or Physical library.

[mph999]

Physical library.

What you see in robtest when you run s s is sent from the library.  robtest is simply displaying what it is told.

The h/ware vendor may well try to blame NBU, if this happens you need to tell them they are wrong.

Quite simply, there is absolutley nothing that can be done in NBU to fix this.

Martin

[Marianne]

Please see my post above.