How to Mount EDB On Different Exchange Server? Complete Solution

  author
Written By Andrew Jackson
Anuraag Singh
Approved By Anuraag Singh
Published On August 24th, 2022
Reading Time 6 Minutes Reading

Summary: Are you facing trouble for finding the solution to mount EDB on Different Exchange Server in an easy way? If so, then you are read the correct article. Here we will guide users to mount the Exchange database file to different Microsoft Exchange Server.

Microsoft Exchange Server EDB file is very important for an IT organization and other industry verticals that allows their employees, users, clients as well as customers to communicate with each other, share their work under the same domain inside and outside the organization.

All the Exchange mailbox data is saved in .edb file on the server. Everyone knows that Exchange Server is prone to corruption and Exchange Administrator try their level best to keep the data safe & secure but due to server crashes, virus/malware attacks, etc… the Exchange data is damaged/corrupted, deleted, or lost. In the worst-case scenario, if any disaster or catastrophe occurs, there are chances of the entire Exchange Server completed stopped working.

In this case, it is important to mounted the Exchange database file to different or new server to access the mailbox data.

Solution to Mount EDB On Different Exchange Server

What you can do to make the Exchange Server working is to restore the backup but due to unfortunate condition the Exchange database file being backed up. In this scenario the AD (Active Directory) is also lost. So, you have to reconstruct the Microsoft Exchange Server along with AD. Then, attach the EDB file but starting isn’t a piece of cake.

First, install the server and setup the Domain Naming System (DNS), Dynamic Host Control Protocol (DHCP), and Active Directory services. Then, configure the new schema and to keep the Exchange Server up to date, install all new windows updates.

After that user have to install the MS Exchange Server (2010, 2013, 2016) and make sure that the new server should be configured with all the same specification/level as the previous Exchange Server. Then, move the Exchange database to the working server and mount it.

If the EDB file is troubling in mounting then this may be because it is in Exchange dirty shutdown state. In order to mount the database in Exchange Server, it should be in a clean shutdown state. To verify the state of the Exchange database users have to use the eseutil /mh cmdlet given below to check whether it is in a clean state or not.

mh-path

Output:

dirty-shutdown

If the state of database is clean then you can mount it easily on Exchange Server. Here the state is dirty and the Log Required is 3-3. In this case the transaction log file are not available and to perform soft repair to reconstruct the log file and bring the database in clean shutdown state by using the command given below:

eseutil /r E06 /l C:\RecoveryLogFiles/dC:\RecoveryDBFile

Here,

r/: defines soft recovery
EO6: transaction log file
l/: log file path
/d: database path

This command performs the soft repair. Then, the user can check the state of the database again if it shows clean then mount EDB on different Exchange Server. If not, then user have to do hard recovery in Exchange 2010, 2013, 2016 database.

Note: There are certain things that you should keep in mind that user have to accept the data loss if they perform this recovery process and it is impossible to predict that how much data is lost.

Use the cmdlet given below to perform hard repair:

eseutil /p command

After this process, user have to defrag Exchange mailbox database. For the Exchange older version, one can use the ISInteg tool but after the Microsoft Exchange 2010 sp1 server users can use the PowerShell New-MailboxRepairRequest cmdlet.

Note: To use this cmdlet it requires in-depth knowledge, hands-on experience and technical skill. Also it is a very time taking process. If you are new to Exchange Server environment then it would be very difficult for you to use this recovery process.

To avoid all this complexity to repair the Exchange database file and mount EDB on different server, you can use the third-party software provided by SysTools i.e. Exchange EDB File Repair Tool that easily repair and recover severely damaged EDB file and resolves database corruption Exchange 2010, 2013, 2016 and other versions with no data loss without using the command.

Download purchase

Use Best Automated Tool

Exchange EDB Repair Tool provides scan mode option i.e. Quick and Advance scan that easily recover & repair EDB file as well as mailboxes from corruption without any loss of data. Depending on the level of corrupted Exchange database file. You can select the dual scan mode to repair Exchange mailbox along with EDB file.

Also, the advance scanning option of this utility recover permanently deleted Exchange database mailboxes and data items from offline/dismounted .edb file. So, now users can use the automated tool to recover deleted mailbox after retention period. After recovery of mailboxes users can export the recovered Exchange mailbox directly to Live Exchange Server mailboxes, office 365, and PST, EML, HTML, MSG, MBOX, PDF file formats.

Along with the Exchange database file, this advanced software also supports the pub.edb file and STM file. Any technical and non-technical users can use this recovery manager for Exchange database tool and after conversion, it automatically creates an export report which stores the success & fail count of exported Exchange data.

Key features Of Professional Tool

  1. Extract data from public and private offline EDB file
  2. Preview Exchange mailbox data items before conversion
  3. Maintains the actual folder hierarchy and keep metadata intact
  4. Extract mailbox from EDB file Exchange 2016, 2013, 2010
  5. Export selective Exchange data items by using categories and date filter option
  6. Remove encryption from Exchange mailbox in batch
  7. Suitable with all Windows OS, Microsoft Outlook and Exchange Server version

Bringing It All Together

This write-up provides detailed information on how to mount EDB on different Exchange Server by using the solution mentioned here. Now users know why mounting of Exchange database file is important on different server. In case of any EDB file is severely damaged or corrupted during the mounting process, then instead of using the prolonged method i.e. ESEUTIL. User can use the advanced software to remove corruption from dismounted/offline Exchange database file with no data loss in a hassle freeway.

  author

By Andrew Jackson

I am SQL DBA and SQL Server blogger too. I like to share about SQL Server and the problems related to it as well as their solution and also I do handle database related user queries, server or database maintenance, database management, etc. I love to share my knowledge with SQL Geeks.