![\"\"](\"https:\/\/www.kerneldatarecovery.com\/blog\/wp-content\/uploads\/2017\/06\/Database-mounting-error.jpg\")
<\/p>\n
Why is Exchange database shown in dirty shutdown state?<\/h4>\n
When the Exchange database cannot be mounted it is shown in dirty shut down state. One or more of these can be the reason:<\/p>\n
- \n
- EDB became inaccessible<\/li>\n
- Log files got damaged<\/li>\n
- Log files got removed<\/li>\n
- Miscellaneous other reasons<\/li>\n<\/ul>\n
You cannot guarantee that Exchange Servers will never fail, but as an IT manager you should always be ready to rise to the occasion and do your best to disentangle the mess. In this blog I am going to share with you a little secret on how you can do it in surprisingly easy way.<\/p>\n
When the Exchange database is not mounting, the way of recovery depends on the status quo, for example, you may have a good backup and good log files, there may be no backup at all or backup is corrupt but log files are fine, along with backup log files that are also corrupt. In most of these situations, using Exchange Server\u2019s native recovery tool \u2013 eseutil, you can solve the problem, however, if the problem is not solved you can use Exchange Server Recovery<\/strong> software to solve the problem. Here is how you do it:<\/p>\n
![\"Download](\"https:\/\/www.kerneldatarecovery.com\/blog\/wp-content\/uploads\/2018\/06\/dl-btn-new.png\")
<\/a><\/p>\nMake sure that the Exchange Server is working in flow.<\/p>\n
- \n
- Step 1:<\/strong> Locate the problem area \u2013 the folder on the Exchange Server in which the Exchange database file and log files are stored. Generally, the folder is located here:
\nC:\\Program files\\Microsoft\\Exchange Server\\v15\\Mailbox\\ Mailbox Database\\*.edb<\/code>
\nHowever, the location may vary if you have chosen some other place to store the log files. Generate a backup of the Exchange database and associated log files.<\/li>\n- Step 2:<\/strong> Stop the Exchange services and close the Exchange Server management console or ECP.<\/li>\n
- Step 3:<\/strong> Now rename the Mailbox database folder. For example, you can rename it to _old. If the folder containing the log files is different than the Mailbox Folder, rename that as well.<\/li>\n
- Step 4:<\/strong> Create a new folder with the name of the folder that you have just renamed. In the below image, old database folder is \u2018
Mailbox Database 0054972546_old<\/code>\u2019 and the new folder is \u2018Mailbox Database 0054972546<\/code>\u2019.![\"\"](\"https:\/\/www.kerneldatarecovery.com\/blog\/wp-content\/uploads\/2017\/06\/1.Create-a-new-empty-database-folder.jpg\")
<\/li>\n- Step 5:<\/strong> Start the Exchange services and open the Exchange Server Management console.<\/li>\n
- Step 6:<\/strong> Now right click on the Database folder in the Exchange Server management console and click mount. It will ask to create a new, empty database. Click OK.But before that, you can ask the users to copy the existing, old data from the email clients, because on mounting the new, empty database, data on the email clients will be refreshed and disappear. Or, you can ask the users to configure a new profile in the email client. In this way a backup copy of data will be saved. However, as you have already created a backup of the EDB file, this step is only for extra precaution.
\n![\"\"](\"https:\/\/www.kerneldatarecovery.com\/blog\/wp-content\/uploads\/2017\/06\/2.-Create-a-new-empty-Exchange-Server-database.jpg\")
\nAfter this step, the exchange will start running and all the mailboxes will become accessible but will be empty. Now when you open the folder, you will find the new, empty Exchange Server database inside it. Now comes the important part \u2013 restoring data from old, corrupt database to the empty mailboxes.<\/li>\n- Step 7:<\/strong> Install and launch the application (Exchange Server Recovery<\/strong>). Locate the old, corrupt database which must be in the renamed folder (as we did in step 3).Include the required database in the application. Data will be recovered and displayed in an Outlook like GUI. In the following image, recovered data from the old Exchange Database File is seen with all the mailboxes in it, and the last mailbox is expanded to show all the folders in it.
\n![\"\"](\"https:\/\/www.kerneldatarecovery.com\/blog\/wp-content\/uploads\/2017\/06\/3.Preview-of-the-recovered-Exchange-mailboxes-in-LERM.jpg\")
<\/p>\n\n<\/li>\n
- Step 8:<\/strong> Add the Live Exchange Server to the application. You will be able to see the new, empty EDB after the Exchange Server is added to the application. In the following image, the EDB can be seen at the root and the mailboxes are under it which are empty.
\n![\"\"](\"https:\/\/www.kerneldatarecovery.com\/blog\/wp-content\/uploads\/2017\/06\/4.Empty-mailboxes-in-destination.jpg\")
<\/li>\n- Step 9:<\/strong> Right-click on the old EDB in the source pane and select \u2018Copy All Mailboxes\u2019 option from the context menu.
\n![\"\"](\"https:\/\/www.kerneldatarecovery.com\/blog\/wp-content\/uploads\/2017\/06\/5.Select-copy-all-mailboxes-in-source.jpg\")
<\/li>\n- Step 10:<\/strong> Right click on the Live Exchange Server in the destination pane and select \u2018Paste All Mailboxes\u2026\u2019 option.
\n![\"\"](\"https:\/\/www.kerneldatarecovery.com\/blog\/wp-content\/uploads\/2017\/06\/6.Paste-all-mailboxes-in-destination.jpg\")
\nAfter that \u2018Migrate all mailboxes\u2019 wizard will start. You will get the option to select which mailboxes you want to migrate and what data you want to migrate based on date.<\/li>\n- Step 11:<\/strong> Source mailboxes will be automatically mapped folder wise to the destination mailboxes. If a match is not found, you can map the source mailbox to any other existing target mailbox.\n
![\"\"](\"https:\/\/www.kerneldatarecovery.com\/blog\/wp-content\/uploads\/2017\/06\/7.Map-source-and-target-mailboxes.jpg\")
<\/p>\n<\/li>\n- Step 12:<\/strong> Once the mapping is complete, begin the migration by clicking on the start button. As the migration progresses, you will see its status on the application\u2019s console. Finally, after all the mailboxes are migrated, you can see its report by clicking the \u2018Generate Reports<\/strong>\u2019 button. In the following image, the report is shown in a grid.
\n![\"\"](\"https:\/\/www.kerneldatarecovery.com\/blog\/wp-content\/uploads\/2017\/06\/8.Mailbox-migration-report.jpg\")
<\/li>\n<\/ul>\nAfter this, users will be able to see their emails in the Outlook client, and normal email services will be restored.<\/p>\n
Conclusion<\/h4>\n
The cmdlets to mount the database back to Exchange Serve do not assure that it will safely complete the process. Exchange Server Recovery<\/a> software will restore the Exchange database to the Server with all the mailboxes and the data present. The software does not require any backup, log file, or transaction log to recover the items. As convert EDB to PST<\/a> tool did for Mr Krish.<\/p>\n
- Step 2:<\/strong> Stop the Exchange services and close the Exchange Server management console or ECP.<\/li>\n
- Step 1:<\/strong> Locate the problem area \u2013 the folder on the Exchange Server in which the Exchange database file and log files are stored. Generally, the folder is located here: