- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Problem with replacement LTO4 tapedrive.
Operating System - OpenVMS
1753411
Members
7215
Online
108793
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
тАО05-09-2010 07:33 PM
тАО05-09-2010 07:33 PM
Re: Problem with replacement LTO4 tapedrive.
Hi,
After replacing LTO4 tapedrive in a MSL4048 library did you execute below commands?
MC sysman io list
MC sysman io find
MC sysman io Auto
OR
Mc sysman io replace /WWID
Regards,
Ketan
After replacing LTO4 tapedrive in a MSL4048 library did you execute below commands?
MC sysman io list
MC sysman io find
MC sysman io Auto
OR
Mc sysman io replace /WWID
Regards,
Ketan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-10-2010 04:49 AM
тАО05-10-2010 04:49 AM
Re: Problem with replacement LTO4 tapedrive.
Hi Brit,
The problem of hang when performing a tape backup can also happen
because of a faulty SCSI terminator.
Check the following link -
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1426068
Here also a similar kind of problem was seen, wherein the backups hang
for a long period of time after which it had to be manually aborted.
Regards,
Murali
The problem of hang when performing a tape backup can also happen
because of a faulty SCSI terminator.
Check the following link -
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1426068
Here also a similar kind of problem was seen, wherein the backups hang
for a long period of time after which it had to be manually aborted.
Regards,
Murali
Let There Be Rock - AC/DC
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-11-2010 05:18 AM
тАО05-11-2010 05:18 AM
Re: Problem with replacement LTO4 tapedrive.
First I would like to thank you all for your suggestions and assistance over the weekend.
I have not found a clear explanation for the cause of my original post (sad to say), but on the semi-good side, the problem may have gone away.
Summary of yesterday.
Arrived to find the library in the same state as Saturday, that is, Error LED On, Attention LED flashing, Clean LED On.
Steps performed.
1. Unloaded the Drive
2. Power Cycled the Library (Error LED now Out)
3. Run cleaning tape (Clean LED now Out)(Note:: this is second clean in 2 days, without a successful backup in between)
Attention LED is still flashing, and Library Status shows (!). Checked all of the slots and found one cassette with the (!) alongside. Removed this cassette from the Library and discarded.
Attention LED now Out, and Library status is good.
Incidentally, the cassette that I removed was one of those being used for testing over the weekend, and may have been the cause of many of the "Parity" and other errors. In retrospect, the "scratch" tapes which are kept in reserved slots in the library, and are used for automatic recovery when a "severe error" occurs in the backup job, have been in the library for close to 2 years. While the lifetime for tape media should be longer than that (5 years I believe), the age of the tapes may have been a contributing factor.
At ~9am yesterday I submitted a test of the failing backup, using this problem drive (Drive 1, MGA5), and it ran successfully to completion. In addition, the normally scheduled backup ran last night without any problems.
I am not totally conviced that I am off the hook yet, I will need a couple of days of success before I start to relax. The main problem being that I do not have a clear picture of what caused my problem, or what caused it to go away. I expect that I will have to just except the situation and move-on.
I just wish I had an explanation for the initial hang which occurred on Friday evening.
Oh Well!
Thanks again for your help.
Dave.
I have not found a clear explanation for the cause of my original post (sad to say), but on the semi-good side, the problem may have gone away.
Summary of yesterday.
Arrived to find the library in the same state as Saturday, that is, Error LED On, Attention LED flashing, Clean LED On.
Steps performed.
1. Unloaded the Drive
2. Power Cycled the Library (Error LED now Out)
3. Run cleaning tape (Clean LED now Out)(Note:: this is second clean in 2 days, without a successful backup in between)
Attention LED is still flashing, and Library Status shows (!). Checked all of the slots and found one cassette with the (!) alongside. Removed this cassette from the Library and discarded.
Attention LED now Out, and Library status is good.
Incidentally, the cassette that I removed was one of those being used for testing over the weekend, and may have been the cause of many of the "Parity" and other errors. In retrospect, the "scratch" tapes which are kept in reserved slots in the library, and are used for automatic recovery when a "severe error" occurs in the backup job, have been in the library for close to 2 years. While the lifetime for tape media should be longer than that (5 years I believe), the age of the tapes may have been a contributing factor.
At ~9am yesterday I submitted a test of the failing backup, using this problem drive (Drive 1, MGA5), and it ran successfully to completion. In addition, the normally scheduled backup ran last night without any problems.
I am not totally conviced that I am off the hook yet, I will need a couple of days of success before I start to relax. The main problem being that I do not have a clear picture of what caused my problem, or what caused it to go away. I expect that I will have to just except the situation and move-on.
I just wish I had an explanation for the initial hang which occurred on Friday evening.
Oh Well!
Thanks again for your help.
Dave.
- « Previous
- Next »
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