Re: [Veritas-bu] media ID not unique in database (34)

THAT’S what I was looking for; thanks Mark!!

From: Mark.Donaldson AT cexp DOT com [mailto:Mark.Donaldson AT cexp DOT com]
Sent: Thursday, September 18, 2008 17:16: VIRUS ALERT!
To: Randy Samora; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] media ID not unique in database (34)

Do you have duplicate tape numbers? Barcode numbers? Most common reason.

Otherwise, pull all the offending tapes, let your library update it's inventory, and then sync netbackup against it using the GUI or:

vmupdate -rn <robnum> -rt <robtype> -rh <robhost> -use_barcode_rules

then inject the tapes again and allow the library to inventory & reupdate netbackup's inventory.

-M

From: veritas-bu-bounces AT mailman.eng.auburn DOT edu [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Randy Samora
Sent: Wednesday, September 17, 2008 4:57 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] media ID not unique in database (34)

My tape dude didn’t want to inventory new tapes into the library 54 at a time so he opened the door and inserted 200 tapes. When I try to run an inventory now, I get “media ID not unique in database (34)”. If I run a comparison, the robot inventory shows the new tapes but the Volume Configuration does not and so I see a “Mismatch – Yes”. But if I try to update the volume configuration, that’s when I get the Status 34. I’ve rebooted the library but the library already knows what’s in the library. How do I get NetBackup updated? This is a Windows environment running NBU 6.0 MP5.

Thanks

Randy

No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.169 / Virus Database: 270.6.21/1676 - Release Date: 9/17/2008 17:07: VIRUS ALERT!

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu