Article ID: 823167 - Last Review: December 3, 2007 - Revision: 3.3 How to use the Eseutil utility to perform a checksum procedure on a streaming fileOn This PageSUMMARYThis article describes how to use the Eseutil utility to perform a checksum procedure on a streaming file in Exchange Server 2003. How To Use the Eseutil Utility to Perform a Checksum Procedure on a Streaming FileExchange 2003 uses a checksum procedure to confirm the data integrity of pages in the database. To perform a checksum procedure on a streaming file, you can use the Eseutil utility that is included in Exchange Server 2003. The Eseutil utility in Exchange 2003 includes a switch (/k) that you can use to verify the page-level integrity of the information store databases. The following optional command-line switches are associated with the /k switch:
Note The integrity check does not run a database recovery. If a database is inconsistent, or in a "dirty shutdown" state, Microsoft recommends that you perform a recovery operation to make sure that database operations are completed correctly. After you perform the recovery operation, you can use the Eseutil utility to perform the integrity check. For more information about disaster recovery, click the following article number to view the article in the Microsoft Knowledge Base: 326052
(http://support.microsoft.com/kb/326052/
)
White paper - Disaster recovery for Microsoft Exchange 2000 Server
Note Before you use the Eseutil utility, use Exchange System Manager to dismount the stores that you want to examine.To perform a checksum procedure on the streaming file, follow these steps:
Microsoft(R) Exchange Server Database Utilities
Version 6.5
Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating CHECKSUM mode...
Streaming File: C:\Program Files\Exchsrvr\MDBDATA\priv1.stm
(NOTE: only header pages will be validated)
File: C:\Program Files\Exchsrvr\MDBDATA\priv1.stm
Checksum Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|----|----|----|----|----|
...................................................
2 pages seen
0 bad checksums
0 uninitialized pages
0 wrong page numbers
1 reads performed
0 MB read
1 seconds taken
0 MB/second
20 milliseconds used
20 milliseconds per read
20 milliseconds for the slowest read
20 milliseconds for the fastest read
Operation completed successfully in 1.372 seconds. | Article Translations
|
Back to the top
