GreenLake Administration
- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- MSA Storage
- >
- MSA 500 G2
MSA Storage
1850754
Members
4937
Online
104055
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
back
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
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
03-22-2005 08:45 AM
03-22-2005 08:45 AM
MSA 500 G2
We use two of these with two Proliant servers. They each house a number of databases that together are around 200Gb. We were getting data corruption even though we had the write cache set at %0 and read cache set at %100. MS SQL server suffers from database corruption if write caching is enabled. Write caching controllers and disk subsystems are safe for SQL Server, if they are specifically designed for use in a data critical transactional database management system (DBMS) environment.
We had corruption even though we had write at %0. Come to find out the Modular Smart Array 500 G2 contoller had what is called Array Accelerator. This "Logical Drive Array Accelerator" was the root of our problem. We disabled it and have had no more occurances of data corruption.
I would think the MSA 500 G2 is a commom database storage solution, but I cannot fathom why HP would include a setting that, at least for us, caused data corruption in our databases. Is the MSA 500 G2 designed for use in a data critical transactional database management system (DBMS) environment.
We had corruption even though we had write at %0. Come to find out the Modular Smart Array 500 G2 contoller had what is called Array Accelerator. This "Logical Drive Array Accelerator" was the root of our problem. We disabled it and have had no more occurances of data corruption.
I would think the MSA 500 G2 is a commom database storage solution, but I cannot fathom why HP would include a setting that, at least for us, caused data corruption in our databases. Is the MSA 500 G2 designed for use in a data critical transactional database management system (DBMS) environment.
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
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP