Video Screencast Help

Error : Medium indentifier do not match

Created: 05 Feb 2007 • Updated: 21 May 2010 | 5 comments

Hi !

On Friday, last week, i put 4 new DLT S4 Tapes in the Quantum PX 502 library and
configure them to the correct volume-pool and so on.
At this morning (monday) on some sheduled backups i have statuscode 96.
I take a look at the non.succesfull backup and see the following in the statuswindow.
...
05.02.2007 08:50:00 - granted resource FEB701
05.02.2007 08:50:00 - granted resource Drive1
05.02.2007 08:50:00 - granted resource BigStore
05.02.2007 08:50:13 - started process bpbrm (2368)
05.02.2007 08:50:46 - mounting FEB701
05.02.2007 08:50:46 - connecting
05.02.2007 08:50:56 - connected; connect time: 00:00:10
05.02.2007 08:51:33 - Error bptm(pid=5804) FREEZING media id FEB701, Medium identifiers do not match
05.02.2007 08:51:33 - Warning bptm(pid=5804) media id FEB701 load operation reported an error
05.02.2007 08:51:33 - current media FEB701 complete, requesting next media Any
05.02.2007 08:52:23 - granted resource FEB703
05.02.2007 08:52:23 - granted resource Drive2
05.02.2007 08:52:23 - granted resource BigStore
05.02.2007 08:52:27 - mounting FEB703
05.02.2007 08:53:32 - current media FEB703 complete, requesting next media Any
05.02.2007 08:54:13 - granted resource FEB704
05.02.2007 08:54:13 - granted resource Drive1
05.02.2007 08:54:13 - granted resource BigStore
05.02.2007 08:54:14 - mounting FEB704
05.02.2007 08:55:08 - Error bptm(pid=5804) FREEZING media id FEB704, Medium identifiers do not match
05.02.2007 08:55:08 - Warning bptm(pid=5804) media id FEB704 load operation reported an error
05.02.2007 08:55:08 - current media FEB704 complete, requesting next media Any
05.02.2007 08:55:51 - Critical bpbrm(pid=4092) from client server123: FTL - tar file write error (10054)
05.02.2007 08:55:52 - end writing
unable to allocate new media for backup, storage unit has none available(96)
...

Two of the four tapes are set to frozen stat without writing, one tape is full but not frozen, and one tape ist written with ~140 GB and then frozen.

What does this message mean :
--> Medium identifiers do not match

The barcode-label are different to the media-id that are use from netbackup, but one tape is ok and the others not.
Barcodelabel S4FEB703
Media-ID FEB703

Greets
Holger

Comments 5 CommentsJump to latest comment

Chia Tan Beng's picture

Hi Hoger,

Netbackup reads the barcode label when you inject new tapes into library but would only attempt to writes the internal label onto tape when they're first loaded to drive for write (e.g. during a backup). So when the "new tapes" has no internal label exists (i.e. genuinely new), it write the ID of the barcode label onto the tape. If netbackup finds there's existing internal label, it check against it volume database and if it exist, netbackup freeze the media. This may explain the 2 tapes that were frozen before writing and another was not.. The last one that was wriiten and was frozen could likely due to media error, consider retiring it.

Do a bpimmedia -mediaid on the 2 frozen tapes to confirm there's no un-expire images. Do a vmdelete -m to remove the volume id from volume database if you've ensure that there's no relevant images. Perform a inventory of the robot to re-gain the "new" volume.

Dennis Strom's picture

Another thing to check is to make sure that both the tapes and the drives are of the same type
ie dtl(0)

Michael Sponsler's picture

I have a PX510 that is exhibiting similar behavior.

I have 6 drives in my PX510, how ever only 1 of the drives will actually write backups. All 6 drives will do a label / erase.

02/08/2007 10:41:33 - requesting resource csnbkp21-dlt-robot-tld-56
02/08/2007 10:41:33 - requesting resource csnbkp1.NBU_CLIENT.MAXJOBS.csnbkp21
02/08/2007 10:41:33 - requesting resource csnbkp1.NBU_POLICY.MAXJOBS.CSNBKP21-System-Backup
02/08/2007 10:41:35 - granted resource csnbkp1.NBU_CLIENT.MAXJOBS.csnbkp21
02/08/2007 10:41:35 - granted resource csnbkp1.NBU_POLICY.MAXJOBS.CSNBKP21-System-Backup
02/08/2007 10:41:35 - granted resource X0004
02/08/2007 10:41:35 - granted resource QUANTUM.SDLT600..csndb2a1003
02/08/2007 10:41:35 - granted resource csnbkp21-dlt-robot-tld-56
02/08/2007 10:41:37 - started process bpbrm (pid=28080)
02/08/2007 10:41:37 - connecting
02/08/2007 10:41:38 - connected; connect time: 0:00:00
02/08/2007 10:41:42 - mounting X0004
02/08/2007 10:44:10 - Error bptm (pid=28087) FREEZING media id X0004, Medium identifiers do not match
02/08/2007 10:44:10 - Warning bptm (pid=28087) media id X0004 load operation reported an error
02/08/2007 10:44:11 - current media X0004 complete, requesting next media Any
02/08/2007 10:46:22 - granted resource X0017
02/08/2007 10:46:22 - granted resource QUANTUM.SDLT600..csndb2a1003
02/08/2007 10:46:22 - granted resource csnbkp21-dlt-robot-tld-56
02/08/2007 10:46:24 - mounting X0017
02/08/2007 10:47:09 - Error bptm (pid=28087) error requesting media, TpErrno = Robot operation failed
02/08/2007 10:47:09 - Warning bptm (pid=28087) media id X0017 load operation reported an error
02/08/2007 10:47:10 - current media X0017 complete, requesting next media Any
02/08/2007 10:47:39 - granted resource X0017
02/08/2007 10:47:39 - granted resource QUANTUM.SDLT600..csndb2a1003
02/08/2007 10:47:39 - granted resource csnbkp21-dlt-robot-tld-56
02/08/2007 10:47:40 - mounting X0017
02/08/2007 10:47:47 - Error bptm (pid=28087) error requesting media, TpErrno = Robot operation failed
02/08/2007 10:47:48 - Warning bptm (pid=28087) media id X0017 load operation reported an error
02/08/2007 10:47:48 - current media X0017 complete, requesting next media Any
02/08/2007 10:48:11 - granted resource X0015
02/08/2007 10:48:11 - granted resource QUANTUM.SDLT600..csndb2a1003
02/08/2007 10:48:11 - granted resource csnbkp21-dlt-robot-tld-56
02/08/2007 10:48:13 - mounting X0015


I did see this in my vmoprcmd:

QUANTUM.SDLT600..csndb2a1 Yes Yes X0002 X0002 Yes dlt
csnbkp21 /dev/rmt/11cbn TLD
csndb2a1 /dev/nst5 ACTIVE

QUANTUM.SDLT600..csndb2a1002 Yes Yes X0010 X0016 Yes dlt
csnbkp21 /dev/rmt/3cbn TLD
csndb2a1 /dev/nst2 ACTIVE

Dennis Strom's picture

You may want to bring your netbackup sevices down then use robtest to move a tape into each drive and verify that your maping is correct using mt -f path status. You can also run scan and sgscan to verify your config.

Chia Tan Beng's picture

> I did see this in my vmoprcmd:
>
>QUANTUM.SDLT600..csndb2a1 Yes Yes X0002 X0002 Yes dlt
>csnbkp21 /dev/rmt/11cbn TLD
>csndb2a1 /dev/nst5 ACTIVE
>
>QUANTUM.SDLT600..csndb2a1002 Yes Yes X0010 X0016 Yes dlt
>csnbkp21 /dev/rmt/3cbn TLD
>csndb2a1 /dev/nst2 ACTIVE

Hi Michael,

I can see your second drive (i.e. csnbkp21 /dev/rmt/3cbn TLD) loaded a tape with internal MediaID of X0010 and with barcode ID X0016. Do consider my response to Hoger in this post. Also, Dennis has his point, try his suggestion too.