Video Screencast Help

Inventory failed: media ID not unique in database (34)

Created: 09 Feb 2014 • Updated: 10 Mar 2014 | 3 comments
This issue has been solved. See solution.

I got this error in Netbackup Administration Console:

Inventory failed: media ID not unique in database (34)

 

issues 34 error.JPG

Operating Systems:

Comments 3 CommentsJump to latest comment

Nicolai's picture

This can happen if two tapes has the same barcode label or if a tape has been removed from the tape robot without a following inventory. If the same tape is then imported via the CAP you will see the "media ID is not unique" because Netbackup will think the media is still in the robot.

Do the following:

Inventory the robot (this should move 0015L5 logical out of  the robot)

re-try to insert 0015L5 into the robot.

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

SOLUTION
DV1UBY's picture

I checked that this tape has not yet reached its retention period of 90 days since the tape is monthly tape. I inserted new tapes now its ok.

Marianne's picture

The location of a tape has nothing to do with retention period. The retention is not the reason why you cannot put it back in the robot - what if you need to restore from a tape that is offsite and you need to put it back in the robot?

Nicolai is probably right - NBU thought the tape was already in another slot in the robot.

You need to have another look at the method you use to remove tapes from the robot and put them back.

If your robot has a MAP/CAP, best to use it to eject media and reinsert tapes.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links