Article ID: 258470 - View products that this article applies to.
This article was previously published under Q258470
This article describes how to modify the circular logging setting on a Microsoft Exchange 2000 Server computer. The following topics are discussed:
Description of Circular LoggingIn the standard transaction logging used by Exchange 2000 Server, each database transaction in a storage group is written to a log file and then to the database. When a log file reaches a certain size, it is renamed and a new log file is created. Over time, this results in a set of a log files. If there is a crash, you can recover the transactions by replaying the data from these log files into the database.
Circular logging overwrites and reuses the first log file after the data it contains has been written to the database. In Exchange 2000 Server, circular logging is disabled by default. By enabling it, you reduce drive storage space requirements, but without complete transaction log files, you cannot recover anything more recent than the last full backup. Therefore, in a normal production environment, circular logging is not recommended.
How to Enable or Disable Circular LoggingExchange 2000 Server supports multiple databases and storage groups on the same server. You can create up to four storage groups on a server and each storage group can contain up to five databases, for a maximum of 20 databases on a single server. Each storage group is controlled by a separate instance of the Extensible Storage Engine (ESE). Therefore, each storage group shares the same set of log files. As a result, circular logging is enabled or disabled for a particular storage group, not for a particular database.
To enable or disable circular logging: