HPE GreenLake Administration
- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- MSA1000 A/A performance worse than A/S (VMS BACKU...
HPE EVA Storage
1826287
Members
3926
Online
109692
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-14-2008 07:13 PM
09-14-2008 07:13 PM
MSA1000 A/A performance worse than A/S (VMS BACKUP)
Hi all. After upgrading our MSA1000s from A/S (4.48) to A/A (7.0) we have noticed a significant performance decrease when doing backups. Other I/O seems about the same or better.
VMS BACKUP bypasses the VMS file cache so it has a greater reliance on the controller cache than normal I/O.
I suspect that going to A/A reduced the amount of READ and READ AHEAD cache available for an individual LUN. I assume in A/A all the cache is shared which means each controller only gets to use half of it. The other half is hidden. The total amount cache available is the same but per LUN it is reduced. Is the correct?
Anyone seen VMS backup performance drop off with A/A? Any work-arounds? Can I configure 7.0 as A/S?
Tim
VMS BACKUP bypasses the VMS file cache so it has a greater reliance on the controller cache than normal I/O.
I suspect that going to A/A reduced the amount of READ and READ AHEAD cache available for an individual LUN. I assume in A/A all the cache is shared which means each controller only gets to use half of it. The other half is hidden. The total amount cache available is the same but per LUN it is reduced. Is the correct?
Anyone seen VMS backup performance drop off with A/A? Any work-arounds? Can I configure 7.0 as A/S?
Tim
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