- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- setting up new eva6400 .need suggestion
HPE EVA Storage
1752437
Members
5716
Online
108788
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
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
04-12-2011 07:37 PM
04-12-2011 07:37 PM
setting up new eva6400 .need suggestion
Hi all,
I need to setup EVA6400 with RHEL 5.6 .I need to create a single file system of 2 TB size .This file system is going to be 40% read and 60% write .It will be random read/write .
I am looking for your thoughts in order to get the maximum performance
1) What is the recommended vdisk size?
2) Will it be good idea to use the LVM striping on top of Vraid1 disk? If yes what are the recommended strip size and number of disk in the strip.
As per EVA best practice doc, it was advised that if the vdisk is owned by different controller, then it be advised to go with striping by using the volume manager.
3) How many disk path we can use per LUN for the optimum performance .with EVA 6400 we can have maximum of 8 Path per Lun (4 path per controller) ?
Will there be advantage of 8 path over 4 path ?
I am planning to create 100 GB of vidsk (vdisk1) and going to use LVM striping with -i 2 -I 4096.
Looking for your valuable suggestion.
Thanks
I need to setup EVA6400 with RHEL 5.6 .I need to create a single file system of 2 TB size .This file system is going to be 40% read and 60% write .It will be random read/write .
I am looking for your thoughts in order to get the maximum performance
1) What is the recommended vdisk size?
2) Will it be good idea to use the LVM striping on top of Vraid1 disk? If yes what are the recommended strip size and number of disk in the strip.
As per EVA best practice doc, it was advised that if the vdisk is owned by different controller, then it be advised to go with striping by using the volume manager.
3) How many disk path we can use per LUN for the optimum performance .with EVA 6400 we can have maximum of 8 Path per Lun (4 path per controller) ?
Will there be advantage of 8 path over 4 path ?
I am planning to create 100 GB of vidsk (vdisk1) and going to use LVM striping with -i 2 -I 4096.
Looking for your valuable suggestion.
Thanks
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2011 08:58 PM
04-12-2011 08:58 PM
Re: setting up new eva6400 .need suggestion
Hi!
Some thing to consider:
On the EVA the data is levelled/spread out between all the disks in the disk group automagically by the controllers. Basically: the more physical disks you have in a disk group - the more performance.
If you access a vdisk/LUN from the non-owning controller, the non-owning will have to pass the request to the owning controller anyway. It's recommended to use a multipathing that is ALUA sensitive.
Beware that (last time I checked anyway) - vdisks over 2TB could not be resized.
Some thing to consider:
On the EVA the data is levelled/spread out between all the disks in the disk group automagically by the controllers. Basically: the more physical disks you have in a disk group - the more performance.
If you access a vdisk/LUN from the non-owning controller, the non-owning will have to pass the request to the owning controller anyway. It's recommended to use a multipathing that is ALUA sensitive.
Beware that (last time I checked anyway) - vdisks over 2TB could not be resized.
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