Re: Server and storage design for just OWA, POP and IMAP

-We would give the users' the option to store all mail locally or on the
server. Most tend to leave mail on the server.
-No quota as planned (yes I know it's tough to design without any quotas.)
-99% are in the same time zone.
-Most messages are in the 10-50KB range.

Though I will need to look into planning the SMTP servers, my biggest
concern is the spindle count for the DB's at this point. The current
whitepapers go over calculating the IO's per average user and how to design
your storage. I was at Teched this year and the guys I spoke with didn't
really have an answer for IO's for an average OWA, POP and IMAP user. We
all agreed it was less but I need a definitive answer. The previous post
talked about the HP sizing tool which I'm going to look at.

"Al Mulnick" <amulnick_No_SPAM@xxxxxxxxxxx> wrote in message
news:eogEWk0eFHA.2844@xxxxxxxxxxxxxxxxxxxxxxx
> Do you have more information available?
>
> Storage: Do you intend for POP users to store mail locally only? Or
> locally and on the server? What is the mailbox sizing you're aiming for?
> Usage patterns: Is this all in the same time zone with all users
> concurrently using the system? If not, how many concurrent are expected?
> Message size: What's the average message size you expect?
>
> Generally speaking, SMTP performance is achieved by adding physical disks
> especially for submit transactions. Delivery will also have some disk
> performance relationship.
>
> POP, IMAP, and HTTP users typically scale quite well and are what the
> FE/BE scenario is designed to achieve. My biggest concern in that kind of
> design would be around reliability (availability of service) and disk
> subsystem. Network topology would be next depending on the requirements.
>
> Al
>
>
>
> "Joe" <joe@xxxxxxxxxxxxxxx> wrote in message
> news:ui%23mOezeFHA.2736@xxxxxxxxxxxxxxxxxxxxxxx
>> All of the current whitepapers are geared towards perf and capacity
>> planning for MAPI users. I need help with how to design the servers and
>> storage for about 50,000 users that will be regulated to just OWA, POP
>> and IMAP. Anyone have any ideas?
>>
>
>


.

Relevant Pages

  • Re: Exchange 2007 and Hyper-V question
    ... I'm finalizing a design for a client that wants a 5,000 user Exchange 2007 ... I understand that E2K7 is supported in Hyper-V, with the exception of the UM ... Install Hyper-V on the server as well as the UM role. ... You would then be able to use three mailbox servers as ...
    (microsoft.public.exchange.design)
  • User autentification and access to "sister" domain resources
    ... I am in process of designing brand new AD structure for our customer. ... 2003 Servers - pretty classic design ... All DCs are Global Catalogs. ... user_from_domainA gets IP address from siteB DHCP server ...
    (microsoft.public.win2000.active_directory)
  • Re: Using SQl to store aspx pages and memory problems
    ... The solution I was looking at would be to create some specific server side ... I want the data to be saved in the page so I thought that a asp.net control ... the original design and one that ensures that future system changes will not ... > database isn't some sort of magic pixie dust that solves all problems. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Software Testing Tools
    ... you should design and redesign frequently while ... majority of its functionality implemented on the server. ... API for the client such that the UI is an entirely separate component - ... most efficient and reliable way to test the server is not with the GUI ...
    (comp.software.testing)
  • Re: External users vs internal users.
    ... I think I need help with the design full-stop. ... To have Team and Meeting sites available to groups of external users. ... Then you'll need a separate WSS farm for this since you're using account ... > server, with Portal server on an internal server, but both use the same ...
    (microsoft.public.sharepoint.portalserver)
Loading