|
|
|
date: Tue, 16 May 2006 01:40:09 +0100,
group: microsoft.public.exchange.clustering
back
Re: IO on HDS 9585
For each virtual server, you need to define a requirement in terms of IOPS
and space. MS gives guidance on determining the IOPS requirements in
"Optimizing Storage Performance for Exchange Server 2003". The space
requirement will include the sum of the usable space of all volumes that
will reside on the SAN, as well as space that is use by the mirroring or
parity scheme, for snapshots or shadow copies, space for clones or BCVs,
etc. This is usually defined as Raw Space and Usable Space.The IOPS
requirement should have a response time tied to it. in Optimizing Storage,
poor performance is defined as average latency over 20ms and more than
occasional spikes lasting more than a few seconds over 50ms. 20ms is a good
response time starting target if you wish to aviod poor performance.
Once you have the requiremnt defined, the Storage architect will translate
that into a SAN architecture that support the requirement. From a
perfornace perspective, the most significant factor will be the spindle
count. Without knowing the specifics of the requirement and the design, it
is impossible to predict what the performance of the SAN will be like
irregardless of vendor or model.
"Tim Coveney" wrote in message
news:ugOONFIeGHA.2068@TK2MSFTNGP02.phx.gbl...
> Hi all,
>
> Would anyone have any real world figures on IO throughput on a 4-8 node
> cluster sharing drives on a HDS 9585 SAN they're willing to share?
>
> Will be talking to the manufacturers soon, just looking for some 'I've
> seen this' figures from people who've done it...
>
> Many thanks,
>
> Tim
>
> --
>
> Tim
> Llama IT
> This posting is provided in good faith, "as is" with no warranties, and
> confers no rights.
>
>
date: Mon, 15 May 2006 20:59:35 -0700
author: John Fullbright [MVP] fjohn@donotspamnetappdotcom
Re: IO on HDS 9585
Thanks John, but I know how to design Exchange storage, I just was looking
for any real world experience with this specific piece of kit. Thanks
anyway.
--
Tim
Llama IT
This posting is provided in good faith, "as is" with no warranties, and
confers no rights.
"John Fullbright [MVP]" <fjohn@donotspamnetappdotcom> wrote in message
news:OIoHn0JeGHA.4720@TK2MSFTNGP03.phx.gbl...
> For each virtual server, you need to define a requirement in terms of IOPS
> and space. MS gives guidance on determining the IOPS requirements in
> "Optimizing Storage Performance for Exchange Server 2003". The space
> requirement will include the sum of the usable space of all volumes that
> will reside on the SAN, as well as space that is use by the mirroring or
> parity scheme, for snapshots or shadow copies, space for clones or BCVs,
> etc. This is usually defined as Raw Space and Usable Space.The IOPS
> requirement should have a response time tied to it. in Optimizing
> Storage, poor performance is defined as average latency over 20ms and more
> than occasional spikes lasting more than a few seconds over 50ms. 20ms is
> a good response time starting target if you wish to aviod poor
> performance.
>
> Once you have the requiremnt defined, the Storage architect will translate
> that into a SAN architecture that support the requirement. From a
> perfornace perspective, the most significant factor will be the spindle
> count. Without knowing the specifics of the requirement and the design,
> it is impossible to predict what the performance of the SAN will be like
> irregardless of vendor or model.
>
>
>
> "Tim Coveney" wrote in message
> news:ugOONFIeGHA.2068@TK2MSFTNGP02.phx.gbl...
>> Hi all,
>>
>> Would anyone have any real world figures on IO throughput on a 4-8 node
>> cluster sharing drives on a HDS 9585 SAN they're willing to share?
>>
>> Will be talking to the manufacturers soon, just looking for some 'I've
>> seen this' figures from people who've done it...
>>
>> Many thanks,
>>
>> Tim
>>
>> --
>>
>> Tim
>> Llama IT
>> This posting is provided in good faith, "as is" with no warranties, and
>> confers no rights.
>>
>>
>
>
date: Tue, 16 May 2006 11:25:02 +0100
author: Tim Coveney
|
|