Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

media ID not unique in database (34)

Status
Not open for further replies.

kendas

Technical User
Feb 2, 2004
108
SG
hi,
i am not able to do an update invenetory for one of my tape.
it says "media ID not unique in database (34)"
pls help. thanks
 
I get that same error if I move too many tapes around and then do an inventory. All I've had to do in the past is to click the 'start' button again and it figures itself out.
Of corse this is on a linux master server and I feel that I'm a beta site for Veritas.

Carpe Queso (Seize the Cheese),
Mark
 
The only time I have seen this is when you remove the tape from the library and do NOT perform an inventory after removing the volume. Then try and put the volume back in the library and the volmgr still thinks that the tape is in the library therefore not allowing then duplicate tape to enter. Try performing an inventory first to update the Veritas library config and then try adding the volume back into the library. I am assuming you have alread looked into whether or not there could be a possible duplicate tape label.
 
I've had problems before with this.
What I ended up doing is ensuring that the tape is not in any of the libraries.
Then I reset the library which forces it to do a scan and build the physical inventory.
Then I inventory the robots with the netbackup application.
The two inventories are then in sync and the tape should show up as not in any library.
I then inject the tape into the desired library.


Bob Stump
Incorrigible punster -- Do not incorrige
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top