Re: Single RAID 5 for everything....

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Something to note:
When you do alleviate the disk bottle neck, you'll likely see some
additional processor usage and some memory being freed up. Not that I'd
know from experience or anything :)

You can also check the client response times which will indicate what the
clients are seeing. Exchange 2003 keeps those on the server as long as
you're using Outlook 2003 (or later).

BPA might be of use to you as well. You may want to check it out since you
need supporting data.

My $0.04 anyway.

Al




"kage13" <kage13@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:72199C66-C1D2-435A-8FAA-2890C43AA43A@xxxxxxxxxxxxxxxx
Thanks guys for the response. With regards to perfmon monitoring...thats
one
of the first things I did so I could gauge the IOPS, which is realtively
low
mainly due to the lack of utilization of the CPU and memory. The avg. CPU
%
is 4-6 and I haven't gotten any paging errors or memory errors either so
the
resource usage is low. Now on to the disk IO...the baseline # is 2 for
avg
total disk queue...ours is constantly around 4-6 and my physicaldisk/avg
disk
sec/read/write is over 50ms for the better part of the working day.
Maybe these are types of figures I need to keep putting in their faces to
get them to understand. Not to mention that since the server was rebuilt
back in June/July...they had a major weekend prior to my starting and a
disk
on the exchange server failed on the reboot already.
To me its a no-brainer...but what do I know. :)

Thanks guys...anymore info. would be appreciated.

Ken


"Ed Crowley [MVP]" wrote:

Personally, I wouldn't bother splitting the page file from the OS because
if
you're paging so much that paging disk performance is affecting overall
system perfromance, then you simply don't have enough memory. In an
Exchange server, you should be installing so much memory that Exchange
doesn't page--the extra memory is used for data caching, which doesn't
page.
Instead, I'd add those two disks to the store volume so that you're
striping
across more disks.

In addition, if you have a top-flight RAID controller (like HP
SmartArray)
then RAID-5 can actually be more efficient because you'd be striping
across
more drives. If you have enough users, you could possibly improve
performance by splitting your store and logs in two and building
additional
RAID-1 and RAID-5 volumes for the logs and databases, respectively.

However, I cannot tell you that your disk performance is the cause of
your
problem because I haven't seen any evidence to support that. You're
going
to have to start collecting some Performance Monitor data to support
that.
In the Microsoft Exchange 2003 Technical Resources web site there's a
great
white paper that will help you determine which performance monitor
counters
to use to troubleshoot disk performance.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"kage13" <kage13@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:ED57988C-0C6E-4E15-A851-12A5E202C68D@xxxxxxxxxxxxxxxx
yup, that's correct. I have taken over for an exodus Exchange Admin at
my
current employer. Sometime ago the previous Exchange server had a
catastrophic failure they ended up rebuilding the server and performing
a
restore. However, instead of rebuilding the correct way, it was
rebuilt
as a
poster child of what NOT to do...a single RAID 5 for everything.
I now have the task of arguing with mgmt. that this is not working, the
server is heavily taxed with I/O ops, client latency from Outlook, etc.
I
have given my recommendations on how the server should be setup:
C:\ - OS; Exchange system files - RAID1 (on physical sever)
D:\ pagefile - RAID1 (on physical server)
E:\ Transaction logs - RAID1 (SAN)
F:\ Storage Groups - RAID0+1 (SAN)

and they are saying that this is overkill that it won't provide much
more
than what they are currently getting! Can you believe this!
Anyway, has anyone had the same discussion with their ex/bosses and won
the
fight I'd appreciate any information you used for leverage. I'm about
to
pull my hair out and just let the server go down in flames and wait for
them
to come to me fix it, with an "I told so!" from me.

TIA,

Ken






.



Relevant Pages

  • RE: The store.exe process is allocating more memory than usual.
    ... Welcome to SBS nesgroup. ... I understand that after install SBS SP1, your SBS got memory allocates ... It is an expected error after apply the Exchange ... For the Small Business Server 2003, Microsoft has release a specific update ...
    (microsoft.public.windows.server.sbs)
  • Re: Disck write latency > 50ms
    ... Also how can I tell how many users are connected to the Exchange 2003 ... long IO operations against a given physical disk are taking. ... criteria from "Optimizing Storage for Exchange Server 2003" to alert; ... we are to but another RAID card for this too. ...
    (microsoft.public.exchange.admin)
  • Re: Store.exe consumes too much RAM
    ... report our server as uninfected. ... SBS2000, Exchange 2000, SQL Server 2000 all with latest ... >server has been down as low as 4k of available memory. ... >out of the installed 1GB of RAM. ...
    (microsoft.public.exchange2000.information.store)
  • Re: Ideal Hard Drive configuration
    ... can run Exchange Best Practices Analyzer utility to check your Exchange ... Server, for more detailed questions, please contact our Advisory Services ... Microsoft CSS Online Newsgroup Support ... |> of physical RAM can require large amounts of additional kernel memory to ...
    (microsoft.public.exchange.admin)
  • Re: Ideal Hard Drive configuration
    ... implement hot-add memory or that are configured with more than 4 gigabytes ... to reduce the server load by removing large numbers of mailboxes or to ... So please not configure the Exchange Server with more than 4 GB RAM. ... I have included some articles about Windows 2003 planning and deployment ...
    (microsoft.public.exchange.admin)