Live Chat
Home » Blog » Exchange Server » How to Restore Exchange Database To Different Server? Get the Solution
Exchange Server

How to Restore Exchange Database To Different Server? Get the Solution

  author
Published By Mohit Jha
Tej Pratap Shukla
Approved By Tej Pratap Shukla
Published On April 3rd, 2024
Reading Time 8 Minutes Reading

Summary: Have you ever wondered how to restore Exchange database to different server? If yes, then this write-up helps users and provides the complete solution to restore the mailbox database to the new server via manual and advanced solution without any loss of data or corruption.

Nowadays the existing Exchange Server is being upgraded or replaced by the new one because Microsoft is upgrading their servers day by day. It incorporates unique services, security, advanced features, etc… which makes the Exchange users/administrators work a lot easier.

If you are working on the older version of MS Exchange Server and want to upgrade to the new one, in that case, users will need to restore & mount the mailbox database to the new server.

By reading this write-up, users can easily move & restore Exchange database to a new server. With minimum outage. This article also helps users restore the corrupt offline/dismounted EDB to the new server.

Before moving towards the solution, first have a quick brief about the Exchange database downtime scenario.

Overview Of Exchange Downtime While Recovering the EDB to A New Server

This situation arises when the Microsoft Exchange Server comes across failures, has network connectivity or database issues, shutdowns, etc… It disconnects all the Exchange user’s mailboxes and disrupts the entire email flow/communication. All this occurs in the mailbox database restore process.

Note: It is suggested to perform the database restore job after working hours in order to avoid the downtime in the business.

However, to avoid the disruption and complexity that users face in restoring the mailbox database to a new server, users can use the Exchange EDB Repair Tool. This recovery manager for Exchange database utility helps users in repairing the Exchange mailbox & EDB files.

Manual Methods to Restore Exchange Database to Different Server

Follow the solutions given below to restore the Microsoft Exchange mailbox database to the new server

Solution 1: Use the Database Portability Method

Database Portability is the MS Exchange Server feature that enables the administrator to migrate, mount, or move the Exchange database to different server in an easy way. This feature is available in Microsoft Exchange 2019, 2016, & 2013 and it reduces overall recovery times.

It is the easiest way to move the Exchange database to a different server. This solution helps users quickly migrate the mailbox database from the existing or old server with minimum downtime.

With the help of this method, users can move the Exchange database from one server to a new one in the same organization. The new Exchange Server should have the same database schema as the previous one. Also, note that users cannot move the mailbox database from the previous versions to the running Exchange Server such as 2016 or 2019.

Important Point: To restore Exchange database to different server, you need to make sure that the source & target Exchange Server are running on the same version and OS (Operating System).

Things to Know Before You Begin to Recover Exchange Database

  1. Users cannot use the Exchange Admin Center to move the Exchange user mailboxes to the recovered or dial tone database via database portability.
  2. You have to assign the permission to perform this procedure. To see what kind of permission you need, check the mailbox recovery in the recipient’s permissions.

Follow the Steps Given Below:

Step 1. Make sure that the state of database should be in Clean Shutdown. If the mailbox database is not in a clean state then you have to perform soft recovery by running the eseutil /r cmdlet.

Syntax:

eseutil /r <enn>

Output:

repair edb

Step 2. Then create the database on the server by using the command given below:

New-MailboxDatabase -Name  -Server  -EdbFilePath  -LogFolderPath

Step 3. Now use the Exchange Management Shell command given below to “set database can be over written by restore attribute”.

Set-MailboxDatabase  -AllowFileRestore $true

Step 4. Then move the actual database files like – log files, Exchange Search catalog and .edb file.

Step 5. After that mount the Exchange database use the cmdlet given below:

Mount-Database

Step 6. Then, users have to move the old database to the new one

Get-Mailbox -Database  |where {$_.ObjectClass -NotMatch '(SystemAttendantMailbox|ExOleDbSystemMailbox)'}| Set-Mailbox -Database

Step 7. After that, use the command to trigger the delivery of any remaining message

Get-Queue  | Retry-Queue -Resubmit $true

After the successful completion of AD (Active Directory) replication service, now all users can easily access the mailboxes to the New Exchange Server

Issues with Database Portability Solution

  1. It is a time-consuming method and users should have the technical knowledge & skill to use the manual solution
  2. Users have to perform soft repairs to bring back the database in a clean state
  3. The AD (Active Directory) and the re-submission of queue messages increases the downtime

Also Read: How to take backup of Exchange mailbox?

Solution 2: Use WSB (Windows Server Backup) to Recover Exchange Database

On recent server, users have to use the Windows Server Backup to create the database backup that you want to restore the new server. When done, follow the steps given below to the new server:

On a recent server, users have to use the Windows Server Backup to create the database backup that they want to restore to the new server. When done, follow the steps given below to restore Exchange database to different server. 

  • Step 1. Open the WSB >> Click on the Action tab >> Select the recover button
  • Step 2. On the recovery wizard page >> Select the server from the radio button >> Click on the Next button
  • Step 3. Then set the location path >> After that specify the shared folder path >> Click on the Next button
  • Step 4. Select the date & time to restore the Exchange database >> Click on the Next button
  • Step 5. Select the recovery type>> Click the Next button
  • Step 6. Then, on the application page, verify that the Exchange is selected in the application >> Click next
  • Step 7. Set the location where you want to restore the Exchange database on the specified recovery options page >> Click on the Next Button
  • Step 8. Verify all the settings on the confirmation page >> Click the Next button
  • Step 9. When the process is completed >> Click on the close button.

Note: If the restored database is in dirty shutdown state, then users have to perform Exchange database hard repair or soft repair by using the ESEUTIL command.

If you want to verify whether this solution has worked or not, go to the directory where you have restored the Exchange database and see if it exists. Users can also check the Windows Server backup log files to verify the job status.

Optimum Solution to Restore Exchange Database to Different Server

The Database Portability method has its drawbacks and on the WSB (Windows Server Backup) solution users have to first create the backup data to import it on the new server. However, in this solution, there is a need for the recent EDB file and the working server within the same organization and in the same forest.

If users want to restore Exchange database to a new server when it is in an offline or dismounted state, then in this case this solution doesn’t work. For this, users can use the advanced Exchange EDB Repair Tool used by many IT Experts, Exchange, and novice users to add the offline EDB to the Live Exchange Server mailboxes.

Download Now Purchase Now

Any technical and non-technical can use this utility as it provides a graphical user interface which makes the user’s work a lot easier and saves their time as well as effort. It provides a scan mode option i.e. Quick & Advance scan which recovers &  repair corrupt Exchange mailbox as well as mailbox database without any loss of data in a hassle freeway.

After recovery, users can easily extract the healthy and recovered mailboxes to export them directly into the Exchange Server, Office 365, and multiple file formats.

Bringing It All Together

Restore Exchange database to different server is not a piece of cake. Users can use the manual solution to restore the mailbox database from the existing server to the new one. Still, it is advised to use the automated wizard given in the above section. It can easily recover the minimal and severely corrupted offline/dismounted Exchange database. Additionally, it can export it to the Live Exchange Server in a simplified way without any interruption.

Frequently Asked Questions

Q1. How do we move from one Exchange database server to another server?

Ans – By using the Database portability, you can move or mount the database to a different server.

Q2. How to check Exchange database health using PowerShell?

Ans – Execute the below command to know the status of the Exchange database.

 Get-MailboxDatabase -Status | Format-List name, server, mounted

Q3. How to recover Exchange database 2016 to different servers?

Ans – You can use the above-mentioned automated EDB Repair tool to restore the Exchange database 2016, and the below versions as well.

Q4. Is the database portability an effective solution to restore Exchange database to different server?

Ans – No, there are some limitations such as it being a time-consuming process and requiring soft repair.