Issue with unloading Tapes into use slots in silo
The issue is the silo is moving tapes to incorrect slots
- Netbackup obtains tape label and position direct from silo when an inventory is ran. The software depends on the silo moving tapes used from the drives back to the same slot it was called from.
- Tape once used gives a request to robot to unload drive and move tape back to it’s original slot number. The silo is not doing this. It appears to be trying to move tape to be unloaded back to a slot that is in use. Therefore we are forced to manual unload tape and run an inventory from Master NB server.
- The robot always reports that tapes are now in a new slot and not the original. This means the robot is moving tapes internally to incorrect slots and giving false report on tape location
4. This issue only started after the first 36 hours. During this time no tapes were in use by the installed slots. Once silo started to use them the problem appeared
Quantum say this is a Netbackup issue - I've never seen anything like this - it's causing havoc on our backup system. We are on 7.0.1 - we have two i500s the one that didn't get an upgarde is still operating without issue.
The problem is with the silo where we added 3 drives and 36 more slots.
OK - I would try the following:
Empty the library - making sure no tapes are in drives
Update the inventory making sure all tapes have dissapeared from the library section of the admin console
If any remain the right click then and select "Move" and then select StandAlone so that nothing shows as being in the library in NetBackup
Next re-run the device configuration wizard against the library
Then re-inventory the library and try again to see if this puts things right
If it still goes wrong call Quantum and maybe get the latest fireware the the tape library
Also makes sure you do not have any drivers loaded for the robot in Windows (assuming you are using Windows Media Servers - if you do ten roll them back so the library shows in device manager as an "unknown medium changer" (if you do this you will need to re-boot and re-run the device configuration wizard)
Hope this helps