In an Exchange server 2010/2013/2016, the Exchange Admins have to import Exchange Database Files or EDBs when they are stuck with either of the following situations – Exchange server upgrades, organization planning for in-house server installation, issues on the current Exchange server and so on. In all the cases, Exchange Admins try to backup the EDB files to import at the new location. PowerShell commands are available to import the PST data on the Live Exchange server, but these commands do not support the import of EDB files. Read on to know how to import EDB files into Live Exchange directly.
You must be aware that Exchange server database holds a crucial place for its users. It is used to ensure that the employees work in a collaborative environment, where they can share data and work on a single domain. The entire data shared as emails, contacts, calendars, etc. is saved on the server’s mailbox.
As Exchange database is essential to access Microsoft Outlook, the Exchange server and the server hosting the database must be up and running 24×7. If it is not so, the database becomes inaccessible which may hamper business communication. There are many factors which may cause damage to the server or the database.
Let’s check these factors which may cause damage to the Exchange server mailbox along with the ways in which Admins can import EDB file in Exchange Server 2010/2013/2016.
Need for EDB Data Restoration
- Exchange server upgrades: An organization has decided to upgrade the Exchange server from version 2010 to 2016. Once the Exchange server 2016 is built, the Admin must import the Exchange database from the old server to the newly created Exchange, which is possible with EDB data restoration. The corruption in the database makes it unavailable and creates the need for data restoration by using a professional software
- Exchange server is affected due to:
- Index Corruption: A backup of Exchange server database is installed on a system with a local ID installed on the system. When the Exchange Administrator tries to restore the database on the system, it results in Index corruption due to ID-conflict.
- Metabase Corruption: IIS Metabase and Exchange server Metabase deprivation cause severe Exchange issues. For example, server exposure, Exchange server related services are becoming useless. Then it becomes crucial to recover the EDB file on Exchange server.
- Antivirus scanning: Antivirus software locks up and starts scanning the same file which is being accessed by the Exchange server. Due to this conflict, the Server Information store misses locking the file thus leading to corrupt and unavailable EDB data.
- Denial of Services (DoS) on Server: When multiple systems flood the bandwidth or the resources of the Exchange server then the server becomes indefensible. Commands such as “Mail From”, “Rcpt To” may result in server crash with further impact on integrity of the data available on Exchange server.
When the Exchange server is affected by corruption error or DoS or antivirus settings, it is most likely that the Exchange database becomes inaccessible. The inaccessible database needs to be either restored or recovered. The restoration procedure includes Exchange database restoration from backup with the help of PowerShell commands. Alternatively, use a reliable software to repair and recover EDB files when they get corrupt.
Method 1: Restore EDB files via backup:
The following steps help in database restoration:
- Restore EDB files via Windows server backup
- Move EDBs to Live Microsoft Exchange
- Mount retrieved database
The detailed steps to import EDBs into Exchange Server 2010/2013/2016 are available on this link. These also include the list of PowerShell commands.
The PowerShell commands help in retrieving the Exchange database, but there are certain limitations. The PowerShell commands cannot retrieve the entire database when the files are corrupt. Secondly, the long list of steps has to be followed diligently to restore the database, and if the backup is not good, then the whole effort is rendered futile.
There are reliable software-based utilities which help the Exchange Admins to overcome the complications of PowerShell commands. Such software like Stellar Repair for Exchange repair the corrupt EDBs without any data loss and also assist in importing the EDBs without going through lengthy procedures and bar the use of cmdlets, completely.
Method 2: Recover EDB files with Stellar Repair for Exchange
The software-based utility works on the following principle: “Repair corrupt EDB files and export all the restored files to Live Exchange.”
The following steps help in data restoration:
- Launch the software and Open EDB
- Select the Scanning option – Quick Scan or Extensive Scan
- Add multiple EDB files. Skip the step if only one EDB file is available
- Right click on the mailbox to export the mailbox directly on Live Exchange
- Provide Exchange server credentials, and click on Export
- The scanned Exchange mailboxes available in the specified EDB file are successfully imported into Exchange Server 2010/2013/2016
The ease with which an organization imports the EDB files on Live Exchange server including the ability to repair the entire database enables the organizations to increase the time spent on more productive activities and in turn reduce downtime for the users.
Conclusion
There are various reasons behind Exchange database turning inaccessible for users. Here comes the role of Exchange Administrators who have to ensure that the Exchange system is up and running 24×7 and if in case there are any server or database related problems then these should be attended quickly.
All these ends are well-achieved with the help of software-based Stellar Repair for Exchange. The Admins can import EDBs directly into Live Exchange Server without the use of lengthy and time-taking PowerShell commands. The software’s capacity to recover dismounted and offline EDB file through its extensible interface makes it all the more competent.
