As you said your first robot0 died
I bet you did not get to eject the tapes from it.
So NB still thought the tapes were
in that library (look at media in gui and see it is assigned to a robot and a
slot)
What you needed to do is move all
the tapes to standalone (media right click choose standalone)
They NB would know they were NOT
in a library.
Then a inventory of the new
library robot2 would have changed the status of the tapes to show their
location in robot2
From:
veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Johan
Redelinghuys
Sent: Wednesday, May 12, 2010 7:37 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Netbackup and robot change.
Netbackup 6.5.4 on master server. Server connected to an I2K
robot. Robot went down and was replaced with a new one. All the tapes were
transferred over to the new robot. Drive and robot configuration deleted on
Netbackup master server and rescan was done. Robot and drives were picked up.
All in TLD control and all looked OK.
Ran robot inventory and “volume not unique in
database” error was encountered. Even pulling in the tapes via the cap
still produces the same error. Had to manually add each tape (128 tapes) one by
one. Selected move and changed standalone to robot. Selected the correct slot
and added the tape. Then right click tape and do a rescan and add .
What is the quickest way to get tapes back without going
this manually? The tapes were still protected so deleting them and then doing
inventory was not an option. What is the CLI options?
The issue seems to be that the volume group changed.
