12-22-2010 03:09 AM
Hi,
We have had our Quantum Scalar i40 library setup for around two weeks now but have encountered problems getting scheduled jobs to run and getting the library to perform tasks through Backup Exec 2010 and 2010 R2.
We have the library connected to a Dell PowerEdge 1950 server running server 2003, via SAS cable, and have a single half height HP SAS LTO-4 drive in the Quantum.
The library shows in Backup Exec as Quantum001 and the HP tape drive HP001 plus Slots are beneath it.
When a tape is imported via the library's interface, and we run a scan then inventory and start a job off it runs without issue, but once the job has run it seems that the device becomes pretty much unusable until it is rebooted.
As a typical example of what happens.....
The error messages which we get when the drive goes offline are either....
# The drive hardware is offline, Please confirm that the drive hardware is powered on and properly cabled. ID 58053
# [job name] - The job failed with the following error: Physical Volume Library Drive not available. ID 34113
# Robotic library hardware error - The robotic library has reported a general hardware error condition... ID 58053
We were able to install the Symantec drivers for the HP tape drive, but the Quantum device was not detected when running tapeinst.exe, i've done much searching on these and other forums and found that setting the library to Unknown Medium Changer should work. So currently it's set to that.
The SCSI information for each is HP Drive Port: 3 Bus: 0 Target ID: 45 LUN: 0 and library Port: 3 Bus: 0 Target ID: 45 LUN: 1.
Which ties in with what i've read about having the drive on a lower LUN than the library.
When we first configured the library it was using BE 2010, but we have since upgraded to 2010 R2 and the results are exactly the same.
Does anyone have experience of a similar problem or any advice on things we could try.
If we reboot the library with the BE services stopped then the library works and we can import a tape, and perform a backup job with no problems at all, but once a job has run Backup Exec seems unable to perfrom any tasks, be it inventory, initialize, scan or unlock.
Any help will be greatly appreciated, thanks.
Paul.
Solved! Go to Solution.
01-11-2011 03:35 AM
I installed a new HBA yesterday alongside our existing one.
Rather than using the DELL PERC 6/E RAID enabled card we are now using the DELL SAS 5/E HBA with no RAID support and no other devices. Ran a manual job yesterday and that was fine, scheduled job ran fine last night too.
Looks like this can be closed, thanks for your help Gurvinder and Amol ;)
12-22-2010 03:14 AM
Hi Paul
Open BEutility.exe and check the status of the server if its "Paused" or "Running"
BEutility is located at X:\Program Files\Symantec\Backup Exec.
Also check Windows system log for any error message.
Make sure the library and the tape device is reflecting in the Windows device manager.
12-22-2010 03:27 AM
..for the quick response,
BEUtil shows the server is running, and Windows event logs only show the three listed errors either with either 34113 or 58053 IDs all in the application log.
In device manger the devices all show fine..
Unknown Medium Changer (have also tried using Quantum supplied drivers)
DELL PERC 6/E Adapter RAID Controller
HP Ultrium 4-SCSI SCSI Sequential Device
thanks again, Paul.
12-22-2010 03:35 AM
Paul, check the web console of the library I guess tape is stucked in the drive.
EDIT: Please post the description of event id 58053.
12-22-2010 03:52 AM
Yes, that's right the web interface (and operation panel) both refuse to allow the tape to be removed from the drive.
Once that happens the only solution is to stop the services in Backup Exec and reboot the library. After we do that everything works OK for a while, until a job completes and then same problem again.
These are the two errors the first happens after a job fails when i try to attempt an inventory etc. The second error appears when the scheduled job fails.
------------------------
12-22-2010 03:55 AM
Paul the issue seems to be with the medium changer, I guess you will have to contact
hardware vendor to fix it.
12-22-2010 03:58 AM
Ok, thanks for the advice Amol.
If anyone else has any other suggestions then please feel free to contribute, but i'll get in touch with the vendor for some advice.
Thanks again.
12-23-2010 05:52 AM
Just to bump this thread.... i pulled the following from my adamm.log file earlier, currently waiting for Quantum to get back to me on the issue, but does anyone know what this error suggests?
12-23-2010 06:22 AM
Follow this Hardware Troubleshooting TechNote step by step :-
www.symantec.com/docs/TECH24414
Also check "Support Policy for Host-Bus-Adapter that feature RAID"
www.symantec.com/docs/TECH70907
Somethings that you can check :-
- Does the front panel for RL report any errors
- Check for any Tape jams
- Make sure Tape Library is set to automatic or random
- Make sure RL is supported as per SCL
- Medium Changer and Drive have latest drivers
Test with OEM and Symantec Drivers
-- Check events in event viewer (system logs)
-- You can also run tracer.exe while running the Job. Export the log as text
and look for scsi errors
12-23-2010 07:17 AM
12-23-2010 11:31 PM
keeps us posted..thanks
01-06-2011 02:03 AM
Just to update anyone reading this thread i found a possible solution to my issue.
After installing Dell OpenManage server adminisatrator on the server i had a look to see if there were any settings to adjust on my HBA, and it highlighted the fact that the Storport Driver Version for Windows 2003 was below the supported version of the OpenManage software.
I updated this with a hotfix from Microsoft to 5.2.3790.4173 and things do seem to be working better, the drive has only gone offline once in the last two days and i have been using the drive \ library a lot in that time.
I'm still waiting for delivery of a Dell non-RAID SAS 5/E card to install alongside the PERC 6/E for the library to connect but for now it does seem at least that this works.
01-11-2011 03:35 AM
I installed a new HBA yesterday alongside our existing one.
Rather than using the DELL PERC 6/E RAID enabled card we are now using the DELL SAS 5/E HBA with no RAID support and no other devices. Ran a manual job yesterday and that was fine, scheduled job ran fine last night too.
Looks like this can be closed, thanks for your help Gurvinder and Amol ;)
01-11-2011 03:43 AM
Cheers!!!