Veritas-bu

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

2008-09-18 18:32:34
Subject: Re: [Veritas-bu] media ID not unique in database (34)
From: <Mark.Donaldson AT cexp DOT com>
To: <Randy.Samora AT stewart DOT com>, <veritas-bu AT mailman.eng.auburn DOT edu>
Date: Thu, 18 Sep 2008 16:16:02 -0600
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

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