Is there a limit on the number of "stores" you can have on an Exchange server? It seems that it takes a very long time to repair one large store and we are thinking it might be better to divide the stores up into smaller chunks so we can bring accounts back up faster if it happens again. Some people were thinking there was a maximum number you could have. This seems a bit arbitrary to me....
|
With an Exchange 2003 Standard server it is 1 Mailstore and 1 Recovery Mail store. With the Enterprise version it is 4 + 1 Recovery Mail Store. Of course the better question is "Why do I have to recover my mail store enough that this is a concern?" You really should not need to repair your mail store unless something goes horribly wrong - like power dropped and your battery on your RAID controller was dead so you lost changes. Additionally, smaller mail stores won't help you that much. The repair programs need to go through every data structure in the JET database, inspect, verify, attempt repair, re-inspect, re-verify it is a process that is just going to take a long time. However, you really should not have to repair an Exchange data store all that often - if ever. |
|||||||||||
|
|
From KB 821748 - HOW TO: Add New Mailbox Stores in Exchange Server 2003
This applies to the Enterprise edition of Exchange 2003. The Standard edition limits you to a single mailbox store of 16GB, or 75GB if you have SP2 and make a small registry change. |
|||
|
|
Graeme Donaldson and Zypher are correct. That is actually a good reason to go to Exchange 2007/2010. In the standard edition, you can have 5 databases in either 2007 or 2010, and in the enterprise edition, you can have 50 in 2007, and 100 with Exchange 2010. Even with the standard editions, you can take your heaviest users and break them up over three databases, and put the rest on one. I usually leave one open for future use. This can really be noticeable help, for example, if you are doing a granular restore in Backup Exec since it has to stage the entire database, and if it is broken up, it takes much less time. |
|||
|
|