tsm:tsm_exchange_sesutil
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
tsm:tsm_exchange_sesutil [2022/01/06 12:03] manu |
tsm:tsm_exchange_sesutil [2022/01/06 12:32] (current) manu |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Exchange integrity check ====== | ====== Exchange integrity check ====== | ||
| + | |||
| + | https://www.stellarinfo.com/blog/how-to-use-eseutil-for-exchange-database-repair/ | ||
| If you need to backup without integrity check, maybe your Exchange DB needs to be repaired ? | If you need to backup without integrity check, maybe your Exchange DB needs to be repaired ? | ||
| Line 24: | Line 26: | ||
| C:\Program Files\Microsoft\Exchange Server\V15\Bin\ | C:\Program Files\Microsoft\Exchange Server\V15\Bin\ | ||
| | | ||
| - | Step 3: Check Database State | + | ==== Step 1: Check Database State ==== |
| To identify the database state, use the /MH switch. If the state is displayed as Clean Shutdown, there shouldn’t be any issues and the database can be easily mounted after moving all the log files to a different location. | To identify the database state, use the /MH switch. If the state is displayed as Clean Shutdown, there shouldn’t be any issues and the database can be easily mounted after moving all the log files to a different location. | ||
| Line 33: | Line 36: | ||
| c:> eseutil /mh <database file name> | c:> eseutil /mh <database file name> | ||
| </cli> | </cli> | ||
| + | |||
| + | ==== Step 2: Check Logs ==== | ||
| + | |||
| + | If your database is in Dirty Shutdown, you will see another line under it, which mentions the log file that is required. The next step is to check if the logs are healthy or if there is a problem with the logs. To do this, use the ML prefix with EseUtil and the log path that you can copy from the Log Required section of the report. | ||
| + | |||
| + | <cli prompt='>'> | ||
| + | c:> eseutil /ml "M:\mbx01\logs" | ||
| + | </cli> | ||
| + | |||
| + | ==== Repair index ==== | ||
| + | |||
| + | **IsInteg** tool for Index Repair. IsInteg is a repair only utility that understands relation between tables and records and turns them into folders and messages. The tool is located at the following location, | ||
| + | |||
| + | C:\Program Files\Exchsrvr\bin> | ||
| + | |||
| + | Then run the IsInteg test by using the following command, | ||
| + | |||
| + | <cli prompt='>'> | ||
| + | c:> Isinteg –s <server_name> -fix –test alltests | ||
| + | </cli> | ||
| + | |||
| + | You may repeat the command multiple times to get rid of errors. Once errors are fixed, you can mount the database. | ||
| + | |||
| + | Further, you can use **New-MailboxRepairRequest**, if you have Exchange Server 2010 with SP1 or later versions, before mounting the database on the server. One more thing, you cannot stop the process once it started. If you stop it anyway, it may cause even more damage to the database. However, if all goes well, you will be able to mount the database. | ||
tsm/tsm_exchange_sesutil.1641466993.txt.gz · Last modified: 2022/01/06 12:03 by manu
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: GNU Free Documentation License 1.3
