Exchange Server data holds a very important place for users. It is mostly used in organizations to allow employees to work under a collaborative network where they can share and work on the same domain.
Meanwhile, a copy of all email transactions made are saved on the Server's mailbox with .edb extension; these files are prone to getting damaged or becoming inaccessible. In order to regain the data that has lost its integrity due to corruption or deletion of data from the mailbox, you may have to move/import EDB file to a new Exchange Server/Live Server. This way, any repaired content is made accessible as well after performing such a procedure.
Read more to get acquainted with the various causes that may cause damage to your Exchange Server mailbox and the way via which one can copy EDB to New Exchange Server.
When Does Your Data Require Restoration?
Index Corruption: In case you have created a backup of Exchange mailbox data on your system that has Local ID installed in it, and then you try restoring the database on a system which does not have LCID installed, this may lead to severe corruption of the Index.
Metabase Corruption: Deprivation within the IIS metabase as well as Exchange Server database is one of the most severe issues. It may end up causing a variety of Server exposures along with making Exchange Server related services useless. This may lead users to demand a firm and stable recovery of a .edb file into the new server.
Resource Failure: Anti virus software file level locks up and keeps on scanning the file, which is presently being accessed by Exchange Server. As a result, Server Information Store misses to lock the file and ultimately it becomes corrupt as well as unavailable.
Denial Of Services: Exchange Server is indefensible to ‘Denial of Service’ attacks which can be induced by a buffer overflow in various types of commands; MAIL FROM, RCPT TO, etc. In case you use the buffer overflow, any remote attacker will be able to overflow this buffer and end up crashing the server. Such an attack will block emails as well as another service that is provided by Exchange. In extreme cases, it may even put an impact on the integrity of the data stored within Exchange Server.
Procedure to Recover & Import EDBto New Exchange Server
Restoration of EDB files via Windows Server Backup
There is a procedural way by which one can follow for the Exchange EDB recovery.
Moving .edb File to Microsoft Live Server
Run the eseutil.exe command in PowerShell or Exchange Management Shell to check. Use the following syntax for this ESEUTIL command:
Syntax: eseutil /mh <edb file path>
Command: eseutil /r E05 /l C:\RecoveryLogFiles/dC:\RecoveryDBFile
In the above command:
/r: Defines Recovery Mode
E05: Labels about Log file, which is named in prefix
/l: States the Path of Log file
/d: Designates path of database
The previously used command will execute the Soft Recovery of data. You can simply check the status of EDB file database by executing mentioned command again.
Command: eseutil /mhC:\RecoveryDBFile
Important: If the state of the database is “Clean Shutdown,” which means .edb files are successfully recovered. If not then, one must go for Hard Recovery of Exchange EDB file. Reation of Retrieved Creation of Retrieved
Creation of Retrieved Database
Run the below-mentioned commands for Database Creation of Recovered data:
1. Run command of New-MailboxDatabases by Recovery Switch. By using the mentioned command:
Command: New-MailboxDatabase -server E05MB5 -Name RecoveryDBFile -Recovery -EdbFilePath C:\RecoveryDBFile\DB5.edb -LogFolderPath C:\RecoveryLogFiles
2. Now, mount the retrieved database by using the mentioned command:
Command: Mount-Database RecoveryDBFile
3. Check the working status of the database by executing below command:
Command: Get-MailboxStatistics -Database RecoveryDBFile | ft -auto
The Final Words
This article lets readers avail themselves of rich information about some of the culprits behind the corruption of Exchange Server databases and lets them know about the right type of ways to move/import EDB to New Exchange Server.