Error bptm(pid=1500) incorrect media found in drive index 0

[stemen055]

What the following error means :

Error bptm(pid=1500) incorrect media found in drive index 0, expected A00000, found A00025, FREEZING A00000

Any clues to correct this issue would be much appreciated.

Thanks

[Andy_Welburn]

First two I can think of simply put:

1) Incorrect drive config has resulted in incorrect labelling of tapes e.g. tapes loaded in 2 drives A & B - incorrectly configured drives could result in the tape in drive A getting a software label that should really be applied to that in drive B.

2) Someone has swapped a few tapes around in the library (either manually or via robtest) and hasn't run an Inventory in NetBackup.

***EDIT***
From the following Tech Note (in relation to point 1 above):
"...
The easiest way to see if the OS and NetBackup see the drives in the same way is to move a tape into a drive (for example, drive 1). Then, look into NetBackup's device monitor and see what drive number NetBackup sees the tape in. If other than drive 1, change the Robot Drive Number of the drive in the NetBackup Media and Device Manager configuration to match what robotic drive number robtest shows the tape in.
..."

Robtest commands that can be used to test the SCSI functionality of a robot

[RollTheBones]

Is it possible tapes got moved around outside of NetBackup?  What kind of library is it?

You can compare what robtest tells you with what netbackup thinks is there, if they do not agree then there is your issue.

[J_H_Is_gone]

This is usually because you have a bad configuration of your tape drives.

say library drive 2 is configured as being rmt1 on your server

say library drive 4 is configured as being rmt3 on your server.

you start a couple of jobs and NB loads tapes in both drive 2 and drive 4

however you have the rmt's switched.

so tape A00025 is loaded into drive 2, and tape A0000 in drive 4
your server goes to backup to rmt3 and finds A00025  ?????

this is because drive 2 is actually rmt3 on your server, that is why it found the wrong tape.

A way to check to look at serial numbers of the drives, and of the rmt's configured on your server.
See if by chance they are not matching, which means you have a bad configuration between your library and you server.  Fix it so that drive 2 is rmt3 and drive 4 is rmt1 and it would work.

[Nicolai]

Phone calls, meanwhile 3 post get submitted.

[Nicolai]

Some ideas right out of my mind:

• Media being moved manual in the robot (run a inventory of the robot)
• Drives location being incorrectly configured in Netbackup (let's say the drive is in bay 1 in the robot, but configured as drive bay 2). Then netbackup will mount the tapes in the wrong drive.

[Andy_Welburn]

[stemen055]

20/05/2010 11:02:14 AM - granted resource xxxx-dlt2-robot-tld-0
20/05/2010 11:02:15 AM - estimated 0 kbytes needed
20/05/2010 11:02:15 AM - started process bpbrm (5516)
20/05/2010 11:02:19 AM - connecting
20/05/2010 11:02:21 AM - connected; connect time: 00:00:02
20/05/2010 11:02:24 AM - mounting A00002
20/05/2010 11:03:00 AM - mounted; mount time: 00:00:36
20/05/2010 11:03:06 AM - Error bptm(pid=4700) incorrect media found in drive index 0, expected A00002, found A00101, FREEZING A00002
20/05/2010 11:03:06 AM - current media A00002 complete, requesting next resource Any
20/05/2010 11:03:43 AM - granted resource A00003
20/05/2010 11:03:43 AM - granted resource COMPAQ.SDLT320.000
20/05/2010 11:03:43 AM - granted resource xxxx-dlt2-robot-tld-0
20/05/2010 11:03:44 AM - mounting A00003
20/05/2010 11:18:19 AM - Error bptm(pid=4700) error requesting media, TpErrno = Robot operation failed    
20/05/2010 11:18:19 AM - Warning bptm(pid=4700) media id A00003 load operation reported an error    
20/05/2010 11:18:19 AM - current media A00003 complete, requesting next resource Any
20/05/2010 11:18:27 AM - Error bptm(pid=4700) NBJM returned an extended error status: drive(s) unavailable or down (830) 
 end writing
extended error

[J_H_Is_gone]

I would do a new inventory of the library with an update ( or do it with a compare) and see if anything is coming up wrong.

Like NB thinks a tape is in slot 25 but the library as a different tape in slot 25.

Also have you changed any barcodes?
If a tape had a barcode of A00003 and was written to so it got an ID of A00003, but then the barcode was changed to A000025.
So when NB/library loaded barcoded tape A00003, but the tape drive read the written id of A00025 it would say it found the wrong tape.

You can check this - if the tape is a scratch (no good images) by doing a label and ask it to YES verify the written id.  If the barcode and the written id are the same it will work, if they are different it will fail.