Reasons for importing EDB file into Exchange server
For email exchange and communication, Microsoft Exchange server has become ubiquitous in many organizations and enterprises. With the release of newer versions of Exchange, the older versions quickly become obsolete or require manual patching of updates. The Exchange EDB, also known as the database file, is an important component of the Exchange server that stores all messages, contacts, notes, and mail items. Now that Exchange 2019 has taken the lead and support for older versions such as 2010 has been phased out, the old database must be moved or imported into a new Exchange server to restore all emails and user mailboxes. Using older versions of Exchange also makes your data more prone to corruption, virus attacks, data loss necessitating a thorough recovery and transfer to another server. In all of these cases, many IT administrators find the Exchange migration extremely difficult to complete without proper guidance and support. This article describes the steps to easily move or import the EDB into Exchange server 2016, 2019, 2013.
How to move Exchange database from one server to another
To move an EDB file from Exchange to another server, first check the database state with Eseutil and backup the database file with Windows Server backup utility. Finally, restore the backup to a new Exchange server.
The Eseutil command line utility is installed when you install the Exchange server and it can check the database file for errors, consistency, missing log files, and so on. To run eseutil, first unmount the database with the Dismount database cmdlet. Next, navigate to the Eseutil's location, launch the tool, and proceed with the following steps.