Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows Server 2003Windows 2000Windows NTSmall Business ServerVirtual ServerExchange ServerIISHost Integration ServerISA ServerSMSWSUSMOMWindows Media ServerSecurityCertification
Related Topics
SQL ServerMS WindowsMS OfficePC HardwareMore Topics ...

Windows Server Forum / Exchange Server / Design / December 2004

Tip: Looking for answers? Try searching our database.

Design Help

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
maddessa - 15 Dec 2004 15:31 GMT
Hi All

Hoping someone can give me some high level advice. I have 1000 users we want
to switch over to Exchange 2003.  The physical location of the servers will
be central.

50 Simulataneous POP or IMAP connections
200 Simultaneous OWA Connections
100 quota limit
50000 messages and 700 MB per day

At this point I did not plan on clustering.

My plan was to implement one front-end server and one back-end server. I
used the HP Exchange configurator to come up with a server to support 1000
users.  People are telling me that you can't put more than 200 users per
backend server. Is this correct? Does it make sense to put 1000 users on one
server should I split them up? Is 2 servers enough? I tried to use the 2000
capacity planning spreadsheet but it is a dead link on the MS site.

Should I add another server dedicated to just routing SMTP mail?

Does anyone have advise on whether I should use one or more message stores?

Does this make sense?
Al Mulnick - 16 Dec 2004 02:39 GMT
1000 users?  That's not very much :)
I've got 5.5 servers that handle more than that.

I think your plan will work fine.  You may want to consider using multiple
backend servers, but not for operational effectiveness.  More to keep from
putting your eggs in one basket so to speak.  If you have a failure on that
one server, you'll effectively take out the entire population.  Vs. having
two smaller servers where you might take out half the population.

The 200 users limit might be a reference to the CDO OWA concurrency barrier.
Some swear you can't get more than 200 simultaneous 5.5 OWA connections
going due to the limitation in the architecture.

The number of message stores is something you'll have to figure out.
Generally, if you're going to use Enterprise version of Exchange, you may
want to spread the users out over multiple stores and storage groups to take
advantage of smaller stores. This allows for faster backups and restores as
well as maintenance if needed.  In your case, you can take advantage of
single instance storage if you leave them in a single store.  However, I
think you should use a few stores (3?) so you can have smaller stores to
work with.  You won't get a benefit in the backups if you use one Storage
group so it's left to your discretion and comfort level.  I would not want
any one store larger than 100GB if I could help it.

Al

> Hi All
>
[quoted text clipped - 22 lines]
>
> Does this make sense?
maddessa - 19 Dec 2004 06:05 GMT
Hi Al
   First, thanks for responding.   So if I was going to buy two backend
servers would you advise splitting the users or cluster, what we be the most
effective use of the hardware?  On other systems I have implemented before
(no exchange) there always seemed to call for an independent mta, is one
advised for use with exchange?

Thanks again

> 1000 users?  That's not very much :)
> I've got 5.5 servers that handle more than that.
[quoted text clipped - 49 lines]
>>
>> Does this make sense?
Al Mulnick - 20 Dec 2004 01:27 GMT
The idea of splitting the users is to provide hardware failure tolerance of
some level.  Clustering can do that as can two standalone servers with some
hardware redundancy in them (power supplies, memory etc).  If you can
withstand more than 15 minutes of downtime on either server at a time
(basically, can you withstand how much time it may take to get you back up
and running if you get a hardware failure on one of the servers), then I say
keep it simple and go with two standalone servers.  If you have to have the
higher availability and hardware is a concern, then the complexity and cost
may be worth clustering. It'll fail over much faster and you'll have them
available as long as the problem is with the machine hardware itself (mostly
;)

There are some pieces of Exchange that don't like to cluster, such as the
SRS last I checked.  I haven't checked in some time however so feel free to
correct as needed.

What I'm trying badly to illustrate is that the decision to use two
machines, or to use one machine or to use a clustered pair of machines has
more to do with our service outage tolerance than any technical reason.
It's a tradeoff you have to make after weighing the different possibilities.

Whatever you do, keep it as simple as you can and you'll be much happier
down the road.

Al

> Hi Al
>    First, thanks for responding.   So if I was going to buy two backend
[quoted text clipped - 59 lines]
>>>
>>> Does this make sense?
maddessa - 20 Dec 2004 16:15 GMT
Al
   You are the man. Thanks for your time.

> The idea of splitting the users is to provide hardware failure tolerance
> of some level.  Clustering can do that as can two standalone servers with
[quoted text clipped - 87 lines]
>>>>
>>>> Does this make sense?
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.