HPE EVA Storage

EVA disk group best practice

 
SOLVED
Go to solution
zeno75
Occasional Contributor

EVA disk group best practice

We've have some performance issues with our EVA, based on the HP best practice document it recommends to have as many disks in a single disk group which we have done and on it were running VMware, SQL and the ocupancy is 128 disks with 95% capacity utilization.

 

What we've found is frequently were getting some high disk latency on the VMware datastores and also SQL get timeout errors. Due to disk requirements we've purchased some new disks and need to deceide to create a new DG or add the disks to the existing DG.

 

Given the current circumstances can anyone provide some suggestions - the vendor recommended we create a new DG with the 60+ disks b/c we won't get much performance gain by having the extra disks in the current DG.

 

Secondly whats the best practice in adding disks to an existing DG eg. if we have a DG with 100+ disks and we need to add another 60 new, do we add the disks one at a time or all 60 to the DG at once.

 

Cheers

5 REPLIES 5
Johan Guldmyr
Honored Contributor

Re: EVA disk group best practice

How many disks do you have at the moment? ( EVAs like the number of disks to be divisible by 8)

Which EVA model do you have?

HP support has a nice performance analysis tool. There is also apparently also something similar in CV these days. Perhaps this is something you could use - to create a baseline of your current performance and after you have added the new disks you could then see if there are improvements or not.

Why wouldn't adding disks to a DG help?

I suppose one benefit of creating a new disk group is that you could dedicate those disks to the services or servers that have vdisks in that disk group.

One quite common thing when it comes to EVA performance is to have the controllers unevenly utilized. evaperf can help with monitoring this. And the solution is to spread the vdisks between the controllers.
zeno75
Occasional Contributor

Re: EVA disk group best practice

We were told by the SI with documentation from HP that there's a diminishing return on performance once you get past 120 disks in the DG right now were at 120, and increasing the 60 or so disks we only get much improvement in performance.

 

We are alos reviewing the balacing of vDisks between the SP's.

 

One side question were using Window 2008 R2 and I with MPIO and the HP DSM - however I'm trying to find information on what I should configured for the "Preferred Path/Mode" on the EVA. For Vmware we have "Path X/Failover/Failback" but for Win2k8 R2 I can't seem to find any documentation on whats the best configuration.

Johan Guldmyr
Honored Contributor

Re: EVA disk group best practice

If you don't have Failback, then if for some reason the vdisks are moved to another controller you'll have to divide the vdisks again.

zeno75
Occasional Contributor
Solution

Re: EVA disk group best practice

So does that mean we should be using "Failover/Failback" configuration? Johan

Johan Guldmyr
Honored Contributor

Re: EVA disk group best practice

As far as I know Windows don't mind if the path to a LUN changes back and forth.

Other OS might be different.