Export (0) Print
Expand All
Expand Minimize

The IgnoredLogs folder contains more than 1 GB of accumulated log files

[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at http://go.microsoft.com/fwlink/?linkid=34707.]  

Topic Last Modified: 2010-04-01

The Microsoft Exchange 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:

  • Local Continuous Replication (LCR)

  • Cluster Continuous Replication (CCR)

  • Standby Continuous Replication (SCR)

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:

E:\TransactionLogs\StorageGroup1\IgnoredLogs\

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:

  • E00OutofDate

    This subfolder contains old E00.log files that were present on the passive node at the time of failover. An E00.log file is created on the passive node if the node was previously running as an active node. When these log files are moved to the E00OutofDate subfolder, event ID 2013 is logged in the Application log.

  • InspectionFailed

    This subdirectory contains log files that have failed inspection. Event ID 2013 is logged when a log file fails inspection. Then, the log file is moved to the InspectionFailed folder. The log file inspector uses the Eseutil tool together with other methods to verify that a log file is physically valid. Any exception that is returned by these examinations is considered as a failure result, and the log file is considered to be corrupted.

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 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.

noteNote:
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:

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft