MSExchange.org Monthly Newsletter of July 2007 Sponsored by: ASP-OneWelcome to the MSExchange.org newsletter by Henrik Walther, Exchange MVP, MCTS/MSITP Exchange 2007, MCSE 2003 Messaging/Security. Each month we will bring you interesting and helpful information on Exchange Server. We want to know what all *you* are interested in hearing about. Please send your suggestions for future newsletter content to: henrik@msexchange.org 1. Exchange Server 2007 Memory UsageWelcome to the July 2007 edition of the MSExchange.org newsletter! Many of you are probably already enjoying your summer vacations, but there is always time available for reading the latest edition of the newsletter right? :-) I see a lot of memory related Exchange Server 2007 questions in the Exchange 2007 forum on the MSExchange.org boards, so this month my plan was to talk about what has changed in regards to memory utilization in Exchange Server 2007 compared to previous versions of Exchange Server. As most of you remember, because Exchange Server 2003 was based on 32-bit architecture, this version of Exchange Server was limited to using a maximum of 4GB of memory. Because Exchange Server 2007 is based on 64-bit architecture, this limitation is no longer there. In fact Exchange Server 2007 has much better memory utilization than Exchange Server 2003 had, and is capable of using 32 GB of memory and more. Personally, I have deployed Exchange 2007 Mailbox servers with 16 GB of memory installed, and I have seen Store.exe processes grow as large as to approximately 14 GB in size! These memory utilization changes are excellent for large enterprise IT organizations, but several of the smaller organizations with a relatively small amount of mailbox-enabled users (between 10-30) and an Exchange 2007 Mailbox server with let us say 4 GB of memory often seem to experience problems with excessive memory utilization. Several Exchange administrators report that their Exchange 2007 Mailbox server uses more memory than the amount of physical memory installed in the server. This means that the server can become sluggish and unresponsive. With Exchange Server 2003, the store process was bound to a certain memory cache limit. The upper bounds of this limit were typically set at around 900MB. With Exchange Server 2007 which uses 64-bit architecture, the limit on database cache size is no longer present. Currently, the default minimum cache size for Exchange 2007 is 512MB (for machines with at least 2GB RAM), and there is no maximum value set, which means that ESE (store.exe) will grow the cache to consume almost all available RAM on the server if there is no other memory pressure on the system. A larger database cache size typically results in greatly reduced disk I/O as reading information from memory is much faster than reading information from disk. If memory pressure occurs, that is other applications request/require memory, ESE will appropriately shrink the size of the database cache automatically. Okay, I hear you say, that was a good explanation, but unfortunately this is not the behavior I experience in my environment. So, what can I do if my Exchange 2007 server is sluggish and unresponsive? Although generally not recommended by Microsoft, there is one thing you can do. You can set a limit on the ESE database memory cache. This is done by following the below steps: Warning!
For example, 1GB cache equates to 1048576 (1024 * 1024). Divide the cache that you want to set by 8kb to determine the value to enter. In this case, 1048576 divided by 8 is 131072. If you wanted to set the cache size to 16GB, the value would be 2097152 (16777216 divided by 8). Note For more information on how to modify the store database cache size, see the following KB article: How to optimize memory usage in Exchange Server 2003 Cheers, Note: 2. Order Henrik Walther's Exchange Server 2007 book
3. MSExchange.org Learning Zone Articles of InterestWe have a great group of articles in the Learning Zone that will help you get a handle on your most difficult configuration issues. Here are just a few of the newer and more interesting articles:
4. KB Articles of the MonthHere are some interesting and useful MSExchange related articles posted by Microsoft in the last month:
5. Exchange WebcastsTechNet Webcast: Exchange Server 2007 Client Access and Web Services (Level 200) TechNet Webcast: A Technical Overview of Forefront Client Security (Level 200) TechNet Webcast: Disaster Recovery in Exchange Server 2007 (Level 200) MSDN Webcast: Windows PowerShell and Microsoft Management Console (Level 200) Momentum Webcast: Top Ten Reasons to Upgrade Your Messaging Server (Level 100) Momentum Webcast: Windows Mobile 6.0 Is Another Reason to Upgrade to Exchange Server 2007 (Level 100) Momentum Webcast: A Sneak Peek at Microsoft Unified Communications (Level 100) 6. Tip of the MonthHave this in mind when you make use of Edge Transport servers in your Exchange 2007 organization. When you have set up an Edge subscription you should always create/modify the send connector on the Hub Transport server(s) and NOT on the Edge Transport server, as the Hub Transport server periodically (by default every fourth hour) will sync any Send Connector changes to the Edge Transport server in your perimeter network using the EdgeSync process. For additional information I suggest you read this section in the Exchange 2007 Documentation. 7. MSExchange Links of the MonthExplore the Edge Transport server frontier http://technet.microsoft.com/library/c90c661c-a3c2-4f0d-9389-d9cbe6dc1ccb.aspx?wt.svl=featured Get to know transport rules in Exchange 2007 http://technet.microsoft.com/library/0b7aa1f9-d56c-4a09-9f0f-135cea5ac256.aspx?wt.svl=featured Data protection and disaster recovery for Exchange Server 2007 http://www.microsoft.com/technet/technetmag/issues/2007/07/exchange/default.aspx?wt.svl=featured TechED 2007 talk; Becky Benfield on Exchange 2007 SP1 Standby Continuous Replication (SCR) http://msexchangeteam.com/archive/2007/07/19/446454.aspx Windows 2003 SP2 Scalable Networking pack and its possible effects on Exchange http://msexchangeteam.com/archive/2007/07/18/446400.aspx Video: TechED 2007 talk; Kristian Andaker on Exchange 2007 SP1 OWA improvements http://msexchangeteam.com/archive/2007/07/17/446358.aspx Cross Org mailbox migration cleanup with Exchange Server 2007 http://msexchangeteam.com/archive/2007/07/16/446321.aspx Microsoft Baseline Security Analyzer Automation http://msexchangeteam.com/archive/2007/07/12/446151.aspx Mobile Device Connectivity to Exchange using IMAP vs Exchange ActiveSync http://msexchangeteam.com/archive/2007/07/10/446015.aspx How to Remove a Public Folder Database in Exchange Server 2007 RTM http://msexchangeteam.com/archive/2007/07/09/445967.aspx More on Exchange 2007 and certificates - with real world scenario http://msexchangeteam.com/archive/2007/07/02/445698.aspx Standby Continuous Replication in Exchange Server 2007 Service Pack 1 http://msexchangeteam.com/archive/2007/06/28/445538.aspx 8. Ask Henrik Walther a questionQUESTION: Hi Henrik, ANSWER: If the structure of the organization has changed, then you will not be able to mount the public folder databases on the new server. You would instead need to extract the data to .PST files using a 3rd party tool such as Power Controls: http://www.ontrackpowercontrols.com/exchange-solutions/email-exchange-server-recovery/ TechGenix Sites
|
Get Latest News on fashion, world politics, Internet, medical ,science ,education,money,shares,wildlife ,TV, Market,Sensex,Nasdaq,,Business,Accounting,Advertising, Animals,Antiques,Art,audio,books ,business,clothing, communication,computer,education,entertainment,internet,travel ,toys,health,gifts,games,gambling,finance, internet,jewelry,music,photography,politics,professional ,religion,shopping, sport.
No comments:
Post a Comment