Get Even More Visitors To Your Blog, Upgrade To A Business Listing >>

Restoring Exchange Server Database from a Storage Failure (Database is not Mounting)



We all know ‘unable to mount Exchange database’ is the most frequent and common issue faced by Exchange administrators, and database restoration is the last option to get rid of it. However, below are the possible options to get the problem resolved when database storage fails:

    A good and updated Exchange backup is available.

    Exchange database is down.

     Mounting a new or blank or empty database with the messaging kept active until the database is repaired.

    Performing a soft-recovery and fixing the database.

    Opting for a professional Microsoft Exchange Server recovery software.

Let’s now discuss each option to restore the Exchange server database in a step-by- step process:

1. A Good and Updated Exchange Backup is Available 

If you find yourself in the midst of such a situation, the first thing you need to check is whether there is an updated backup on the server. Go for the best Exchange Server backup software to restore the Exchange database from the backup with minimal downtime, but ensure that the live data is retained on the existing storage drive. Once you’ve restored the database from the backup, create a recovery database and repair the failed database and combine it with your process.

But before restoring the database using Exchange backup software, create a copy of the database or just rename it. Using the database without even copying or renaming can override the database file on existing storage drives.

2. What if No Backup is Available and Exchange Database is Down 

If a backup is not available, you then need to verify the health of the database. Because you don’t have any backup copy of the database, and the size is very large (approximately 8-10 GB), it will take several hours to run a successful repair. So firstly, make a copy of the database (if the backup is available) so that if the repair job is interrupted in the middle of the process, you can restart the job with the saved backup copy.

Let’s now examine the health of database:

Open PowerShell and locate the default location of Eseutil.exe. If you couldn’t find the utility, open the following folder location by navigating to the path:

C:\Program Files\Microsoft\Exchange Server\V15\Bin

Next, run the below command to check the health of database:

.\eseutil.exe /mh "D:\log files\Mailbox Database\DB1.edb"

(I) If database is healthy and showing a Clean Shutdown state:

The database still can’t be mounted back to the server because it isn’t able to read and understand current log files sequence. So you need to delete all those log files and then mount the database. Exchange server will generate new log files for the database and mount the database successfully.

(II) If database is showing in Dirty Shutdown State

3. Mounting a new or blank or empty database with the messaging kept active until the database is repaired.

Follow the steps below:

         i.            Stop Microsoft Search Service and Search Host Controller Service:

 


This post first appeared on Exchange Timeline, please read the originial post: here

Share the post

Restoring Exchange Server Database from a Storage Failure (Database is not Mounting)

×

Subscribe to Exchange Timeline

Get updates delivered right to your inbox!

Thank you for your subscription

×