- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: LVM Layout for Oracle under SAN EVA 5000
Operating System - HP-UX
1752796
Members
6013
Online
108789
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
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
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
12-06-2005 10:47 PM
12-06-2005 10:47 PM
Re: LVM Layout for Oracle under SAN EVA 5000
Simon, just a few quick things that I don't think anyone has mentioned yet:
. old strategies about striping and spreading loads over different LUNs generally do not work on the EVA because of the virtualization that it does
. when creating disk groups, keep in mind that the more disks you have in a single group, the more IO requests per second that group can service
. thus, more disk in a single group = higher performance
. for better protection they recommend that your data and your logs reside in different disk groups... if one disk group goes to hell, you might still have the other with good data on it
. try to spread your disk group(s) vertically - across all the disk shelves
. do read the best practices docs; you can find them by going to www.hp.com/go/eva5000 and clicking on the "Technical docs" link on the right side
. if you'll be doing large data loads, and feel like taking risks, you can disable the write cache mirroring feature - it will boost your IOs per second... remember to turn it back on after the data load is done
. when defining LUNs, set the "preferred path" through the "Command View" software but keep in mind what others have said about the caching and load balancing
. finally, it is VERY IMPORTANT to make sure that you have the latest EVA controller firmware (aka VCS code); you want at least 3.028
Hope that helps!
. old strategies about striping and spreading loads over different LUNs generally do not work on the EVA because of the virtualization that it does
. when creating disk groups, keep in mind that the more disks you have in a single group, the more IO requests per second that group can service
. thus, more disk in a single group = higher performance
. for better protection they recommend that your data and your logs reside in different disk groups... if one disk group goes to hell, you might still have the other with good data on it
. try to spread your disk group(s) vertically - across all the disk shelves
. do read the best practices docs; you can find them by going to www.hp.com/go/eva5000 and clicking on the "Technical docs" link on the right side
. if you'll be doing large data loads, and feel like taking risks, you can disable the write cache mirroring feature - it will boost your IOs per second... remember to turn it back on after the data load is done
. when defining LUNs, set the "preferred path" through the "Command View" software but keep in mind what others have said about the caching and load balancing
. finally, it is VERY IMPORTANT to make sure that you have the latest EVA controller firmware (aka VCS code); you want at least 3.028
Hope that helps!
- « 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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP