On Mon, 30 Oct 2006, "Koster, Phil" wrote:

> We have an old Storage TEK 9840 library that because of our setup
> requires a SCSI-to-Fiber bridge (connected through a Dell 56f, I know,
> break out the history books) for our NBU master to connect to it.  That
> connection is a little flakey and this weekend it "hiccupped" on us
> effectively killing all of our back ups.  For some reason it will not
> re-initialize itself when the communication is reliably restored.
> Management will not throw ANY money at this as there is a P.O. somewhere
> in our purchasing department for a whole new tape library.  (BTW, we are
> running NBU6 MP2 on a Win 2K Server.)
> 
> Question is:
> 
> Will a "tpconfig -l" get us to a point where we can tell what is going
> on and be able to parse it or should we be doing something else?  
> 
> From my own experimentation it looks like a tpconfig -l will not
> actually tell us the robot's status (always shows up as a hyphen) but we
> can see the drive status which (near as I can tell) should be UP, DOWN,
> or AVR.  So in theory we could parse for the AVR status on the drives
> and go from there.  Problem is we have a second NBU server that uses the
> same robot through our master that we will begin using soon to offload
> some of the work from the master.  Neither of us NBU guys here know what
> that drive status will show up as when the secondary kicks in.  Am I on
> the right path?  Anyone?  Anyone?  Bueller?  Bueller?  
> 
> Thanks.
> 
> Phil Koster
> Network Administrator
> City of Grand Rapids
> Direct: 616-456-3136
> Helpdesk: 456-3999
> 
> 

Definitely be watching for AVR as when 1 or more drives are in AVR, the 
robot could be hung up or have a serious error.

Justin.