|
Guy recommends :
Find out which of your VMs are a waste of space and which VMs need more resources.
|
Microsoft Exchange Server 2003 - Stores and Storage GroupsIntroduction to Exchange Server 2003 Stores and Storage GroupsInstead of having one huge mail store, I advise you to divide, and so rule your Exchange kingdom. Management really is the keyword. By creating multiple storage groups you will greatly improve your control of the Exchange Server 2003 mailboxes. I would go so far as to say that amateurs are unaware of the benefits of multiple stores, whilst professionals create stores for different user groups or different backup requirements. Topics for Microsoft Exchange 2003 Stores and Storage Groups
Benefits of Exchange Multiple Stores
Trap: Multiple stores and storage groups are only available in the Enterprise edition of Exchange 2003. (Not in the Standard or SBS editions.) ♠ Configuration Properties for Exchange Mailbox StoresEach mailbox store has its own settings. You can have up to 5 stores in each Storage Group. Just imagine the logistics problems having one huge store which holds everyone's mailbox. Then think of the benefits of having the bosses, manager, and directors in their own mailbox store. Advantages include, faster restore, less disruption if you need to dismount a store. Also you can create different Exchange System Policies for each store. Multiple stores give flexibility. Limits Tab My
advice is set limits for all users' mailboxes. Firstly, limits encourage good housekeeping; people need a reminder to delete old mail messages. Secondly,
perhaps I should not say this, but it
gives you an opportunity to play the hero. Take the situation where you know the limit could be 10x. However you set the limit at 5x and when the users complain, you kindly raise the limit
to 8x. Now you are their friend and you still have 2x in reserve. Talking of being the hero, always select: ' Keep Deleted Items '. What this setting does is act as a safety net. The users think, ' Oh dear, the message is gone for ever '. However, clever you have a copy of their email on the server. Just instruct them how to retrieve the deleted item using their Outlook Tools menu. My preferred setting is to tick: Do not permanently delete until the store is backed up. I expect you realize that where necessary, you can over-ride the mailbox limits. To make an exception to your policy, navigate to an individual's Exchange properties sheet in Active Directory Users and Computers. Alternatively, you could set Limits via a System Policy see here. General Tab What are you going to do about archiving email? One day your government may pass a law making it compulsory to keep copies of all company email. The technology to journal or archive messages has been around since Exchange 5.5. The problems are more to do with politics and security than configuring Exchange 2003. Database Tab The Exchange 2003 databases, (e.g. Priv1.edb) are used by MAPI clients like Outlook 2003. All non MAPI clients send and receive in MIME format, and their messages are stored in the .stm (streaming database). All the conversion goes on automatically ' under the covers '. Be aware of these two databases (.edb and .stm), but there is little to configure apart from the file location. Note: Strange but true, it is possible to dismount a store then move the .edb file to another disk. Plan your Exchange 2003 maintenance schedules. Make sure that the timings are staggered for each store. Maintenance in general and indexing in particular, can be processor intensive, so schedule maintenance for the middle of the night when there are few users online.
| ||||
Custom Search
|
SolarWinds Exchange Monitor
|
|
Home Copyright © 1999-2012 Computer Performance LTD All rights reserved Please report a broken link, or an error. | |