Written by Hi everyone today I’ll be talking about importing Exchange EDB files to live Exchange servers.
Restoring orphaned EDB files to a Live exchange server is not an easy chore, as you probably know. The procedure could provide several challenges, including a growing problem like corruption or another. As you are aware, importing PST files to Live Exchange Server with certain PowerShell Commands is similarly simple as backing up Live Exchange Server Database to PST.
It is not so simple, though, if we believe that we may import EDB to Live Exchange Server using the same method since Exchange Admin Centre lacks direct PowerShell commands or tools to accomplish this job.
Most of the time you might like to exchange just a few chosen mailboxes from EDB file without compromising any other functionality and mailboxes. Recover Database gives us tools to mount an EDB file to an Exchange server without compromising the live database in Exchange 2010 and 2013. Although recovery databases cannot be assigned to an active user, we can retrieve some mails from them. This is the reason Recovery Database is titled as such. Let us now turn now toward the importing process.
EDB file recovery using Windows Server Backup
You have to follow these guidelines for EDB file recovery:
- Click Recover after running Windows Server Backup.
- Choose now the location of EDB file storage. You may choose your own server location or another here.
- Choose Date & Time for Restoring now and then move on to next action.
- It will now probe “What do you want to recover?” and here you have many of choices for rehabilitation. You might choose, for instance, “files and folders,” “Hyper-V recovery,” “Volume recovery,” “application recovery,” and at last “System date” recovery.
- Since we only want to recover EDB files and move on from here, you should choose “Files and folders”. You must choose “Application” recovery if you must restore Exchange Server Live Database.
- Now expand the tree from left panel, find the EDB file location, and move on to the next stage.
- Choose now a restoration destination site.
- Now at last confirm the work and head for Recovery.
We have to import and mount the database file to Exchange Server once the Recovery process is finished.
Import Live Exchange Server’s EDB file
I have recovered EDB files as you are aware; so, we should import database files to replace the server. However, if we try to mount the recovery database right now, it would display a failure warning since it is currently in state of “Dirty Shutdown”. Running eseutil.exe in PowerShell or Exchange Management Shell will let you check it. ESEUTIL commands have this syntax.
Syntactic: eseutil /mh /edb file path
The following processes import EDB files to Exchange Server:
To bring EDB file to Clean shutdown state, run PowerShell and type blow command.
Command: eseutil /r E05 /l C:\RecoveryLogFiles /d C:\RecoveryDatabaseFile
Character:
/r: Talks about Recovery Mode
E05: Details on log file name prefix
/l: Specifies Path of Log File
/d: Shows database path.
2) The command above will carry soft recovery. Running following command once again will help you to check the state of the database EDB file.
Command: e-use /mh C:\RecoveryDB File
Should you discover that the state of the database is “Clean shutdown,” EDB file have either successfully recovered or else you will have to engage in hard recovery of EDB file.
Making a Recovery Database
Just run under instructions for the creation of a Recovery Database.
- Run a New-Mailbox Databases command using a Recovery Switch. Below is a command example:
New-Mailbox Database -server E05MB5 -Name File in Recovery Database: Recovery EdbFile Path C:\ Recovery Database File: DB5.edb – Log Folder Path C:\ RecoveryLog Files
- Currently mount the Recovery Database. To mount below command:
- Command: Database Recovery File Mount
Run below a command to check the database file’s operational condition.
Get-Mailbox Statistics: Database Recovery Database File | ft -auto
Simple and Automatic EDB file importing method for Exchange Server
Importing an EDB file to live exchange was not a simple chore as you might have seen above. To follow above approach, you should be well familiar with PowerShell commands for exchange server management. For you can lose your data if you do something incorrectly.
Given small corruption, I would advise you to use an automatic Softaken EDB to PST Converter allowing you to import EDB files to Exchange Server following recovery. With this utility, you might get many more features and capabilities including support and recovery of a corrupt EDB file.
At last
We have talked about the labor-intensive manual importing of individual EDB files to live Exchange server. Restored EDB file, created recovery database, imported EDB file to Exchange and at last Mounted database to Exchange Server following some required actions.
We also spoke about a very simple and practical automatic method for importing EDB file data to Exchange Server.