<div>
The key thing with database size is what your SLAs are like. Between 50 and 100gb is recognised as being a good place to be with regards to having databases that are fairly quick to restore if required. <br />
<br />
-M
</div>


<div>
Hi Guys<br />
<br />
Thanks for all the articles.<br />
<br />
I have a couple of queries;<br />
<br />
a) Recommended database size limit is 100 GB in case you are not use any kind of continuous replication &amp;&nbsp;200 GB if you are using LCR/CCR.<br />
<br />
Is SCC (which we will be using) considered continous or non-continous?<br />
<br />
b) If we have a mailbox quota of 1GB and have 100 users, will the max DB size be 100GB, or do we need to factor in white space etc? Is there &nbsp;a method to calculate this?<br />
<br />
I have seen this method;<br />
<br />
Maximum database size should always be calculated as follows: Number of mailboxes × Maximum mailbox size = Database size<br />
<br />
But also this;<br />
<br />
&nbsp;Mailbox Size = Mailbox Quota + White Space + (Weekly Incoming Mail × 2)<br />
<br />
Can anyone help me?<br />
<br />
Much appreciated.<br />
<br />

</div>


<div>
On the MS Exchange Team blog they have a spreadsheet which can calculate your storage requirements for you. I suggest that you start with that. <br />
<br />
-M
</div>


<div>
<div class="content wysiwyg-content">
Hi Everyone<br />
<br />
We are currently using Exchange 2003 SP2 - we have a couple of mailbox servers, each with 4 Storage groups each. Each Storage Group has 4 Mailbox stores. Therefore we have a total of 32 Mailbox stores.<br />
<br />
With Exchange 2007, we are looking into one Mailbox store per Storage Group. As such, we'll need to increase the number of Storage Groups (we are looking at about 60 altogether).<br />
<br />
Since we are almost doubling the amount of Mailbox stores, we want to ensure we keep users of the same department on the same store to take advantage of Single Instance Storage.<br />
<br />
We are, however, planning on giving all mailboxes a 1GB limit as opposed to 100MB which it is currently.<br />
<br />
Are there any recommended numbers of max users/sizes of databases/storage group log locations for Exchange 2007?
</div>
</div>


Hi Everyone

We are currently using Exchange 2003 SP2 - we have a couple of mailbox servers, each with 4 Storage groups each. Each Storage Group has 4 Mailbox stores. Therefore we have a total of 32 Mailbox stores.

With Exchange 2007, we are looking into one Mailbox store per Storage Group. As such, we'll need to increase the number of Storage Groups (we are looking at about 60 altogether).

Since we are almost doubling the amount of Mailbox stores, we want to ensure we keep users of the same department on the same store to take advantage of Single Instance Storage.

We are, however, planning on giving all mailboxes a 1GB limit as opposed to 100MB which it is currently.

Are there any recommended numbers of max users/sizes of databases/storage group log locations for Exchange 2007?

Recommended sizes for Exchange 2007 mailbox stores

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

Servers are computing devices that are similar to desktop computers in that they have the same basic components, but are significantly different in size, configuration and purpose. Servers are usually accessed over a network, and many run unattended, without a computer monitor, input device, audio hardware or USB interfaces. Many servers do not have a graphical user interface (GUI), and are configured and managed remotely. Servers typically include hardware redundancy such as dual power supplies, RAID disk systems, and ECC memory, along with extensive pre-boot memory testing and verification. Critical components might be hot swappable, and to guard against overheating, servers might have more powerful fans or use water cooling.

Server Hardware

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.