最後更新: 20160910

MODES OF OPERATION:

• Defragmentation:  ESEUTIL /d <database name> [options]
• Recovery:  ESEUTIL /r <logfile base name> [options]
• Integrity:  ESEUTIL /g <database name> [options]
• Checksum:  ESEUTIL /k <file name> [options]
• Repair:  ESEUTIL /p <database name> [options]
• File Dump:  ESEUTIL /m[mode-modifier] <filename>
• Copy File:  ESEUTIL /y <source file> [options]
• Restore:  ESEUTIL /c[mode-modifier] <path name> [options]

Offline defrag it

(You will have to dismount the datastores)

eseutil /d c:\progra~1\exchsrvr\mdbdata\priv1.edb

Defragmentation:

Eseutil creates a new database that contains all the information in the original database. When defragmentation is complete, the original database is deleted or saved to a user-specified location, and the new version is renamed as the original. If the tool encounters a bad record, it stops and displays an error message.

Eseutil offline defragmentation should not be run as any kind of standard maintenance. Exchange runs an automatic online defragmentation nightly that handles the day-to-day maintenance of Exchange. For day-to-day, month-to-month, or year-to-year maintenance, there is no reason to run an offline defragmentation.

Eseutil defragmentation should not be run when the database is not in a consistent state.

For example, defragmenting a 100-gigabyte (GB) database containing 10 GB of data takes about the same time as defragmenting an 11-GB database containing 10 GB of data.

Repair

# log generation prefix of E02 ( the file name of check file )

eseutil /r E02 /l "C:\RecoveryDB\Logs" /d "C:\RecoveryDB\File"

opts:

• /l        # Transaction log files are not in the current folder
• /d       # If the /D switch is used without a path, then the current directory will be used as the path for the database files.

OR

CD DB_FOLDER
ESEUTIL /R Enn /I /D

Hard recovery: A transaction log replay process that occurs after restoring a database from an online backup.

Soft recovery: A transaction log replay process that occurs when a database is re-mounted after an unexpected stop,
                     or when transaction logs are replayed into an offline file backup copy of a database.