After a reboot this weekend, our SBS 2003 server now shows the Exabyte VXA320 1 x 10 1U Autoloader as Offline, although it does recognize the actual drive as online.
I have used all the suggested actions of Veritas support document 255501: How to troubleshoot issues with a Robotic Library or Tape Drive in Backup Exec 9.x and 10.x, but nothing seems to have worked.
We are using BE 10.1d SP2 Rev 5629.
I have tried uninstalling and reinstalling the drivers using tapeinst.exe and the latest driver download: BackupExecTapeDeviceDriverInstall20061015_285593.exe
I tried restoring the database, but unfortunately the latest one was made after the drive was registering offline.
The exabyte diagnostic tools all report and interact with the drive and loader fine.
In adamm.log, I see the following reported error:
0005:0000:0000:0000 Device Name ""
Primary Inquiry "EXABYTE VXA 1x10 1U A10D"
Serial Number ""
Device Flags SCSI
Device State 1, Offline, ERROR = 0x0000007B (ERROR_INVALID_NAME)
0005:0000:0001:0000 Device Name "\\.\Tape0"
Secondary Name "\\?\scsi#sequential&ven_exabyte&prod_vxa-3&rev_3106#6&13e34216&0&010#{53f5630b-b6bf-11d0-94f2-00a0c91efb8b}"
Primary Inquiry "EXABYTE VXA-3 3106"
Serial Number "EXABYTE VXA-3 V13106 000088100080"
Device Flags SCSI, SN(TYPE 1)
Device State 3, Online
Device IDs 1002, {E6580BB3-D0BE-4337-84CB-9824DC981A45}
Device Name "Exabyte VXA-320"
Device Type 33619968, "8MM 64K (64K,10,7,E)"
Device Features 0x0009FA7F
Device Element 1003, 0
Please help.