Export (0) Print
Expand All
Expand Minimize

Log files stored on network drive

[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: 2005-11-18

The Microsoft® Exchange Server Analyzer Tool queries the Active Directory® directory service to determine the value for the msExchESEParamLogFilePath attribute of each storage group object. This attribute specifies the location of the transaction log files used by databases in the storage group.

The Exchange Server Analyzer also queries Active Directory to determine the count of the entries listed in the homeMDBBL attribute of each mailbox store. The count of this attribute represents the number of mailboxes on the mailbox store.

If the Exchange Server Analyzer finds that the msExchESEParamLogFilePath attribute starts with \\ on an Exchange Server with more than 50 mailboxes, an error is displayed.

This error indicates that the transaction log files for a storage group are being stored on a network share. If the msExchESEParamLogFilePath attribute starts with \\, it indicates that the log file path uses a Universal Naming Convention (UNC) path. This is not a recommended practice because interruptions in network connectivity could cause transaction log and database errors, resulting in lost data or corrupt databases. It is recommended that you correct this problem as soon as possible.

  • Move the transaction logs from the network share to a local disk. For optimum performance, place all transaction logs on separate drives.

For information about how to move the transaction logs to another location, see the Microsoft Knowledge Base article 239944, "XADM: How to Move the Transaction or System Logs to Another Location" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=239944).

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

Community Additions

ADD
Show:
© 2014 Microsoft