Restore Mailbox Database in Exchange 2016

Share This Article: Share on Facebook0Share on Google+0Tweet about this on TwitterShare on LinkedIn0Pin on Pinterest0Email this to someone

Mailbox Database is a critical part of Exchange infrastructure. Sometimes mailbox database can get corrupted for some reason. For Exchange admin it can be a nightmare when mailbox database fails. There are different ways to recover mailbox database. You can recover the volume where databases are stored or you can recover single database instead of recovering all available database. Similarly, you also have option of recovering standalone Exchange server. You can use Windows Server Backup to restore mailbox database in Exchange 2016.

Restore Mailbox Database in Exchange 2016

Scenario: Exchange server is working fine, but for some reason the databases doesn’t mount. After digging a little bit, you find that the drive where mailbox databases are stored have crashed. Here we can recover all mailbox databases from the backup. You can use this method if the volume where database were stored have now crashed. This method is also used if Exchange server have just been recovered using /RecoverServer switch. In the scenario, we have Exchange server (MBG-EX01) with two databases in D drive and transaction logs in E drive. The D drive has failed and is replaced with fresh new drive. Now we need to recover database to this new D drive from the old backup. The latest full backup ran by Windows Server Backup is stored in backup drive.

Log on to MBG-EX01. Open Windows Server Backup application.

recover

Right-click Local Backup and click Recover.

Restore Mailbox Database in Exchange 2016

Choose the location where backup is stored. In this case it is stored in this server in backup drive. Choose This server and click Next.

choose available backup

Choose available backup. You can see the details of the backup as shown above. The date, time, location status and recoverable items. You can click on recoverable items link to view details of recoverable items.

recoverable items

As you see above selected portion is two different mailbox database. You can verify by type following cmdlets in EMS.

[PS] C:\Windows\system32>Get-MailboxDatabase | fl name, guid
Name : Mailbox Database 2095368010
Guid : 6eb8962a-778f-4b24-a254-1be7e60d1986

Name : DB01
Guid : 3917761b-6267-4379-9ce9-efe045ebc03a

In the Select Backup Date page, select the available backup above and click Next.

applications recovery type

In the Select Recovery Type page, choose Applications and click Next. You can also choose Volumes which will recover the drive. But with applications you have option of roll forward.

select application

In the Select Application page, select Exchange. You can click View Details to view database information as shown above. These two databases will be restored. By default Exchange server will try to roll forward by committing all uncommitted transaction logs. Remember we have transactions logs in E drive, we are recovering D drive. So after the failure of D drive, new emails are stuck in transaction logs in E drive. So to let these emails go to mailboxes we need to roll forward the application database. So uncheck the option and click Next.

recovery option

In Specify Recovery Options page, choose recover to original location option. Click Next.

restore confirmation

Review the confirmation page. Click Recover.

recovery completed

The recovery progress will begin. Click close after it is completed. Now let’s verify if the database is mounted. Get-MailboxDatabaseCopyStatus can be used to know about database status as shown below.

[PS] C:\Windows\system32>Get-MailboxDatabaseCopyStatus | fl name, status, contentindexstate

Name              : Mailbox Database 2095368010\MBG-EX01
Status            : Mounted
ContentIndexState : Healthy

Name              : DB01\MBG-EX01
Status            : Mounted
ContentIndexState : Healthy

As you can see above the database is mounted and is healthy. In this way you can recover mailbox database using Windows Server Backup application.

The following two tabs change content below.
Bipin is a freelance Network and System Engineer with expertise on Cisco, Juniper, Microsoft, VMware, and other technologies. You can hire him on UpWork . Follow Bipin Giri on Google+. Bipin enjoys writing articles and tutorials related to Network technologies. Some of his certifications are, MCSE:Messaging, JNCIP-SEC, JNCIS-ENT, and others.