138 CHAPTER 4 UNDERSTANDING EXCHANGE 2003 DATA STORAGE mailboxes each, I suspect that this will happen more frequently with Exchange 2003. I have heard of this happening on really busy Exchange 2003 servers. The good news is that you can reset the log file generation. I usually take this opportunity to perform an offline defragmentation on all the stores in a storage group at the same time. For a server that is supporting 5,000 mailboxes, this will take more than a few minutes. Here is a procedure you can use to reset the log file generation: 1. Perform a normal (full) backup of the entire storage group. 2. Dismount all the stores in the storage group. 3. Optionally, use the ESEUTIL utility with the /D option to perform an offline defragmentation/ compaction of each store in the storage group. 4. Move all of the log files that begin with E*.LOG for that particular storage group, and move the checkpoint file. These files should be moved out of the production log directory into a temporary holding spot until you are sure that the stores are mounted and working properly with their new logs. 5. Remount all of the stores in that storage group. 6. Perform a normal (full) backup of the entire storage group, as now your previous backups will no longer be usable with the new generation of log files. Ta da! You have reset your log file generation. This did require downtime for every information store in the entire storage group. An alternative to resetting the log file generation in this method is to create a new storage group, create new mailbox stores in that storage group, and then move the mailboxes to the new mailbox stores. If minimal disruption to your user community is important, this may be a better (though time-consuming) approach. NOTE Exchange 2003 will cleanly shut down the stores prior to running out of log file numbers and issue a warning to the event logs. Prior versions of Exchange did not always shut down cleanly when this happened. Viewing Advanced Log File Information You can learn some revealing information from each log file by using the ESEUTIL command. The ESEUTIL command with the /ML option will dump the header information from the log file. The following is the result of the ESEUTIL /ML command: Microsoft(R) Exchange Server Database Utilities Version 6.5 Copyright (C) Microsoft Corporation. All Rights Reserved. Initiating FILE DUMP mode… Base name: e00 Log file: e00003a7.log lGeneration: 935 (0x3A7) Checkpoint: (0x3A8,16D5,3F) creation time: 12/11/2005 22:27:28 prev gen time: 12/11/2005 22:26:33 Format LGVersion: (7.3704.8)

Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost Low Cost Web Hosting services

Bookmark the permalink.

Comments are closed.