echarnley
Joined 17 years ago
User Profile
User Widgets
Contributions
Exabyte Drive Not Recognized - Please Help!
I am running Backup Exec 10D on a new server installation. We have an Exabyte VXA-2 DAT drive installed. Backup Exec will see the device when I install the Veritas drivers, but the drive will never show up under devices after this. Windows sees the drive in device manager. I have uninstalled and reinstalled the drivers multiple times, but it still never shows up in Backup Exec. I have checked the hardware compatibility list and this drive is supported. The drive is attached via SCSI to an LSI Logic PCI-X Ultra320 SCSI Host Adapter. Here are some of the contents of the adamm.log file (since I cannot exceed 2000 characters in this post I will only post the first part that contains some of the errors): ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [2204] 06/07/07 09:42:59 Adamm Log Started! ("RUNNER", 1000, {C67FE115-77CA-4CFE-AC74-3A04500C5FEF}) Adamm Info: Version 10.1, Build 5629 OS Info: Windows NT 5.2, Build 3790, Service Pack 1 Database Driver Info: SQLSRV32.DLL, 03.86.1830 Database Server Info: Server Name = "RUNNER", Active Node = "" Database Connection String: "DRIVER=SQL Server;SERVER=RUNNER\BkupExec;DATABASE=BEDB" DateTimeSync: Local = 2007/06/07 09:42:59, System = 2007/06/07 16:42:59 GMT, Database = 2007/06/07 16:42:59 GMT Shared Storage Authorization: No TSM Authorization: Yes Library Expansion Options: 1 [2852] 06/07/07 09:43:00 Device Registry: Scsi Address Prt :Bus :Tar :Lun Attributes ------------------- ------------------------------------------------------------------------------- 0000:0000:0000:0000 "atapi", (Port Driver) ------------------- ------------------------------------------------------------------------------- 0001:0000:0000:0000 "atapi", (Port Driver) ------------------- ------------------------------------------------------------------------------- 0002:0000:0000:0000 "HpCISSs2", (Port Driver) ------------------- ------------------------------------------------------------------------------- 0003:0000:0000:0000 "symmpi", (Port Driver) 0003:0000:0011:0000 "EXABYTE VXA-2 210D", (Tape Device), "\\.\Tape0" ------------------- ------------------------------------------------------------------------------- [2852] 06/07/07 09:43:00 PnP Device Paths: Scsi Address Prt :Bus :Tar :Lun Device Path ----------------------------------- ------------------------------------------------------------------------------- 00000003:00000000:00000011:00000000 \\?\scsi#sequential&ven_exabyte&prod_vxa-2&rev_210d#6&395c19b3&0&0b0#{53f5630b-b6bf-11d0-94f2-00a0c91efb8b} [2852] 06/07/07 09:43:00 Read Device Records - start [2852] 06/07/07 09:43:00 Read Device Records - end [2852] 06/07/07 09:43:00 Read Device Inquiries - start [2204] 06/07/07 09:53:30 Adamm Log Stopped! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [4668] 06/07/07 09:53:31 Adamm Log Started! ("RUNNER", 1000, {C67FE115-77CA-4CFE-AC74-3A04500C5FEF}) Adamm Info: Version 10.1, Build 5629 OS Info: Windows NT 5.2, Build 3790, Service Pack 1 Database Driver Info: SQLSRV32.DLL, 03.86.1830 Database Server Info: Server Name = "RUNNER", Active Node = "" Database Connection String: "DRIVER=SQL Server;SERVER=RUNNER\BkupExec;DATABASE=BEDB" DateTimeSync: Local = 2007/06/07 09:53:31, System = 2007/06/07 16:53:31 GMT, Database = 2007/06/07 16:53:31 GMT Shared Storage Authorization: No TSM Authorization: Yes Library Expansion Options: 1 [4800] 06/07/07 09:53:46 Device Registry: Scsi Address Prt :Bus :Tar :Lun Attributes ------------------- ------------------------------------------------------------------------------- 0000:0000:0000:0000 "atapi", (Port Driver) ------------------- ------------------------------------------------------------------------------- 0001:0000:0000:0000 "atapi", (Port Driver) ------------------- ------------------------------------------------------------------------------- 0002:0000:0000:0000 "HpCISSs2", (Port Driver) ------------------- ------------------------------------------------------------------------------- 0003:0000:0000:0000 "symmpi", (Port Driver) 0003:0000:0011:0000 "EXABYTE VXA-2 210D", (Tape Device), "\\.\Tape0" ------------------- ------------------------------------------------------------------------------- [4800] 06/07/07 09:53:46 PnP Device Paths: Scsi Address Prt :Bus :Tar :Lun Device Path ----------------------------------- ------------------------------------------------------------------------------- 00000003:00000000:00000011:00000000 \\?\scsi#sequential&ven_exabyte&prod_vxa-2&rev_210d#6&395c19b3&0&0b0#{53f5630b-b6bf-11d0-94f2-00a0c91efb8b} [4800] 06/07/07 09:53:46 Read Device Records - start [4800] 06/07/07 09:53:46 Read Device Records - end [4800] 06/07/07 09:53:46 Read Device Inquiries - start [4668] 06/07/07 09:56:56 Adamm Log Stopped! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [2164] 06/07/07 10:02:20 Adamm Log Started! ("RUNNER", 1000, {C67FE115-77CA-4CFE-AC74-3A04500C5FEF}) Adamm Info: Version 10.1, Build 5629 OS Info: Windows NT 5.2, Build 3790, Service Pack 1 Database Driver Info: SQLSRV32.DLL, 03.86.1830 Database Server Info: Server Name = "RUNNER", Active Node = "" Database Connection String: "DRIVER=SQL Server;SERVER=RUNNER\BkupExec;DATABASE=BEDB" [3892] 06/07/07 10:02:20 PnP Device Paths: Scsi Address Prt :Bus :Tar :Lun Device Path ----------------------------------- ------------------------------------------------------------------------------- 00000003:00000000:00000011:00000000 \\?\scsi#sequential&ven_exabyte&prod_vxa-2&rev_210d#6&395c19b3&0&0b0#{53f5630b-b6bf-11d0-94f2-00a0c91efb8b} [3892] 06/07/07 10:02:20 Read Device Records - start [3892] 06/07/07 10:02:20 Read Device Records - end [3892] 06/07/07 10:02:20 Read Device Inquiries - start [3892] 06/07/07 10:02:51 ReadDeviceScsiInquiryInfo - failed [3892] 06/07/07 10:03:27 ReadDeviceScsiInquiryInfo - failed [3892] 06/07/07 10:04:03 ReadDeviceScsiInquiryInfo - failed [3892] 06/07/07 10:04:39 ReadDeviceScsiInquiryInfo - failed [3892] 06/07/07 10:05:15 ReadDeviceScsiInquiryInfo - failed [3892] 06/07/07 10:05:51 ReadDeviceScsiInquiryInfo - failed [3892] 06/07/07 10:06:27 ReadDeviceScsiInquiryInfo - failed [3892] 06/07/07 10:07:03 ReadDeviceScsiInquiryInfo - failed [3892] 06/07/07 10:07:39 ReadDeviceScsiInquiryInfo - failed [3892] 06/07/07 10:08:15 ReadDeviceScsiInquiryInfo - failed [3892] 06/07/07 10:08:51 ReadDeviceScsiInquiryInfo - failed [3892] 06/07/07 10:09:27 ReadDeviceScsiInquiryInfo - failed [3892] 06/07/07 10:10:03 ReadDeviceScsiInquiryInfo - failed [3892] 06/07/07 10:10:39 ReadDeviceScsiInquiryInfo - failed [3892] 06/07/07 10:11:15 ReadDeviceScsiInquiryInfo - failed [3892] 06/07/07 10:11:51 ReadDeviceScsiInquiryInfo - failed [3892] 06/07/07 10:12:27 ReadDeviceScsiInquiryInfo - failed [3892] 06/07/07 10:13:03 ReadDeviceScsiInquiryInfo - failed [3892] 06/07/07 10:13:39 ReadDeviceScsiInquiryInfo - failed [3892] 06/07/07 10:14:15 ReadDeviceScsiInquiryInfo - failed [3892] 06/07/07 10:14:51 ReadDeviceScsiInquiryInfo - failed [3892] 06/07/07 10:15:27 ReadDeviceScsiInquiryInfo - failed [3892] 06/07/07 10:16:03 ReadDeviceScsiInquiryInfo - failed [3892] 06/07/07 10:16:39 ReadDeviceScsiInquiryInfo - failed [3892] 06/07/07 10:17:15 ReadDeviceScsiInquiryInfo - failed [3892] 06/07/07 10:17:51 ReadDeviceScsiInquiryInfo - failed [3892] 06/07/07 10:18:27 ReadDeviceScsiInquiryInfo - failed [3892] 06/07/07 10:19:03 ReadDeviceScsiInquiryInfo - failed [3892] 06/07/07 10:19:39 ReadDeviceScsiInquiryInfo - failed [3892] 06/07/07 10:20:15 ReadDeviceScsiInquiryInfo - failed [3892] 06/07/07 10:20:51 ReadDeviceScsiInquiryInfo - failed [3892] 06/07/07 10:21:27 ReadDeviceScsiInquiryInfo - failed [3892] 06/07/07 10:22:03 ReadDeviceScsiInquiryInfo - failed [3892] 06/07/07 10:22:39 ReadDeviceScsiInquiryInfo - failed [3892] 06/07/07 10:22:44 Read Device Inquiries - end [3892] 06/07/07 10:22:44 Serialize Devices: [3892] 06/07/07 10:22:44 Device Discovery: Scsi Address Prt :Bus :Tar :Lun Attributes ------------------- ------------------------------------------------------------------------------- 0003:0000:0011:0000 Device Name "\\.\Tape0" Secondary Name "\\?\scsi#sequential&ven_exabyte&prod_vxa-2&rev_210d#6&395c19b3&0&0b0#{53f5630b-b6bf-11d0-94f2-00a0c91efb8b}" Primary Inquiry "EXABYTE VXA-2 210D" Serial Number "" Device Flags SCSI Device State 1, Offline, ERROR = 0x00000005 (ERROR_ACCESS_DENIED) ------------------- ------------------------------------------------------------------------------- [3892] 06/07/07 10:22:44 Start Rsm Support: [3892] 06/07/07 10:22:50 Device Discovery End: [2164] 09/05/07 17:25:04 Adamm Log Stopped! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Any help would be greatly appreciated. I have tried everything I can think of and the drive is still not recognized in Backup Exec. Thanks in advance, Eric Charnley106Views0likes0Comments