HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Backup, Copy, RMS Errors (OpenVMS 7.3-2)
Operating System - OpenVMS
1828374
Members
3125
Online
109976
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
Forums
Discussions
Discussions
Discussions
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
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
09-29-2010 08:22 PM
09-29-2010 08:22 PM
Re: Backup, Copy, RMS Errors (OpenVMS 7.3-2)
Hein,
Definitely do not want to muddy any waters.
After re reading this post, my case doesn't apply. I have to confirm, it but I think my issue was that the container file was not set /nocache.
As to the problem in this post...
From what I know OpenVMS tends to be rather robust as far as error detection goes.
It it was a hardware error in the disk subsystem, you think that the copy command would exhibit errors as well. The disk subsystem does not know whether backup or copy command was doing the IO.
I'm assuming that the firmware on the MSA1000 is at the latest version. Also that all the connections profiles on the MSA1000 are set to OpenVMS. We had issues on system after we replaced a Fibre Channel HBA on a node but forgot to update the connection profile to OpenVMS.
If the MSA1000 is not active/active, then
it could have been an issue with the MSA1000 controller and when the system rebooted it forced a switch of the FC path over to the other MSA1000 controller.
If the MSA1000 is active/active then we have to look at the system. It is not clear that this test was done from both systems in the cluster. If both systems show the same issue then it is not hardware related to any one system.
If you still had the BACKUP-FILE it would be interesting to dump the file around the errors to see what is written compared to what is supposed to be there. Is the data random? Is it zero? Is it similar to other data in the file? I would look if the errors occur at where the file is fragmented.
Do the EA40s have Elsa Gloria graphics cards? If so see. http://forums13.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1285819675885+28353475&threadId=1251038
Definitely do not want to muddy any waters.
After re reading this post, my case doesn't apply. I have to confirm, it but I think my issue was that the container file was not set /nocache.
As to the problem in this post...
From what I know OpenVMS tends to be rather robust as far as error detection goes.
It it was a hardware error in the disk subsystem, you think that the copy command would exhibit errors as well. The disk subsystem does not know whether backup or copy command was doing the IO.
I'm assuming that the firmware on the MSA1000 is at the latest version. Also that all the connections profiles on the MSA1000 are set to OpenVMS. We had issues on system after we replaced a Fibre Channel HBA on a node but forgot to update the connection profile to OpenVMS.
If the MSA1000 is not active/active, then
it could have been an issue with the MSA1000 controller and when the system rebooted it forced a switch of the FC path over to the other MSA1000 controller.
If the MSA1000 is active/active then we have to look at the system. It is not clear that this test was done from both systems in the cluster. If both systems show the same issue then it is not hardware related to any one system.
If you still had the BACKUP-FILE it would be interesting to dump the file around the errors to see what is written compared to what is supposed to be there. Is the data random? Is it zero? Is it similar to other data in the file? I would look if the errors occur at where the file is fragmented.
Do the EA40s have Elsa Gloria graphics cards? If so see. http://forums13.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1285819675885+28353475&threadId=1251038
- « Previous
-
- 1
- 2
- 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.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP