Article ID: 886298 - Last Review: October 27, 2006 - Revision: 1.1 Advantages and disadvantages of decreasing the log checkpoint depth in an Exchange 2000 Server clusterINTRODUCTIONIn Microsoft Exchange Server, the Extensible Storage Engine (ESE) writes storage group database transactions to logs, and then the ESE writes storage group database transactions to the database. The maximum amount of data that the Extensible Storage Engine can write to logs before it writes to the database is known as the log checkpoint depth. You can decrease the log checkpoint depth setting on an Exchange Server computer in a clustered environment. This decrease causes better failover performance. However, this decrease may cause a performance penalty on disk resources and on CPU resources. MORE INFORMATIONWarning If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows 2000 Server, Microsoft Windows Server 2003, Microsoft Exchange 2000 Server, Microsoft Exchange Server 2003, or both Windows and Exchange. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes at your own risk.
On a computer that is running Microsoft Exchange 2000 Server in a clustered environment, the following behavior may occur:
In Exchange 2000 Server, the default log checkpoint depth is 20 megabytes (MB). Therefore, 20 MB of logs may have to be written to the databases before an Information Store shutdown is initiated. Therefore, the time that is required for the Exchange virtual server to move depends on the time that is required for the transaction logs to be written to the databases. By reducing the log checkpoint depth, you can reduce the write timings. By reducing the write timings, you reduce the failover times. To reduce the checkpoint depth, you must use the Active Directory Service Interfaces (ADSI) Edit utility to change the msExchESEParamCheckpointDepthMax attribute value in the Active Directory directory service. To apply the new settings, you must restart the Exchange Information Store service. To modify the checkpoint depth, follow these steps:
Note In an environment that has multiple domain controllers, you must wait for this attribute change to be replicated in Active Directory before you see the changes reflected on the Exchange 2000 Server computer. A reduction in the log checkpoint depth causes the Exchange Store Engine to write data to the databases more frequently. This behavior may cause disk and CPU performance penalties. Whether this behavior causes these performance penalties depends on your environment. A reduction of the checkpoint depth from 20 MB to 5 MB may cause a penalty of 5 percent on disk and CPU resources. REFERENCES
For additional information about how to monitor uncommitted checkpoint logs, click the following article number to view the article in the Microsoft Knowledge Base:
819771
(http://support.microsoft.com/kb/819771/
)
Update to monitor uncommitted transaction log files
| Article Translations
|
Back to the top
