<div>
Is it a virt? if so match the cluster size of host storage if not 32 would work best.
</div>


Is it a virt? if so match the cluster size of host storage if not 32 would work best.

<div>
Not a virt. Is this specific to E2K10 or does it also apply to E2K7, just curious. thanks again
</div>


Not a virt. Is this specific to E2K10 or does it also apply to E2K7, just curious. thanks again

<div>
Thanks for the info, one final question:<br />
I typically put the data and log files on two separate partitions, but on the same SCSI container. Would it be wise to do this with E2K10 or should the database and logs go on one big partition, and if the logs go on a separate partition should 32k be used as the cluster size for the log files?
</div>


Thanks for the info, one final question:
I typically put the data and log files on two separate partitions, but on the same SCSI container. Would it be wise to do this with E2K10 or should the database and logs go on one big partition, and if the logs go on a separate partition should 32k be used as the cluster size for the log files?

<div>
Best practice:<br />
1-logic drive for OS, LOGS, DB/store, Transact
</div>


Best practice:
1-logic drive for OS, LOGS, DB/store, Transact

<div>
<div class="content wysiwyg-content">
Is there an optimal cluster size when formatting a hard drive for a E2K10 database.<br />
I saw something where is says: 'The best size for the Exchange 2010 Mailboxes would be 32k NTFS Cluster size, since this maps 1:1 to the Mailbox Cluster Size. Is thsi correct? I have a E2K7 with cluster size of 65,536 kb.
</div>
</div>


Is there an optimal cluster size when formatting a hard drive for a E2K10 database.
I saw something where is says: 'The best size for the Exchange 2010 Mailboxes would be 32k NTFS Cluster size, since this maps 1:1 to the Mailbox Cluster Size. Is thsi correct? I have a E2K7 with cluster size of 65,536 kb.

Cluster Size for Exchange 2010

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.