- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- Re: SCSI error when running L&TT on an StorageWork...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-22-2006 11:32 PM
тАО01-22-2006 11:32 PM
SCSI error when running L&TT on an StorageWorks autoloader.
The current SCSI configuration is likely to be limiting the performance of the drive.
|__ Please check that your HBA is the correct type for the drive and that the cabling is good.
|__ The SCSI configuration referenced is the one for which device analysis was run and/or the support ticket was pulled.
|__ If this is not via your backup server then you may not have an issue.
|__ The drives hardware compression algorithm is currently switched off.
|__ This was probably set by the backup software.
|__ The drive's setup has not been altered.
|__ Current SCSI transfer rate limited to: 160 MB/sec. Recommended: 320 MB/sec. or better
Anyone has any idea about whatтАЩs wrong ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-22-2006 11:42 PM
тАО01-22-2006 11:42 PM
Re: SCSI error when running L&TT on an StorageWorks autoloader.
"Current SCSI transfer rate limited to: 160 MB/sec. Recommended: 320 MB/sec. or better"
Your servers SCSI card seems to be too slow.
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-22-2006 11:48 PM
тАО01-22-2006 11:48 PM
Re: SCSI error when running L&TT on an StorageWorks autoloader.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-23-2006 12:37 AM
тАО01-23-2006 12:37 AM
Re: SCSI error when running L&TT on an StorageWorks autoloader.
One or two ideas.
Did you check the SCSI interface bios config ?
Switch the hardware compression on the drive to ON ( either by hardware or by software ).
Rgds
Alexander M. Ermes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-23-2006 12:46 AM
тАО01-23-2006 12:46 AM
Re: SCSI error when running L&TT on an StorageWorks autoloader.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-23-2006 01:30 AM
тАО01-23-2006 01:30 AM
Re: SCSI error when running L&TT on an StorageWorks autoloader.
If you are using windows, you can go to the device manager, locate your drive, open the drive properties page and click the config tab. Here you can enable/disable the compression.
But how about the scsi connection? Is the lib the only device on your SCSI controller?
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-23-2006 01:38 AM
тАО01-23-2006 01:38 AM
Re: SCSI error when running L&TT on an StorageWorks autoloader.
There are also an Event error in the system log. Event ID 11, The driver detected a controller error on \Device\Scsi\Symmpi1.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-23-2006 04:47 AM
тАО01-23-2006 04:47 AM
Re: SCSI error when running L&TT on an StorageWorks autoloader.
See: http://www.hp.com/products1/storage/compatibility/tapebackup/ThirdParty/index.html
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=lpg50063
2)Algorithm... HP tape drives have self compression. They typcially get 2:1 compression and I have seen 2.5:1 compression occassionally. Veritas Back Up Exec most often disables our drives algorithm in regards to compression. This happens when your back up software has a setting for compression. Compression should be 'un-selected'... no setting made in back up software, for this algorithm to prevent being disabled and for you to get the best compression ratios. Typically I have seen software get 1:1 to 1.7:1 compression.
My suggestion is to turn off your compression setting in your back up software... and run the test again to see if the algorithm is still turned off. Sometimes LTT will detect this and ask if you want to re-enable this now. If this does not recover the algorithm, you might have to flash the firmware to get this recovered so the algorithm will work again.
3)Ignore: "If this is not via your backup server then you may not have an issue.", if you are testing this unit from the local computer.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-23-2006 05:46 AM
тАО01-23-2006 05:46 AM
Re: SCSI error when running L&TT on an StorageWorks autoloader.
If you have anything else on the scsi bus this will limit the LTO transfer rate.
Ultrium units will automatically slow themselves to match the slowest unit on the scsi bus... so separate scsi controllers for each scsi unit is always recommended.
However, this might have been changed in the scsi bios. Check on post for your scsi bios prompt. Check if there is a way to "change/view host bus adapter settings"... then change the sync transfer rate on the card's ID (default #7) and the device's ID to 320 (that is 320 mb/s).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-24-2006 08:38 AM
тАО01-24-2006 08:38 AM
Re: SCSI error when running L&TT on an StorageWorks autoloader.
The HBA you are using is fine.
While the recommendation is 320 MB/sec I wouldn't be too concerned about a negotiated rate of 160MB/sec since that is unlikely to impact your performance. At 2:1 compression the drive runs at 160MB/sec. If you get better than 2:1 you will lose a little performance but most hosts can't actually drive that speed.
There are a few possibilities for why your system hasn't negotiated for 320 MB/sec.
- Bus length/capacitance/other is causing errors at 320 MB/sec so the HBA automatically dropped back to 160MB/sec
- The HBA driver is old. There was a driver update several months ago to fix a negotiation issue that occured in some specific configurations.
- You might have encountered a corner case where the negotiations didn't complete correctly. A firmware roll will be available in the near future to correct that issue.