Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in /home/servertools/public_html/blog/wp-content/themes/schema/schema/options/php-po/php-po.php on line 187
{"id":547,"date":"2016-03-28T03:42:28","date_gmt":"2016-03-28T03:42:28","guid":{"rendered":"http:\/\/www.stellarservertools.com\/blog\/?p=547"},"modified":"2020-12-11T09:19:45","modified_gmt":"2020-12-11T09:19:45","slug":"exchange-2010-2013-database-will-not-mount","status":"publish","type":"post","link":"https:\/\/www.stellarservertools.com\/blog\/exchange-2010-2013-database-will-not-mount\/","title":{"rendered":"Exchange 2013\/2010\/2007 Database is Not Mounting after Restore – Fixed!"},"content":{"rendered":"\n

Several reasons may cause Exchange not mounting issue in MS Exchange 2007, 2010, 2013, 2016 or 2019. In this guide, you will learn a few methods to fix the problem where the Exchange database doesn\u2019t mount after database restore.<\/em><\/p>\n\n\n\n

After restoring Exchange Server 2019\/2016\/2013\/2010\/2007 database from offline backup, you need to mount it to resume the email flow and client access. However, sometimes you may come across \u2018unable to mount database\u2019 error while mounting the restored Exchange database.<\/p>\n\n\n\n

Reasons for \u2018Database is Not Mounting\u2019 Issue<\/h4>\n\n\n\n
There could be various reasons that can cause Exchange database not mounting problem, such as:<\/p>\n\n\n\n
Exchange database is in dirty shutdown state<\/li>
Transaction log files are corrupt, missing, or deleted<\/li>
Database is corrupt<\/li>
Not enough free disk space on the server<\/li><\/ul>\n\n\n\n
You can resolve this issue by following the steps given below. However, if this doe not help or fails, you can always rely on a Exchange repair software, such as Stellar Repair for Exchange. Unlike Eseutil, the software is GUI based and does not require additional permissions, roles or storage space on the server. You can install the software on any system, scan and extract mailboxes from EDB and then save them to Outlook importable PST format. You can also export the mailboxes to a new or existing database on your live server in a few clicks.<\/p>\n\n\n\n
$\"\"$ <\/a><\/figure><\/div>\n\n\n\n
How to Resolve \u2018Database is Not Mounting\u2019 Issue?<\/h4>\n\n\n\n
Exchange not mounting is usually caused by database corruption. If log files are damaged, missing, deleted, or there is some discrepancy between the transaction logs and database files, the Exchange database enters into Dirty Shutdown <\/strong>state. And when the database is in a dirty shutdown state, you cannot mount it. In case you try, it will fail to mount the Exchange database.<\/p>\n\n\n\n
So, the first thing you need to do is to ensure there\u2019s enough storage space and then verify whether the Exchange database is in a clean shutdown state or not.<\/p>\n\n\n\n
For this, you can use the Eseutil<\/strong> command-line tool to examine the current state of the database and perform soft recovery<\/strong> and hard repair<\/strong> commands to repair the damaged or corrupt database.<\/p>\n\n\n\n
But before following the below steps, create a backup of Exchange EDB file.<\/p>\n\n\n\n
Step 1: Check Database<\/strong><\/p>\n\n\n\n
To check and verify the database\u2019s current state, use the following Eseutil command,<\/p>\n\n\n\n
`ESEUTIL \/mh <database name<\/code><\/pre>\n\n\n\nThe command will return the result of database\u2019s current state. If you find the database is in a dirty shutdown state, fix the dirty shutdown by using Eseutil command for Soft Recovery<\/strong> or Hard Recovery.<\/strong><\/p>\n\n\n\n`<\/figure>\n\n\n\nStep 2: Perform Soft Recovery by using Eseutil<\/strong><\/strong><\/h4>\n\n\n\nTo execute the soft recovery, it is mandatory to run the ESEUTIL \/r<\/strong> command from the folder in which the transaction log files exist. Also, use it only when the databases to be recovered are in their original path locations. The complete command is as follows,<\/p>\n\n\n\nEseutil \/r E00 \/l \u201cDrive:\\Exchange Server\\FirstStorageGroup\\Logs\u201d \/d \u201cdrive:\\Exchange Server\\FirstStorageGroup\\MbxStore1\\Mydatabase.edb\u201d \/i<\/code><\/pre>\n\n\n\nE00 specifies the log prefix of the transaction log file E00.log.<\/em><\/li> \/l and \/d specifies the log file and database location path. The log and the database location is \u2013 Drive:\\Exchange Server\\FirstStorageGroup\\<\/em><\/li>\/i switch in the command is used to resolve the streaming error that may occur during command execution.<\/em><\/li><\/ul>\n\n\n\nOnce the command is executed successfully, run eseutil \/mh again <\/strong>to verify if the database is in a clean state now. If it is, restart Exchange System Manager (ESM) and mount the database.<\/p>\n\n\n\n<\/figure>\n\n\n\nIn most cases, this solution works fine. But in case it fails, you can perform hard recovery on the database using Eseutil command<\/p>\n\n\n\n Step 3: Perform Hard Repair using Eseutil<\/strong><\/h4>\n\n\n\nThis process requires a lot of free storage space, almost two or three-times the size of the database. This is due to the temporary database that Eseutil creates before performing hard repair. So make sure you have enough space before executing hard repair command.<\/p>\n\n\n\n The command is as follows,<\/p>\n\n\n\n ESEUTIL \/p <database_file_location><\/code><\/pre>\n\n\n\nPress \u2018Enter\u2019<\/strong> to execute the command and start the hard repair. Once the process is completed, run the eseutil \/mh<\/strong> command to check the database state. It should be clean.<\/p>\n\n\n\n <\/figure>\n\n\n\nIMPORTANT NOTE: <\/em><\/strong>The worst thing about hard repair is that if it finds any damaged pages in the database, it will delete them. So make sure the database or data is not so important if you\u2019re going for a hard repair method because it may lead to additional data loss situations.<\/em><\/p>\n\n\n\n But there is a good alternative available of ESEUTIL.<\/strong><\/p><\/blockquote>\n\n\n\n <\/a><\/figure><\/div>\n\n\n\nHow to Fix the Database When ESEUTIL Fails?<\/h1>\n\n\n\nTo overcome the limitations of ESEUTIL and avoid hard recovery, it is always recommended to go for a professional Exchange database recovery tool such as Stellar Repair for Exchange<\/strong>. This Exchange database repair and recovery software fixes database (EDB) without any data loss.<\/p>\n\n\n\n Whether the database is corrupted, facing dirty shutdown issues, or even unable to mount, Stellar Repair for Exchange<\/strong> software is the permanent solution to fix all problems related to the Exchange server database.<\/p>\n\n\n\n This software doesn\u2019t make any changes in the original format of the database and repairs the severely corrupted Exchange EDB file while maintaining the data integrity. Also, it supports Exchange server 2007, 2010, 2013, 2016, and the latest version released in 2019.<\/p>\n\n\n\nTo know more, visit the official page to download the Stellar Repair for Exchange software<\/a>. In case you\u2019ve any query related to Exchange database, post your query in the comments section below.<\/p>\n","protected":false},"excerpt":{"rendered":" Several reasons may cause Exchange not mounting issue in MS Exchange 2007, 2010, 2013, 2016 or 2019. In this guide, you will learn a few methods to fix the problem where the Exchange database doesn\u2019t mount after database restore. After restoring Exchange Server 2019\/2016\/2013\/2010\/2007 database from offline backup, you need to mount it to resume the email flow and client access. However, sometimes you may come across \u2018unable to mount database\u2019 error while mounting the restored Exchange database. Reasons for \u2018Database is Not Mounting\u2019 Issue There could be various reasons that can cause Exchange database not mounting problem, such as: <\/p>\n","protected":false},"author":101011,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"amp_validity":null,"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/www.stellarservertools.com\/blog\/wp-json\/wp\/v2\/posts\/547"}],"collection":[{"href":"https:\/\/www.stellarservertools.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.stellarservertools.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.stellarservertools.com\/blog\/wp-json\/wp\/v2\/users\/101011"}],"replies":[{"embeddable":true,"href":"https:\/\/www.stellarservertools.com\/blog\/wp-json\/wp\/v2\/comments?post=547"}],"version-history":[{"count":7,"href":"https:\/\/www.stellarservertools.com\/blog\/wp-json\/wp\/v2\/posts\/547\/revisions"}],"predecessor-version":[{"id":1836,"href":"https:\/\/www.stellarservertools.com\/blog\/wp-json\/wp\/v2\/posts\/547\/revisions\/1836"}],"wp:attachment":[{"href":"https:\/\/www.stellarservertools.com\/blog\/wp-json\/wp\/v2\/media?parent=547"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.stellarservertools.com\/blog\/wp-json\/wp\/v2\/categories?post=547"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.stellarservertools.com\/blog\/wp-json\/wp\/v2\/tags?post=547"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}