<div>
I would start with Exchange 2010 Server Role Requirements Calculator from <a href="https://gallery.technet.microsoft.com/office/Exchange-2010-Mailbox-Server-Role-" rel="ugc nofollow">https://gallery.technet.microsoft.com/office/Exchange-2010-Mailbox-Server-Role-</a>
</div>


I would start with Exchange 2010 Server Role Requirements Calculator from https://gallery.technet.microsoft.com/office/Exchange-2010-Mailbox-Server-Role- [https://gallery.technet.microsoft.com/office/Exchange-2010-Mailbox-Server-Role-]

<div>
I get that but I am looking for some real world recommendations. Not MS technet. &nbsp; Any suggestions would be great
</div>


I get that but I am looking for some real world recommendations. Not MS technet.   Any suggestions would be great

<div>
<div class="content wysiwyg-content">
Hello, <br />
<br />
We are in the process upgrading our current exchange environment to provide for more flexibility, manageability, increased performance, etc... &nbsp;I put this question up to take some advise and opinions, here are some details. <br />
<br />
Current Config. <br />
<br />
230 mailboxes, 70ish distribution lists, 500+GB DB size, 1 Exchange 2010 Server running on VMware, Server 2008 R2, Storage on P2000 SAN. RAID 10, SAS 300 Drives. &nbsp; <br />
<br />
We now have 3 hosts connected to the P2000 and have introduced a second enclosure with more SAS drives. &nbsp;<br />
<br />
We would like to do the following: <br />
<br />
Split up the Database? <br />
Multiple Exchange Servers for different roles spread across the three hosts. ? <br />
How many DBs, different LUNS? &nbsp;<br />
<br />
Any other ideas you suggest? &nbsp;<br />
<br />
If you have questions for me, feel free to ask.
</div>
</div>


Hello, 

We are in the process upgrading our current exchange environment to provide for more flexibility, manageability, increased performance, etc...  I put this question up to take some advise and opinions, here are some details. 

Current Config. 

230 mailboxes, 70ish distribution lists, 500+GB DB size, 1 Exchange 2010 Server running on VMware, Server 2008 R2, Storage on P2000 SAN. RAID 10, SAS 300 Drives.   

We now have 3 hosts connected to the P2000 and have introduced a second enclosure with more SAS drives.  

We would like to do the following: 

Split up the Database? 
Multiple Exchange Servers for different roles spread across the three hosts. ? 
How many DBs, different LUNS?  

Any other ideas you suggest?  

If you have questions for me, feel free to ask.

Upgrading Exchange Environment for fail-over\redundancy

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Virtualization is the act of creating a virtual (rather than actual) version of something, including (but not limited to) a virtual computer hardware platform, operating system (OS), storage device, or computer network resources. Virtualization is usually the creation of a system that executes separate from the underlying hardware resources, or the creation of an entire desktop for systems located elsewhere, similar to thin clients.

Virtualization

Within Internet message handling services (MHS), a message transfer agent or mail transfer agent (MTA) or mail relay is software that transfers electronic mail messages from one computer to another using a client–server application architecture. A MTA implements both the client (sending) and server (receiving) portions of the Simple Mail Transfer Protocol (SMTP). The terms mail server, mail exchanger, and MX host may also refer to a computer performing the MTA function. The Domain Name System (DNS) associates a mail server to a domain with mail exchanger (MX) resource records containing the domain name of a host providing MTA services.