Solved

Exchange related question on IOPS

Posted on 2011-02-15
4
359 Views
Last Modified: 2012-05-11
We have a remote site running Exchange 2007 in SCC - Active/Active/Passive on Windows 2008 Server. The environment was sized for about 1500 users and we worked with vendors on SAN disk configuration etc.

We're now going to deploy BES there to keep them inline with company policy.

I understand there will be an increase in IOPS - roughly about 4 times the IOPS for each user we BES-enable.

We haven't gone into the details, so this question is more hypothetical really, but is the solution to increased IOPS more disks in the SAN array? What if the array has no more space for disks? Is there anything else I can do?
0
Comment
Question by:chuckp2010
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
4 Comments
 
LVL 34

Accepted Solution

by:
Paul MacDonald earned 167 total points
ID: 34901582
Generally the response to more IOPS is to spread the load among LUNS, not just to add spindles to a LUN.  That is, create several mail databases and put them each on their own drive.
0
 

Author Comment

by:chuckp2010
ID: 34901669
Could you expand, not sure I understand the answer? I always thought the answer was to add more spindles, so I guess my understanding was wrong in the first place! :)

Secondly, what's the effect of not making changes to deal with the increased IOPS? Delays in Exchange I guess?
0
 
LVL 43

Assisted Solution

by:Amit
Amit earned 167 total points
ID: 34904067
I am not a SAN expert. But as I am handling Exchange from long time. I asked same question to my SAN team. They normally answer, that we need minimum 20% space free in SAN side.

Secondly, I don't think BES will going to create that IOPS issue on the Exchange server. By Default BES will use 5 threads to access information from Exchange. Now make sure you don't configure remote Exchange user to remote BES server. This will block one thread and if it is hung whole BES system will not function. Let me explain how.

If you have multiple Exchange servers. Say EX001 in NYC and EX002 in HAC site. Now you implemented a BES server in NYC site for EX001. Till here all is good. But the time you configure any Ex002 user to NYC BES server, one BES thread will be utilized and if it hung BES mail will not work.
0
 
LVL 55

Assisted Solution

by:andyalder
andyalder earned 166 total points
ID: 34905197
Adding spindles or converting to a faster form of RAID (if possible) on the SAN side should speed it up. Of course it depends on the SAN's current configuration. More LUNs/databases will obviously help too.
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The business world is becoming increasingly integrated with tech. It’s not just for a select few anymore — but what about if you have a small business? It may be easier than you think to integrate technology into your small business, and it’s likely…
After hours on line I found a solution which pointed to the inherited Active Directory permissions . You have to give/allow permissions to the "Exchange trusted subsystem" for the user in the Active Directory...
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
how to add IIS SMTP to handle application/Scanner relays into office 365.

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question