Re: FE/BE vs standalone

  • From: "Lara, Greg" <GLara@xxxxxxx>
  • To: "'exchangelist@xxxxxxxxxxxxx'" <exchangelist@xxxxxxxxxxxxx>
  • Date: Thu, 21 Oct 2004 12:45:26 -0400

I agree with Al's points, and would like to point out something about
storage. As important as determining disk size is choosing the right RAID
configuration for the various databases and logs. Not only the RAID version,
but the number of spindles. There's a very interesting post about this  on
the Microsoft Exchange Team blog at I'll post the
exact link later when I have access to it. 


-----Original Message-----
From: A. M. Salim <msalim@xxxxxxxxxxxx>
To: [ExchangeList] <exchangelist@xxxxxxxxxxxxx>
Sent: Thu Oct 21 12:24:41 2004
Subject: [exchangelist] FE/BE vs standalone


I am trying to decide on the best architecture for a new installation.
This will have 350 users, average mailbox sizes and traffic (100MB
mailboxes typically).  I am OK for figuring out how much space I need.

Question is architecture:

a) for this many (or few?) users, should I consider a front end/back end
configuration or is a single-server installation sufficient (e.g. a
P4/3GHz server with 1GB RAM) ?  What would the benefits of FE/BE be over
stand alone?

b) I will also set up a clustered active/passive backup server.  Are there
any recommendations regarding FE/BE in a clustered environment?

c) The customer has a SAN and seems keenly interested in the notion of
setting up the server to boot off the SAN.  Is this a recommended method
(best practices)?  Booting workstations off of the SAN is one thing but
booting mission critical servers off of a SAN might be risky?  Thoughts?

best regards
Mike Salim

List Archives:
Exchange Newsletters:
Exchange FAQ:
Other Internet Software Marketing Sites:
World of Windows Networking:
Leading Network Software Directory:
No.1 ISA Server Resource Site:
Windows Security Resource Site:
Network Security Library:
Windows 2000/NT Fax Solutions:
You are currently subscribed to this Discussion List as:
To unsubscribe visit
Report abuse to listadmin@xxxxxxxxxxxxxx

Other related posts: