Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

.edb on the shutdown server


  • Please log in to reply
4 replies to this topic

#1 petursson

petursson

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:02:15 PM

Posted 26 March 2017 - 10:46 AM

Hello!

I have 2 storage groups on the exchange server which is in a state of dirty shutdown. The second group is not connected because of incorrect completion. The database is stored on drive E, and transaction logs are on the C drive. 

 

C:\Program Files\Microsoft\Exchange Server\Mailbox\Second Storage Group

 

I tried to run eseutil /mh e:\exdb2 but I get an error saying that the file is locked.

What is the exact command I need to run to repair the .edb?



BC AdBot (Login to Remove)

 


#2 petursson

petursson
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:02:15 PM

Posted 28 March 2017 - 11:59 AM

guys, any idea on this problem?



#3 breslin

breslin

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:02:15 PM

Posted 29 March 2017 - 10:20 AM

First you need to stop your Information Store service and back up everything (edb, stm, and log files) to a different disk. You must ensure that you have sufficient amount of free disk space. 
Now, follow the steps given below to get your database back to the clean shutdown state:

Initially, run the following command to verify your database consistency:

    eseutil /mh "c:\program files\exchsrvr\mdbdata\priv1.edb"

If you find the database state to be 'Dirty Shutdown', perform a soft repair using the below command: 
    eseutil /r "c:\program files\exchsrvr\mdbdata\priv1.edb"

This command replays the transaction log files to make sure that all the database operations are successfully completed.
Perform a hard repair of your database using 'Eseutil /p' as follows: 
   eseutil /p "c:\program files\exchsrvr\mdbdata\priv1.edb"

Defrag your database stores by using the 'Eseutil /d' command-line utility.
Finally check the database integrity by running the 'Isinteg' utility from the BIN folder as follows: 
    'isinteg -s servername -fix -test alltests'



#4 breslin

breslin

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:02:15 PM

Posted 29 March 2017 - 10:23 AM

There is also the possibility to use third-party tools such as Exchange Server Recovery Toolbox. It can also help in your problem. Try to Use all the tools and some of them should help. You can type in a Google query “exchange server recovery tool to recover damaged edb files”. http://www.oemailrecovery.com/exchange_server_recovery.html

Please also refer following Microsoft's support article for same.
http://support.microsoft.com/kb/896143#3  



#5 petursson

petursson
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:02:15 PM

Posted 29 March 2017 - 01:27 PM

You've been very kind in your efforts to help. Thanks for that. 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users