Storage Boards Cleanup
To make it easier to find information about HPE Storage products and solutions, we are doing spring cleaning. This includes consolidation of some older boards, and a simpler structure that more accurately reflects how people use HPE Storage.
Disk Arrays
Showing results for 
Search instead for 
Did you mean: 

EVA4000: Disk Sub System

Go to solution
Arman Obosyan
Frequent Advisor

EVA4000: Disk Sub System

We have two EVA sites, with two HSV200 controllers and one disk enclosure (12x146Gb) each site.

Q1: Is there any estimation for performance difference between sync. and async. write modes for the DR Group.

Q2: Is there any way to priorities disk traffic for different applications, connected to EVA? i.e. we have core banking system DB (Oracle), also file server for Terminal Server farm, also MS Exchange mailstore/logfiles. Let's say we connect them all to EVA. We don't want that exchange peak performance will cause lag for corebanking system. How we can avoid this? Or this is to be done by splitting disk array into different disk groups, and separate mission critical application with it's own disk groups?

Q3: Can one disk group contains disk from different disk enclosures? What is the limit of disk/enclosures quantity for one disk group?
Ivan Ferreira
Honored Contributor

Re: EVA4000: Disk Sub System

Hello Arman:

Q1: The performance will vary depending of the I/O rate, the distancy, the link and the bandwidht. For very fast links at small distances, the performance will not suffer. There is a document that may help you "hp StorageWorks continuous access EVA replication performance estimator V1.1". See the eva documentation site.

Q2: Normally, EVAs are capable of handle large I/O because of the virtutalization technology. You cannot specify a priority for the disks. The disk group separation could help if you separate random from sequential access I/O patterns into different disk groups, but normally, when more disk on the disk groups, the better the performance. You should do performance test on your own environment.

Q3: A disk group can contain all disks from all disk enclosures supported by the EVA with a minimum of 8.
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Mark Poeschl_2
Honored Contributor

Re: EVA4000: Disk Sub System

Q1: Almost entirely dependent on the nature and latency of your WAN link between the sites.

Q2: There isn't a direct mechanism for prioritizing one server's access to an EVA over another's. So one might consider creating a separate disk group for "special" applications, but with only 12 spindles you don't have a choice. The minimum size for a disk group is 8 spindles so you don't have enough for two. Even if you had the necessary 16 spindles, creating two disk groups of 8 would really be shooting yourself in the foot for reasons of both performance and capacity. More spindles per disk group / fewer disk groups is nearly always the best answer when setting up an EVA.

Q3: Yes - a disk group can contain disks from multiple enclosures. For an EVA4000 the maximum is 4 enclosures with a total of 56 spindles in a single disk group.
Arman Obosyan
Frequent Advisor

Re: EVA4000: Disk Sub System