Topic Last Modified: 2009-02-06

The Microsoft Exchange Server Best Practices Analyzer examines the storage locations for Microsoft Exchange Server 2007-based servers that are configured to use one of the following high-availability features:

The Best Practices Analyzer examines the data storage locations to verify that sufficient hard disk drive space is available for the correct operation of Exchange. If the Best Practices Analyzer determines too many log files are present in the IgnoredLogs subfolder of the transaction log folder, the tool generates the following warning message:

The size of the log files in '<FolderName>' folder for storage group '<StorageGroup>' on server <ServerName> is bigger than 1GB. Over time the amount of logs will grow and consume all available disk space. It is recommended that you delete them.

On Exchange LCR, CCR, and SCR servers, each storage group contains a subfolder that is named IgnoredLogs. For example, a server may use a path that resembles the following for a particular transaction log storage location:


Exchange uses the IgnoredLogs folder to store valid log files that cannot be replayed. For example, a log file might be outdated or corrupt. The IgnoredLogs folder may also contain the following subfolders:

Log files that accumulate in the IgnoredLogs subfolder are not automatically removed. Therefore, as the number of log files increases over time, available storage space on the storage location may be used up. This, together with typical transaction log generation could cause Exchange to stop processing messages.

To address this issue, delete the log files from the IgnoredLogs subfolder in the appropriate storage group.

For More Information

For more information about the Exchange 2007 continuous replication architecture and behavior, see the Microsoft blog article, Is this thing on? : Exchange 2007 - Continuous Replication Architecture and Behavior.

The content of each blog and its URL are subject to change without notice. The content within each blog is provided "AS IS" with no warranties, and confers no rights. Use of included script samples or code is subject to the terms specified in the Microsoft Terms of Use.

For more information about how to manage Exchange high-availability solutions, see the following topics: