cancel
Showing results for 
Search instead for 
Did you mean: 

Backup Exec 10d - Event ID 33152 - Adamm Mover Error: GetDriveInfo Failure!

Chris_Campbell
Level 2
Application: Backup Exec 10d for Windows Servers 10.1.5629
Platform: Windows Server 2003 R2 Standard Edition
Tape Drive: HP DAT72 Drive C7438A
Backup Exec Updates Applied:
Service Pack 2
Hotfix 43
Hotfix 46
Hotfix 45
Latest Veritas Tape Drivers
http://seer.support.veritas.com/docs/284707.htm

Problem Description:

Backup Exec 10d running on a Brand new HP ML350 with on-board SCSI controller for the HP DAT72 Drive. (Separate RAID Controller for Disks).

Have removed/updated both the Tape Drive and Backup Exec sooooo many times now im stuck with the below problem, please can anyone help? I thought I could get telephone support from Veritas/Symantec with this, but not without a cost! Anyway.... can anyone help with the below? U'll be given a God status!

Tape device has been detected by Backup Exec and the relevant drivers installed,

Driver Provider: Symantec Corporation
Driver Date: 23/06/2006
Driver Version: 5.1.23.0

Prior to this of course was the latest HP drivers, 1.5.32.

Device is there and viewable under All Devices with correct information etc.

But... and here is the problem folks....

As soon as I do anything with the Device, i.e run an Inventory, Eject, Backup etc... the job just keeps running, and running, and running doesn't actually stop unless I stop it myself. Also in the Event Viewer I get these two messages, they seem fairly generic to me, but maybe the "Aha" for someone reading this?? (I hope so!).



Under Application Log -

Date: Date
Time: Time
Type: Error
User: N/A
Computer: Server Name
Source: Backup Exec
Category: Devices
EventID: 33152

Description:
Adamm Mover Error: GetDriveInfo Failure!
Error = ERROR_IO_DEVICE
Drive = "HP 1"
{F29FDA30-E512-4FD3-893F-EA7575C9443E}
Media = ""
{00000000-0000-0000-0000-000000000000}
Read Mode: SingleBlock(0), ScsiPass(0)
Write Mode: SingleBlock(1), ScsiPass(1)



Under System Log:

Date: Date
Time: Time
Type: Error
User: N/A
Computer: Server Name
Source: Lsi_scsi
Category: None
EventID: 11

Description:
The driver detected a controller error on \Device\Raidport0



Now the Application Log Error (event id 33152) comes up every 1-2 seconds when something is running in Backup Exec. And so does the event 11.

Ive run the SGMON utility and pasted the outputted log below for an Inventory run for about 3 minutes before I cancelled it, as it would have just kept running! Don't know if this is useful for anyone...? -

Capturing to C:\Program Files\VERITAS\Backup Exec\NT\logs\SGMon.log
beserver: 12/18/06 12:20:27 20 Auto Clear Alerts Query
beserver: 12/18/06 12:20:40 -1 SQLLog(1930):AgeSession m_threadMap: SessionThreadID:350, CurrentThreadID:1100
beserver: 12/18/06 12:21:28 20 Auto Clear Alerts Query
beserver: 12/18/06 12:21:29 -1 Job Manager: LoadJob() request completed
beserver: 12/18/06 12:21:34 12 AdammAdminBO::Query() - Parent = NULL , Entity = MACHINE
pvlsvr: 12/18/06 12:21:34 PvlEntityDatabase::QueryEntity()
ParentEntityType = NULL_ENTITY_TYPE
ParentEntityGuid = {00000000-0000-0000-0000-000000000000}
EntityType = MACHINE_ENTITY_TYPE
EntityGuid = {082AB79C-1C97-4EAF-B097-078C1E52CA1D}
EntityName = ""
EntityFlags = 0x00008000
beserver: 12/18/06 12:21:34 12 AdammAdminBO::Query() - hr = 0x0
beserver: 12/18/06 12:21:34 12 AdammAdminBO::Query() - Parent = NULL , Entity = DEVICE_POOL
pvlsvr: 12/18/06 12:21:34 PvlEntityDatabase::QueryEntity()
ParentEntityType = NULL_ENTITY_TYPE
ParentEntityGuid = {00000000-0000-0000-0000-000000000000}
EntityType = DEVICE_POOL_ENTITY_TYPE
EntityGuid = {00000000-0000-0000-0000-000000000000}
EntityName = ""
EntityFlags = 0x00008000
beserver: 12/18/06 12:21:34 12 AdammAdminBO::Query() - hr = 0x0
beserver: 12/18/06 12:21:34 12 AdammAdminBO::Query() - Parent = MACHINE , Entity = DRIVE
pvlsvr: 12/18/06 12:21:34 PvlEntityDatabase::QueryEntity()
ParentEntityType = MACHINE_ENTITY_TYPE
ParentEntityGuid = {082AB79C-1C97-4EAF-B097-078C1E52CA1D}
EntityType = DRIVE_ENTITY_TYPE
EntityGuid = {00000000-0000-0000-0000-000000000000}
EntityName = ""
EntityFlags = 0x00008000
beserver: 12/18/06 12:21:34 12 AdammAdminBO::Query() - hr = 0x0
beserver: 12/18/06 12:21:34 12 AdammAdminBO::Query() - Parent = MACHINE , Entity = BACKUP_TO_DISK
pvlsvr: 12/18/06 12:21:34 PvlEntityDatabase::QueryEntity()
ParentEntityType = MACHINE_ENTITY_TYPE
ParentEntityGuid = {082AB79C-1C97-4EAF-B097-078C1E52CA1D}
EntityType = BACKUP_TO_DISK_ENTITY_TYPE
EntityGuid = {00000000-0000-0000-0000-000000000000}
EntityName = ""
EntityFlags = 0x00008000
beserver: 12/18/06 12:21:34 12 AdammAdminBO::Query() - hr = 0x0
beserver: 12/18/06 12:21:34 12 AdammAdminBO::Query() - Parent = MACHINE , Entity = DRIVE_POOL_DRIVE
pvlsvr: 12/18/06 12:21:34 PvlEntityDatabase::QueryEntity()
ParentEntityType = MACHINE_ENTITY_TYPE
ParentEntityGuid = {082AB79C-1C97-4EAF-B097-078C1E52CA1D}
EntityType = DRIVE_POOL_DRIVE_ENTITY_TYPE
EntityGuid = {00000000-0000-0000-0000-000000000000}
EntityName = ""
EntityFlags = 0x00008000
beserver: 12/18/06 12:21:34 12 AdammAdminBO::Query() - hr = 0x0
beserver: 12/18/06 12:21:34 12 AdammAdminBO::Query() - Parent = MACHINE , Entity = CHANGER
pvlsvr: 12/18/06 12:21:34 PvlEntityDatabase::QueryEntity()
ParentEntityType = MACHINE_ENTITY_TYPE
ParentEntityGuid = {082AB79C-1C97-4EAF-B097-078C1E52CA1D}
EntityType = LIBRARY_ENTITY_TYPE
EntityGuid = {00000000-0000-0000-0000-000000000000}
EntityName = ""
EntityFlags = 0x00008000
beserver: 12/18/06 12:21:34 12 AdammAdminBO::Query() - hr = 0x0
beserver: 12/18/06 12:21:34 -1 ActiveState::doDispatch( :( 'Inventory Drive 00002'
beserver: 12/18/06 12:21:34 17 CJobManagerBO::Query QUERY_JOBSETUP_MONITOR
beserver: 12/18/06 12:21:34 -1 LocalSvr, runTask():{5f1f648d-3bf8-4026-a585-cbe60061f8a2}
beserver: 12/18/06 12:21:34 12 AdammAdminBO::Get() - Parent = NULL , Entity = DEVICE
pvlsvr: 12/18/06 12:21:34 PvlEntityDatabase::QueryEntity()
ParentEntityType = NULL_ENTITY_TYPE
ParentEntityGuid = {00000000-0000-0000-0000-000000000000}
EntityType = DEVICE_ENTITY_TYPE
EntityGuid = {F29FDA30-E512-4FD3-893F-EA7575C9443E}
EntityName = ""
EntityFlags = 0x00000000
beserver: 12/18/06 12:21:34 12 AdammAdminBO::Get() - hr = 0x0
beserver: 12/18/06 12:21:34 11 LocalSvr, RunTask: EngineHandedJob SUCCESS, jobid:{5f1f648d-3bf8-4026-a585-cbe60061f8a2}.
beserver: 12/18/06 12:21:36 -1 UtilityJobThread - started
beserver: 12/18/06 12:21:36 12 AdammAdminBO::Query() - Parent = NULL , Entity = MACHINE
pvlsvr: 12/18/06 12:21:36 PvlEntityDatabase::QueryEntity()
ParentEntityType = NULL_ENTITY_TYPE
ParentEntityGuid = {00000000-0000-0000-0000-000000000000}
EntityType = MACHINE_ENTITY_TYPE
EntityGuid = {00000000-0000-0000-0000-000000000000}
EntityName = ""
EntityFlags = 0x00000000
beserver: 12/18/06 12:21:36 12 AdammAdminBO::Query() - hr = 0x0
pvlsvr: 12/18/06 12:21:36 AdammSession::Execute( ADAMM_SESSION_EXECUTE_SESSION_SET_JOB_INFO )
Session = {870712A9-478E-4CC1-849C-FAE585E502BD}
Job = {5F1F648D-3BF8-4026-A585-CBE60061F8A2}, "Inventory Drive 00002"
beserver: 12/18/06 12:21:36 -1 Start Inventory
pvlsvr: 12/18/06 12:21:36 AdammSession::Execute( ADAMM_SESSION_EXECUTE_INVENTORY_READ_MEDIA_HEADER )
Session = {870712A9-478E-4CC1-849C-FAE585E502BD}
Device = {F29FDA30-E512-4FD3-893F-EA7575C9443E}, "HP 1"
beserver: 12/18/06 12:21:39 17 CJobManagerBO::Query QUERY_JOBSETUP_MONITOR
pvlsvr: 12/18/06 12:21:39 AdammSession::MediaUtilityThreadProc( ADAMM_SESSION_EXECUTE_INVENTORY_READ_MEDIA_HEADER )
Session = {EB70FEC7-6651-4D2A-924C-15818F651550}
Job = {5F1F648D-3BF8-4026-A585-CBE60061F8A2}, "Inventory Drive 00002"
Drive = {F29FDA30-E512-4FD3-893F-EA7575C9443E}, "HP 1"
Slot = 0000
Side = 0000
beserver: 12/18/06 12:21:41 -1 Client requested key.
beserver: 12/18/06 12:21:41 -1 Client 'SR0003DJL' connected('','DJL\administrator'): 0x157eab8
pvlsvr: 12/18/06 12:22:01 AdammSession::MediaUtilityThreadProc( ADAMM_SESSION_EXECUTE_INVENTORY_READ_MEDIA_HEADER )
Session = {EB70FEC7-6651-4D2A-924C-15818F651550}
Job = {5F1F648D-3BF8-4026-A585-CBE60061F8A2}, "Inventory Drive 00002"
Drive = {F29FDA30-E512-4FD3-893F-EA7575C9443E}, "HP 1"
Slot = 0000
Side = 0000
pvlsvr: 12/18/06 12:22:23 AdammSession::MediaUtilityThreadProc( ADAMM_SESSION_EXECUTE_INVENTORY_READ_MEDIA_HEADER )
Session = {EB70FEC7-6651-4D2A-924C-15818F651550}
Job = {5F1F648D-3BF8-4026-A585-CBE60061F8A2}, "Inventory Drive 00002"
Drive = {F29FDA30-E512-4FD3-893F-EA7575C9443E}, "HP 1"
Slot = 0000
Side = 0000
beserver: 12/18/06 12:22:28 20 Auto Clear Alerts Query
beserver: 12/18/06 12:22:40 -1 SQLLog(1931):AgeSession m_threadMap: SessionThreadID:ebc, CurrentThreadID:13ec
beserver: 12/18/06 12:22:40 -1 SQLLog(1932):AgeSession m_threadMap: SessionThreadID:f10, CurrentThreadID:13ec
beserver: 12/18/06 12:22:40 -1 SQLLog(1933):AgeSession m_threadMap: SessionThreadID:1100, CurrentThreadID:13ec
beserver: 12/18/06 12:22:40 -1 SQLLog(1934):AgeSession m_threadMap: SessionThreadID:14a4, CurrentThreadID:13ec
beserver: 12/18/06 12:22:40 -1 SQLLog(1935):AgeSession m_threadMap: SessionThreadID:17dc, CurrentThreadID:13ec
beserver: 12/18/06 12:22:40 -1 SQLLog(1936):AgeSession m_threadMap: SessionThreadID:17e4, CurrentThreadID:13ec
pvlsvr: 12/18/06 12:22:46 AdammSession::MediaUtilityThreadProc( ADAMM_SESSION_EXECUTE_INVENTORY_READ_MEDIA_HEADER )
Session = {EB70FEC7-6651-4D2A-924C-15818F651550}
Job = {5F1F648D-3BF8-4026-A585-CBE60061F8A2}, "Inventory Drive 00002"
Drive = {F29FDA30-E512-4FD3-893F-EA7575C9443E}, "HP 1"
Slot = 0000
Side = 0000
pvlsvr: 12/18/06 12:23:08 AdammSession::MediaUtilityThreadProc( ADAMM_SESSION_EXECUTE_INVENTORY_READ_MEDIA_HEADER )
Session = {EB70FEC7-6651-4D2A-924C-15818F651550}
Job = {5F1F648D-3BF8-4026-A585-CBE60061F8A2}, "Inventory Drive 00002"
Drive = {F29FDA30-E512-4FD3-893F-EA7575C9443E}, "HP 1"
Slot = 0000
Side = 0000
beserver: 12/18/06 12:23:29 20 Auto Clear Alerts Query
pvlsvr: 12/18/06 12:23:30 AdammSession::MediaUtilityThreadProc( ADAMM_SESSION_EXECUTE_INVENTORY_READ_MEDIA_HEADER )
Session = {EB70FEC7-6651-4D2A-924C-15818F651550}
Job = {5F1F648D-3BF8-4026-A585-CBE60061F8A2}, "Inventory Drive 00002"
Drive = {F29FDA30-E512-4FD3-893F-EA7575C9443E}, "HP 1"
Slot = 0000
Side = 0000
pvlsvr: 12/18/06 12:23:52 AdammSession::MediaUtilityThreadProc( ADAMM_SESSION_EXECUTE_INVENTORY_READ_MEDIA_HEADER )
Session = {EB70FEC7-6651-4D2A-924C-15818F651550}
Job = {5F1F648D-3BF8-4026-A585-CBE60061F8A2}, "Inventory Drive 00002"
Drive = {F29FDA30-E512-4FD3-893F-EA7575C9443E}, "HP 1"
Slot = 0000
Side = 0000
pvlsvr: 12/18/06 12:24:14 AdammSession::MediaUtilityThreadProc( ADAMM_SESSION_EXECUTE_INVENTORY_READ_MEDIA_HEADER )
Session = {EB70FEC7-6651-4D2A-924C-15818F651550}
Job = {5F1F648D-3BF8-4026-A585-CBE60061F8A2}, "Inventory Drive 00002"
Drive = {F29FDA30-E512-4FD3-893F-EA7575C9443E}, "HP 1"
Slot = 0000
Side = 0000
beserver: 12/18/06 12:24:29 20 Auto Clear Alerts Query
pvlsvr: 12/18/06 12:24:36 AdammSession::MediaUtilityThreadProc( ADAMM_SESSION_EXECUTE_INVENTORY_READ_MEDIA_HEADER )
Session = {EB70FEC7-6651-4D2A-924C-15818F651550}
Job = {5F1F648D-3BF8-4026-A585-CBE60061F8A2}, "Inventory Drive 00002"
Drive = {F29FDA30-E512-4FD3-893F-EA7575C9443E}, "HP 1"
Slot = 0000
Side = 0000
beserver: 12/18/06 12:24:40 -1 SQLLog(1937):AgeSession m_threadMap: SessionThreadID:f78, CurrentThreadID:1070
beserver: 12/18/06 12:24:40 -1 SQLLog(1938):AgeSession m_threadMap: SessionThreadID:13ec, CurrentThreadID:1070
pvlsvr: 12/18/06 12:24:58 AdammSession::MediaUtilityThreadProc( ADAMM_SESSION_EXECUTE_INVENTORY_READ_MEDIA_HEADER )
Session = {EB70FEC7-6651-4D2A-924C-15818F651550}
Job = {5F1F648D-3BF8-4026-A585-CBE60061F8A2}, "Inventory Drive 00002"
Drive = {F29FDA30-E512-4FD3-893F-EA7575C9443E}, "HP 1"
Slot = 0000
Side = 0000
pvlsvr: 12/18/06 12:25:20 AdammSession::MediaUtilityThreadProc( ADAMM_SESSION_EXECUTE_INVENTORY_READ_MEDIA_HEADER )
Session = {EB70FEC7-6651-4D2A-924C-15818F651550}
Job = {5F1F648D-3BF8-4026-A585-CBE60061F8A2}, "Inventory Drive 00002"
Drive = {F29FDA30-E512-4FD3-893F-EA7575C9443E}, "HP 1"
Slot = 0000
Side = 0000
beserver: 12/18/06 12:25:30 20 Auto Clear Alerts Query
bengine: 12/18/06 12:25:40 DeviceManager: timeout event fired
bengine: 12/18/06 12:25:40 DeviceManager: processing pending requests
bengine: 12/18/06 12:25:40 DeviceManager: going to sleep for 900000 msecs
beserver: 12/18/06 12:25:42 -1 ActiveState::doCancel( 'DJL\administrator', 1 :( Inventory Drive 00002
pvlsvr: 12/18/06 12:25:42 PvlEntityDatabase::UpdateEntity()
ParentEntityType = NULL_ENTITY_TYPE
ParentEntityGuid = {00000000-0000-0000-0000-000000000000}
EntityType = SESSION_ENTITY_TYPE
pvlsvr: 12/18/06 12:25:42 PvlEntityDatabase::UpdateEntity() : SUCCESS!
beserver: 12/18/06 12:25:42 11 LocalSvr, RunTask: EngineHandedJob, SUCCESS TaskID:{5f1f648d-3bf8-4026-a585-cbe60061f8a2}. nReval:0x0.
pvlsvr: 12/18/06 12:25:42 AdammSession::MediaUtilityThreadProc( ADAMM_SESSION_EXECUTE_INVENTORY_READ_MEDIA_HEADER )
Session = {EB70FEC7-6651-4D2A-924C-15818F651550}
Job = {5F1F648D-3BF8-4026-A585-CBE60061F8A2}, "Inventory Drive 00002"
Drive = {F29FDA30-E512-4FD3-893F-EA7575C9443E}, "HP 1"
Slot = 0000
Side = 0000
beserver: 12/18/06 12:25:48 -1 End Inventory
beserver: 12/18/06 12:25:48 -1 UtilityJobThread - catalog
beserver: 12/18/06 12:25:48 -1 UtilityJobThread - log file
beserver: 12/18/06 12:25:48 12 AdammAdminBO::Query() - Parent = NULL , Entity = DRIVE
pvlsvr: 12/18/06 12:25:48 PvlEntityDatabase::QueryEntity()
ParentEntityType = NULL_ENTITY_TYPE
ParentEntityGuid = {00000000-0000-0000-0000-000000000000}
EntityType = DRIVE_ENTITY_TYPE
EntityGuid = {00000000-0000-0000-0000-000000000000}
EntityName = ""
EntityFlags = 0x00000000
beserver: 12/18/06 12:25:48 12 AdammAdminBO::Query() - hr = 0x0
beserver: 12/18/06 12:25:48 12 AdammAdminBO::Get() - Parent = NULL , Entity = DRIVE
pvlsvr: 12/18/06 12:25:48 PvlEntityDatabase::QueryEntity()
ParentEntityType = NULL_ENTITY_TYPE
ParentEntityGuid = {00000000-0000-0000-0000-000000000000}
EntityType = DRIVE_ENTITY_TYPE
EntityGuid = {F29FDA30-E512-4FD3-893F-EA7575C9443E}
EntityName = ""
EntityFlags = 0x00000000
beserver: 12/18/06 12:25:48 12 AdammAdminBO::Get() - hr = 0x0
beserver: 12/18/06 12:25:49 -1 UtilityJobThread - status
beserver: 12/18/06 12:25:49 -1 UtilityJobThread - EndJob:canceled
beserver: 12/18/06 12:25:49 17 JobManager::HandleEndJob() called
beserver: 12/18/06 12:25:49 -1 UtilityJobThread - end
beserver: 12/18/06 12:25:49 -1 ActiveState::doEndEvent( :( 'Inventory Drive 00002'
pvlsvr: 12/18/06 12:25:49 AdammSession::Release()
Session = {870712A9-478E-4CC1-849C-FAE585E502BD}
beserver: 12/18/06 12:25:49 17 JobManager::DoJobCompletionTasks(Inventory Drive 00002): GetFinalJobStatus()=1
beserver: 12/18/06 12:25:49 17 JobManager::DoJobCompletionTasks() Handling normal JOB_STATE_ERROR
beserver: 12/18/06 12:25:49 17 JobManager::DoJobCompletionTasks() Creating canceled job alert
beserver: 12/18/06 12:25:49 18 Alert Job Cancellation, Notify: No, EventLog: Yes, Trap: No
beserver: 12/18/06 12:25:49 17 JobManager: Flagging 'Inventory Drive 00002' for deletion
beserver: 12/18/06 12:25:49 -1 ActiveState::doEndEvent( :( CJobManager::DoJobCompletionTasks() returned 0x0
beserver: 12/18/06 12:25:49 -1 Registered virtual array rowset(11): Client:SR0003DJL, Type:MD_OBJTYPE_JOBHISTORYVIEW
beserver: 12/18/06 12:25:49 17 CJobManagerBO::Query QUERY_JOBSETUP_MONITOR


I've tried finding out as much as I could on these forums and on the Net in general Im sure Ive tried just about everything! PLEASE HELP! :(
6 REPLIES 6

Chris_Campbell
Level 2
Anybody got any ideas, i thought Veritas/Symantec support guys assist here also?

Anybody got any suggestions on obtaining support from Veritas/Symantec for this product? Surely you don't have to 'buy' a support contract! To get support from these guys? What happened to the friendly telephone support or even email! Surely something like that is available?!

Chris_Campbell
Level 2
Ok, going to order a separate Single Channel SCSI Controller and stick the Tape Drive on that. Need to eliminate the system board SCSI. Still anybody got any suggestions?

shweta_rege
Level 6
Hello,




Please check,whether the device that you are using is there in our Hardware Compatibility List.
Kindly refer the following document for the same:

Symantec Backup Exec for Windows Servers (tm) 10d (10.1) Hardware Compatibility List. Includes HCL information for supported drives, libraries, virtual tape devices, fibre-channel HBAs, switches, routers/bridges, and iSCSI components. For printing purposes, the latest version of Acrobat is recommended.

http://support.veritas.com/docs/281670

If the Device is tested,then install the Veritas Drivers.



-- Kindly change Scsi id of the Medium changer to SCSI id 2 and the drive to SCSI id 3.

-- Stop "Removable storage" service and change startup type to manual.



Thank You,

Shweta

Chris_Campbell
Level 2
Hi Shweta,

Thanks for your standard reply. I already checked the Hardware Compatibility list for this device, its compatible. Device works perfectly in another Server, so its tested ok.

-- Kindly change Scsi id of the Medium changer to SCSI id 2 and the drive to SCSI id 3.

Im guessing what your referring to in the above is an Autoloader of some description?? The device I have is just a single Internal DAT72 Drive in a 5" bay.

Removable storage is already set to Manual.

So that left two options.... Backup Exec, as the Drive was detected by Windows and Backup Exec, but refused to function correctly. Or the On-board SCSI controller of the Proliant ML350......

So i refused to wait any longer, after a 200 Mile round trip, and lucky for Symantec/Veritas the fault has appeared to be with the one of the on-board SCSI controller channels.

Bizarre as the problem may seem though because the Device was detected in Backup Exec, and Backup Exec showed no problems with the Drive or what it was Attached too!!! Anyway..... suppose that would a discussion for another day!

Maybe you could explain to me Shweta why it takes so long for a Symantec Employee to reply to my Thread with such a Standard reply? And also why it costs to obtain support for such a Product? What happened to the email support or the telephone support or even just the good old Veritas!

I await your response,

Thanks and Regards,

Chris

Rob_Pelletier
Level 4
I sympathize.

I won't recommend BackupExec any more - it's not worth the trouble. And don't worry about not getting free support: even when you do pay them, they are still often unable to help. All they want to do is tell you to change hardware - the drive, cable, SCSI card, etc etc. (And quite often, they are right - it is often hardware.)

Frankly, you'll get more useful information from other users who read this forum than you will from Veritas (Symantec). Let's face it - the software manufacturer knows more about using their product in ideal (or test lab) conditions. Other users are in the real world, and are more likely to provide useful advice.

I am fighting a similar problem right now, with an HP changer - one device that holds 6 tapes. Everything's in the HCL, and I have replaced it all so far EXCEPT the changer itself, and a replacement is on the way. I'm getting 33152 events. Backups often run, then start providing events 33152 during the verify.

I did the same as you: double-checked the SCSI adaptor BIOS settings; checked SCSI card firmware and drivers; upgraded BE 10d to SP2; installed the latest Veritas drivers; rebuilt the BackupExec database; pulled some more hair out, etc etc.

If you want some free support, call HP. They have intelligent, helpful support personnel who would rather ship a replacement unit than hold up your client any longer than is necessary. Be careful they don't just have you run their LT&T software and use it to "prove" the drive is alright - you may have to remind them that you didn't buy the drive to run diagnostic software: you bought it to do backups!

Wish I could be more help - all I can really do is let you know you're not alone. Since this software is so touchy, I am considering using Windows Backup from now on, or an imaging product like Acronis.

Mike_Wild
Level 3
Just to add to the fun... I'm seeing the exact same types of errors as the two of you. I have
 
(1) VXA320 1U x10 Exabyte autoloader (current firmware)
(1) installed VXA3 packet loader (current firmware)
BU Exec 11D (all current patches / fixes)
Adaptec 39160 Dual channel scsi cont (also with updated / current driver / firmware)
Dell PowerEdge 1900 / Win 2K3 Svr R-2
 
Have heard that dual-channel cards can cause this types of time outs and device failures... possible, but not probable. Have also considered the following (which you guys may or may not have thought of all ready):
 
Removable storage service: Unless you're using native NT B/U, this needs to be stopped and disabled
Bad media
Improper termination and/or scsi ID(s) (some devicess like to have a certain ID to work properly)
Bar code labels (loader-only concern here, obviously): when not using bar code lables, the loader reads each slot up to 10 times before determining that there's no barcode label on the resident tape (amazing... 10 times!! talk about overkill). Anyway, you can experience a scsi timeout because of this.
 
bottom line - I'm getting much better and more effective support from the HW mfg than I ever get from Symantec. So once I eliminate the drive, controller, and loader as being the culprit... I'm going to be looking for a better software solution. I don't know what I was thinking when I bought BU Exec for this... oh yes I do, I was thinking that I needed something cheap. That's where the problem started.
 
-M. Wild

Message Edited by Mike_Wild on 08-27-200701:20 PM