Posts Tagged ‘microsoft exchange’
The Public Beta of Exchange 2010 is Available
Written by Brett Callow on April 17, 2009 – 9:41 am -
On 15th April, Microsoft announced the availability of Exchange 2010, the successor to Exchange Server 2007. According to Microsoft:
Exchange 2010 is part of the next wave of Microsoft Office-related products and is the first server in a new generation of Microsoft server technology built from the ground up to work on-premises and as an online service. This release of Exchange 2010 introduces a new integrated e-mail archive and features to help reduce costs and improve the user experience.
What’s new in Exchange 2010? Here’s some details: Continue reading The Public Beta of Exchange 2010 is Available
Archive Stubbing Techniques Not Recommended
Written by Carl E. Reid on April 7, 2009 – 2:27 pm -
The benefits associated with archiving Microsoft Exchange email and associated data, creates many cost effective solutions. Archiving facilitates government regulatory or civil litigation searches for ediscovery requests. It also allows for more complete archive journaling, and provides storage benefits for both mailbox growth and the various storage devices that can be utilized.
Although lowering storage reduction costs is a common denominator for email archiving, compliance requirements are moving more companies to implementing archiving strategies. Depending on the motivation factors, cost savings on storage are subject to interpretation by different people. For some people, compressing email could reduce licensing, as well as storage hardware costs. For others it may mean creating a mailbox for end users, which has virtually unlimited space.
Continue reading Archive Stubbing Techniques Not Recommended
How Much Memory is Too Much?
Written by Brett Callow on April 3, 2009 – 2:23 pm -“The more the better,” is a common mantra when it comes RAM but, in the case of Exchange Server 2007, that’s certainly not the case (OK, so it isn’t really the case in relation to other operating systems either, but that’s for another story).
With Exchange Server, Microsoft recommend no more than 32 GB of RAM. That’s because a) more than 32 GB will not substantially improve performance (and so you’d be wasting your money) and b) it may actually negatively impact performance. Here’s why (from Microsoft):
Cold state is defined as the state of the Mailbox server immediately following a server reboot or store.exe process restart. The Database Cache, which is used to cache database read/write operations, is small in size (or “cold”) during this period so it has a significantly diminished ability to reduce read I/O operations. As the Mailbox server processes messages, the Database Cache Size grows which increases the effectiveness of the cache and subsequently reduces the I/O footprint of the server. The larger the physical memory size of the server the longer it takes the Database Cache size to reach its optimal size. If the storage is designed/sized for a server with a large amount of physical RAM (>32GB), and the I/O profile of the users assumes an optimal Database cache state (large/warm cache); then the client experience may be compromised due to insufficient disk performance during these “cold state” periods.