In case it's not obvious, it may be important to recall that "DOWN" is a 
NetBackup status, not an operating system or hardware state.  The robot 
and drive may be in perfect health, but still NetBackup may set the 
drive status to "DOWN".

I'd first look in the (v5.1) error file.  On Unix servers this is 
"/usr/openv/netbackup/db/media/errors" ... probably similar in Win2003.

Then I'd look at the "bptm" logs.  See the troubleshooting guide for 
instructions on setting up logging, if not already setup.

cheers, wayne

Matt Ungaro wrote, in part,  on 2/20/2007 4:52 PM:
> System is Veritas Netbackup 5.1 MP6
> 1 Master/Media server running on Windows 2003 standard edition, SP1
> Library is a Qualstar TLS-8466 with 4 drives. 2 LTOII that are 
> attached to our Fibre Channel SAN via a SCSI to fibre bridge, 2 LTOIII 
> that are directly fibre attached to our SAN. All are going through a 
> McData Spherion 4500.
>  
> Seemingly random issue that is occuring is that on occasion our LTOIII 
> drives will be reported in Netbackup as down. What I am looking for 
> is, what are the correct Netbackup processes to activate logging on to 
> get some troubleshooting information? The drive doesn't report as 
> having any problems from the library's perspective, and there are no 
> error messages on the fabric switches. The Netbackup server is zoned 
> to each fibre port in the library individually, so there are 3 zones:
> Netbackup server to SCSI to fibre bridge (Controls robotic arm, and 2 
> LTOII drives)
> Netbackup server to LTOIII drive 1
> Netbackup server to LTOIII drive 2.
>  
> We never have any issues with the LTOII drives or the robotic arm, but 
> the LTOIII drives go down for seemingly no reason whatsoever. Any 
> assistance with troubleshooting this issue is greatly appreciated. 
> Thanks in advance!