Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 32
  • Last Modified:

how to troubleshoot log file or database corruption in exchange 2010

Hello Experts,

Can you guys please give some helpfull suggestions as to what to do if one of the log files is corrupt or missing causing the database to be in an unmounted or unhealthy state? what if the database is corrupt, or is not mounting for whatever reason? any helpfull tips/ advise to go about troubleshooting these two issues will be really appreciated.
1
Newguy 123
Asked:
Newguy 123
1 Solution
 
BusbarSolutions ArchitectCommented:
move all the logs to a new location, and try to mound the DB.
0
 
Manuel FloresCommented:
Try what Busbar suggest, just get rid of that logfiles.

If it doesn't mount, maybe you datastore is in a inconsistent state.  You can try the ESEUTIL command in repair mode.  Depends on the datastore size it could last several hours.

Make copies of everything before proceeding.

Some further reading about ESEUTIL;  https://blogs.technet.microsoft.com/exchange/2004/06/18/repairing-exchange-databases-with-eseutil-when-and-how/
0
 
Ajit SinghCommented:
Before attempting to repair a database, you must verify that it is dismounted and also verify that your Exchange 2010 database has been backed up before repairing.

1) dismount the database 2) shut down exchange services 3) run Eseutil /mh 4) run Eseutil /d 5) delete all of the transaction log files 6) restart exchange services 7) mount the database 8) run the backup jobs on the exchange store and server.

If the log file that's damaged is one that contains only committed transaction then it isn't needed to bring the database back to a consistent state after you dismount that database.
 
Assuming you have only one database in the storage group, if the "eseutil /mh" shows the dtabase to be in a consistent state you can move (don't copy) all the log files and the chk file to another directory and remount the database. That will start a new log file generation. Make a backup of the storage group as soon as you can. Once you're happy the backup is okay and things are running okay you can remove those old log and chk files.

To get in more detailed please refer to below informative resources:

Exchange Database Recovery – Using eseutil commands: http://msexchangeguru.com/2009/07/12/exchange-database-recovery-using-eseutil-commands/

Repairing a corrupt or dirty exchange database: https://community.spiceworks.com/how_to/2217-repairing-a-corrupt-or-dirty-exchange-database

Also check this earlier thread i.e. Exchange 2010 Logs corrupt: https://www.experts-exchange.com/questions/26696928/Exchange-2010-Logs-corrupt.html

Hope this helps!
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now