Exchange 2007 - Stores and Storage Groups
Exchange 2007 Stores and Storage Groups
Instead of having one huge mail store, I advise you to divide, and so rule your Exchange Organization. Management really is the keyword. Creating multiple storage groups will greatly improve your control over the Exchange 2007 server mailboxes.
Topics for Exchange 2007 Storage Groups
The big news for Exchange 2007 storage groups is that the standard edition now has no database limit. If you remember, in Exchange 2003 it only grow to a maximum of 75 GB. However, even better news is the increase in storage groups for the Enterprise versions, you can now have up to 50 mailbox stores per server.
For protecting physical goods, check out Aberystwyth storage.
Creating More Exchange Storage Groups
Begin by launching the Exchange Management Console. You can actually do this from any server.
Exchange Server 2007 has a new feature called Local Continuous Replication (LCR) for your mailbox storage group. One consequence of enabling LCR is that you can only have one database in each store. The idea is to reduce the recovery time for data-level disasters. LCR works by enabling a quick switch to a second online copy of the data.
Exchange Mailbox Store
One option you may wish to implement is the Journal Recipient. Exchange 2007 Server can automatically copy every message, what you do is create a special account, and then 'wire up' the mailbox store to this Journal Recipient.
Move a Mailbox
It could not be easier to move a mailbox store, just right-click the store and the wizard will guide you through the process to re-house the database.
When you configure mailbox limits, they never seem to work. This is because they take at least two hours to take effect. You can enforce a limit immediately by restarting Microsoft Exchange Information Store service. Rebooting the Exchange 2007 server would have the same effect, but restarting the service is a more intelligent and satisfying solution.
Errors when you mount a database
If you get error messages when you mount a database store, the simple solution is to apply Exchange 2007 Server SP1. In the event logs you may see evidence such as ID 7011, 7034, 9518, or 9519. It is possible that these are false positives, and in fact, Exchange 2007 mounted the database without any loss of data.
NTM will produce a neat diagram of your network topology. But that's just the start; Network Topology Mapper can create an inventory of the hardware and software of your machines and network devices. Other neat features include dynamic update for when you add new devices to your network. I also love the ability to export the diagrams to Microsoft Visio.
Finally, Guy bets that if you test drive the Network Topology Mapper then you will find a device on your network that you had forgotten about, or someone else installed without you realizing!
Download your 14 day free trial of SolarWinds Network Topology Mapper
Server Stops Responding to a MAPI Client
Exchange Server 2007 sets limits on the number of server objects that MAPI clients can open. This is a classic trade-off, if you allow Microsoft Outlook client to open unlimited numbers of objects on the server, then a few thoughtless uses can hog the server. If you choke down the number of objects any one client can open, then you will get lots of Event 9646, indicating that a MAPI client has opened too many objects on the Exchange 2007 server.
As so often these cases, there is a registry setting where
you can change the defaults:
You need to create a sub-key called: MaxObjsPerMapiSession
Next, right-click the MaxObjsPerMapiSession that you just created, click New, and then click DWORD Value objtMessage. In the 'Value' data box, type the new maximum number of objects, say 500.
If you are interested, you could research then add more values, for example: objtStream, objtACLView, objtRulesView, objtFXSrcStrm, objtFXDstStrm, or objtCStream.
'Windows could not start the Microsoft Exchange Information Store on Local Computer.'
Check the application event log for Event ID messages 1121 and 5000. The root cause is most likely caused by 'Mr Nobody' deleting the default E-mail Address policy, and then creating a new default policy.
The solution to this error 'Windows could not start the Microsoft Information Store', lies with ADSI Edit (not Regedit). What you need to do is set the attribute msExchPolicyOrder = 2147483647. This how to navigate to the correct property:
General Solution to Store Problems
Restart the underlying Exchange 2007 service:
In Services snap-in, in the details pane, locate the Microsoft Exchange Information Store service.
Alternatively, use a PowerShell command:
SolarWinds' Network Performance Monitor will help you discover what's happening on your network. This utility will also guide you through troubleshooting; the dashboard will indicate whether the root cause is a broken link, faulty equipment or resource overload.
What I like best is the way NPM suggests solutions to network problems. Its also has the ability to monitor the health of individual VMware virtual machines. If you are interested in troubleshooting, and creating network maps, then I recommend that you try NPM now.
After launching the Exchange Management Console and looking around, you may find it quicker and easier to type a few PowerShell commands rather than keep drilling down via the GUI. Here are a few of the many PowerShell commands to configure your Exchange 2007 stores and storage groups.
Example: Mount-Database -Identity ExchSrv\MgrDatabase There is also a sister command: dismount-Database.
Example: remove-MailboxDatabase -Identity "OldMgrs"
set-MailboxDatabase This is the command to set mailbox limits.
Example: Set-MailboxDatabase "MgrDatabase" IssueWarningQuota 512000000 ProhibitSendQuota 563200000 ProhibitSendReceiveQuota 614400000
set-MailboxDatabase has more parameters, for example, you can 'wire up' email journaling. There is also a family of MailboxPermission commands, which use the verbs add, get or remove.
Two more interesting cmdlets are: get-MailboxFolderStatistics and also get-MailboxStatistics.
move-DatabasePath This command requires more parameters, I would favour the GUI unless you are for ever moving mailstore databases.
Import users from a spreadsheet, complete with their mailbox. Just provide a list of the users with the fields in the top row, and save as .csv file. Then launch this FREE utility, match your Exchange fields with AD's attributes, click and import the users. Optionally, you can provide the name of the OU where the new mailboxes will be born.
Just like its predecessor, each Exchange 2007 store is associated with its own database file, but shares the storage group's log files. When you install Exchange Server 2007, it creates a storage group named First Storage Group as well as a mailbox store. Thereafter, you can create additional stores, and modify the parameters associated with a store.
If you like this page then please share it with your friends
See more Microsoft Exchange Server 2007 topics: