How to Mount / Dismount Database in Exchange 2019, 2016, 2013, 2010
Summary: It is a common activity for Exchange administrators to mount dismount database in Exchange 2019, 2016, 2013, 2010. These tasks are usually performed while running maintenance or health checks of Exchange Server. However, if mounting or dismounting is not performed in a systematic manner, then it throws various error messages and can lead to downtime. Thus, we have provided a step by step guide for the same.
The main repository file of Microsoft Exchange Server is the EDB file that it uses to store user mailbox data as well as public folders. This file is mounted to Exchange Server and the mailboxes are only accessible if the EDB file is mounted to Exchange Server.
However, there are some scenarios when an Exchange administrator has to dismount the database from Exchange Server. Usually, the database is dismounted from Exchange Server in case of performing maintenance tasks such as performing integrity checks, defragging the Exchange database, etc.
Although it is a safe task to perform, still many users face issues and errors while mounting or dismounting databases in Exchange 2010, 2013, 2016, and 2019. Thus, in this article, we are providing a detailed guide on how to carry out the entire process in a safe manner.
Steps to Mount and Dismount Database in Exchange Server
If you have admin access on your account, then you use the Exchange Admin Center to perform this task. However, you must note that you can only dismount or mount only single Exchange database at a time.
How to Dismount Database in Exchange 2019, 2016, 2013 & 2010
1. Click on the Servers > Select databases > Click on the Exchange database that you want to dismount.
2. Click on the “…” button > Select the dismounted option.
3. Select the Yes button to confirm.
4. Finally, your mailbox database is dismounted successfully.
How to Mount Exchange Database
1. In EAC, select the Exchange database that you want to mount > Click on the “…” button > Select the mount option.
2. Click on the Yes button to mount the mailbox database > Then, your Exchange database is successfully mounted.
Note: In EAC users can only mount or dismount mailbox database Exchange one at a time and it makes this method slower as compared to Exchange PowerShell.
Although the Mount / Dismount process is simple to perform using Exchange Admin Center, there are certain shortcomings associated with it. One drawback is that it will only Mount / Dismount a single database at a time. This means that if you want to implement the same process for multiple databases, this will take a lot of time.
Thus, if you need a quick solution, then you can go with the PowerShell cmdlet to get the job done.
Mount / Dismount Database in Exchange Using PowerShell
This method is best suited if you have multiple Exchange databases to handle and want to execute the process in an efficient manner. However, you need to have complete technical knowledge of running PowerShell commands to perform the task.
Mount Exchange Database Using PowerShell cmdlet
This is a step-by-step process and needs to be performed in a systematic manner. Please make sure that you execute all these steps to have an error-free experience.
Step 1: Assign Required Roles
To dismount or mount database in Exchange Server 2019, 2016, 2013, or 2010, you need to have a database role assigned to your account. If you are an administrator, then this role is by default assigned to you. However, if you don’t have administrator access, then you need to assign this permission.
Run this command to assign this role:
New-ManagementRoleAssignment –role Databases –User Jaspreet
Step 2: Identify the Database Name
You should also know the name of the Exchange database. You can either use Exchange Admin Center or PowerShell command for it.
In Exchange Admin Center:
- Open EAC and then go to Servers >> Databases.
In PowerShell cmdlet:
Get-MailboxDatabase
Step 3: Verify Database Status
It is essential to first check status of the database before mounting it to Exchange Server. You can use the below-mentioned procedure for the same.
You can use the Get-MailboxDatabase and Format-Table parameter to get the desired details.
Get-MailboxDatabase –Identity <database name> -Status | Format-Table Name, BackupInProgress, OnlineMaintenanceInProgress
You can also check the status of all databases in one go using the –Server parameter.
Get-MailboxDatabase –Server <server name> -Status | Format-Table Name, BackupInProgress, OnlineMaintenanceInProgress
Along with this, you also need to check if the database is in healthy state or not. You can use the eseutil /mh command for the same.
eseutil /mh <full path to the edb file>
Once you run this command, you will either get a clean shutdown state or an Exchange Database Dirty Shutdown state.
In case of dirty shutdown, you need to fix it first before trying the mount the database.
Important Note: If you are facing corruption issues in the Exchange database file and unable to mount Exchange database, then you must try this Exchange Database Recovery Tool. This software is extensively tried and tested by experts and helps users repair EDB files without any data loss.
You can download this application on Windows OS and perform recovery in a hassle free manner.
Once the database is in healthy state and you know the database name and status, you can now mount the Exchange database.
The PowerShell command to mount database in Exchange Server is:
Mount-Database –Identity <database name> –Confirm:$False
This command will mount the specified database without confirmation.
Furthermore, you can also use the following command if you have multiple Exchange databases to mount.
Get-MailboxDatabase –Server | Mount-Database –Confirm:$False
You can also use the PowerShell cmdlet to dismount Exchange Server database as described below:
Dismount-Database –Identity <database name> –Confirm:$False
Conclusion
Mounting and Dismounting a database in Exchange 2019, 2016, 2013, and 2010 is not a complex task if performed by following proper steps. However, there are chances of getting errors if the Exchange DB file is not in healthy state. Thus, you should have a detailed knowledge of the entire process to make the job effortless.