- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- Re: Problem on HP Superstore E DLT 2/20
StoreEver Tape Storage
1748232
Members
3519
Online
108759
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО02-11-2003 02:08 AM
тАО02-11-2003 02:08 AM
Problem on HP Superstore E DLT 2/20
Every night we start 7 backup and
during the last 3 night we gave from only backup this error " Can not open device ([16] Device busy)".
we made these test:
mc -p /dev/rac/c9t0d0 -s S11 -d D2 (Operation OK)
mc -p /dev/rac/c9t0d0 -s D2 -d S11 (Operation OK)
mc -p /dev/rac/c9t0d0 -s S10 -d D2 (Operation OK)
mc -p /dev/rac/c9t0d0 -s D2 -d S10 (we received this output "ERROR: 0x0 No Sense : 0x0 No additional sense information"
during the last 3 night we gave from only backup this error " Can not open device ([16] Device busy)".
we made these test:
mc -p /dev/rac/c9t0d0 -s S11 -d D2 (Operation OK)
mc -p /dev/rac/c9t0d0 -s D2 -d S11 (Operation OK)
mc -p /dev/rac/c9t0d0 -s S10 -d D2 (Operation OK)
mc -p /dev/rac/c9t0d0 -s D2 -d S10 (we received this output "ERROR: 0x0 No Sense : 0x0 No additional sense information"
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-11-2003 04:40 PM
тАО02-11-2003 04:40 PM
Re: Problem on HP Superstore E DLT 2/20
This probably means that robot device times out. Why? Nobody knows until look to diagnostic output - so called support ticket - generated by HP LTT program http://www.hp.com/cposupport/information_storage/support_doc/lpg50128.html . Please generate support ticket, zip it and attach to your next reply
Eugeny
PS. Surestore, but Superstore sounds good too :o)
Eugeny
PS. Surestore, but Superstore sounds good too :o)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-11-2003 05:44 PM
тАО02-11-2003 05:44 PM
Re: Problem on HP Superstore E DLT 2/20
The error your receiving generally is given when a tape library is a "not ready" state. This can be a timeout issue or could even be that the tape library is doing an IPL.
Other than generate the support ticket as suggested, there are some other issues that you need to check on as well both from your HPUX server and your OmniBack cell manager.
OS Issues:
Disable the dm_stape monitor from EMS. I've attached a document on how to do this. This is to be done on each HPUX server.
Have the kenel parameter 'st_ats_enabled' set to '0' (zero)
These two issues deal with SCSI resets.
Omniback Issues:
Logical device locking. For each logical device that is used, the same lock name should be used for this. If this is not done, if a backup starts from logical drive 1 and logical drive two using the same physical drive, then both backups will attempt to start and give the error message your seeing.
Other than generate the support ticket as suggested, there are some other issues that you need to check on as well both from your HPUX server and your OmniBack cell manager.
OS Issues:
Disable the dm_stape monitor from EMS. I've attached a document on how to do this. This is to be done on each HPUX server.
Have the kenel parameter 'st_ats_enabled' set to '0' (zero)
These two issues deal with SCSI resets.
Omniback Issues:
Logical device locking. For each logical device that is used, the same lock name should be used for this. If this is not done, if a backup starts from logical drive 1 and logical drive two using the same physical drive, then both backups will attempt to start and give the error message your seeing.
Anyone for a Mutiny ?
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP