Inventory Robot wrongly telling me the device is up to date.

[jonnyguitar]

I have a Dell ML6000 Tape Library and usually import tapes by slotting them into the media access port, then going to Inventory Robot, clicking "empty media access port" and then start.

 However since yesterday Inventory Robot is saying the library is up to date.

What is causing this?  I've checked there is space in the library.  Also there are no problems with the library at all.  

Any help would be appreciated.  Thanks

[mph999]

Run robtest

run command

s p

(This shows what is in the MAP)

Is the output showing really what is there, or is the output wrong.

Martin

[Marianne]

So, you are putting tapes in the Access port, tell NBU to Empty, then update, but nothing happens? Access port is not emptied?

Tapes still in the MAP/CAP?

Can you confirm that the tapes in the MAP can be seen using robtest?  

See  http://www.symantec.com/docs/TECH83129 for robtest usage.

s p returns the status of all "media access port" slots

If all is fine doing this you need to enable logging in NBU. 

Add VERBOSE entry to vm.conf on robot control host, then create debug folder under volmgr.
Create the following folders in debug:
daemon
ltid
reqlib

Can't remember the exact one where inventory actions are logged, but it's definitely one of those.

Restart NBU to enable this logging.

[Marianne]

Oops! took to long to click 'Save'! 

[jonnyguitar]

Thanks!  Does Robtest interrupt or cancel a current backup job?  There are two jobs that have been running for ages I don't want to interrupt.

[Marianne]

No, it will not interrupt backups.

It will just prevent any new mounts/dismounts while robtest is running.

[mph999]

robots log definately gets caontains info when an inventory is run.

[jonnyguitar]

I ran robtest and it came back with the tapes in the MAP. 

In the end I imported them using the ML6000 library GUI, instead of NBU.  But I don't think NBU can see the tapes until I do another inventory.  Now when I do an inventory I get error

"robot busy cannot perform operation (223)".  What a bother.

I'll do what you suggested regardling logging but I don't think logging works either!  Might call support.

Thanks for everyone's help and suggestions so far by the way.  Really appreciated.

[Marianne]

 but I don't think logging works either! 

Logging does not fix anything, it will just log NBU actions. 
I cannot imagine that Symantec Support will be able to assist without logs.
 

[mph999]

When you run the inventory, be sure to select the 'empty map' check box.

Also, make sure you exit robtest before you run an inventory.

Finally, I'd reboot everything and see if it works after that (including the library).

Martin

[jonnyguitar]

Thanks everyone.  Lots of problems here - one caused by the other.  I think figuring out logging is the way to go.

I've read as much logging information in the docs as I can but I still don't think it's working as it should.  Where do I enable logging?  The admin guide refers to check boxes in "Master server properties" but I don't appear to have a "Master server properties" window anywhere?

[Marianne]

You need to create the log folders.

You never told us the OS on your master and/or robot control host, so my post about logs is pretty much 'generic'.

Please see this extract from my earlier post:

Add VERBOSE entry to vm.conf (in volmgr folder) on robot control host, then create debug folder under volmgr.
Create the following folders in debug:
daemon
ltid
reqlib

(Martin has added 'robot' to the mix)

Restart NBU to enable this logging.

See 'Directory names for legacy debug logs for media and device management' in NBU Troubleshooting Guide.

[Will_Restore]

You have to disable 'manual cartridge assignment' in the library

[Will_Restore]

Johnny, did you get this working?

[jonnyguitar]

Seems ok now, but not entriely sure what the matter was I'm afraid.