A recovery database (RDB) is a unique sort of mailbox database; as a part of the recovery process, you can mount and extract data from a restored mailbox. An Exchange administrator uses different tactics to protect the data from corruption and also to retrieve the data in case of corruption. In this write-up, we will go through some necessary recovery procedures applicable in Exchange Server 2016.
Recover mailbox database using Exchange backup
Exchange administrators usually use Windows Server Backup to take the backup of Exchange data, and you can retrieve the data up to the last successful backup.
In this scenario, you must be aware that the lost data which was created after taking the backup will not be recovered, still you can use the transaction log files to rollback the committed transaction and get the complete data. But if the transaction log files are also missing, then you can only recover the data up to the last backup. It means you will bear some data loss.
Before starting the recovery, check when the Windows Server Backup utility took the last backup.
Run the cmdlet –
Get-MailboxDatabase -Server NPP2016V3 -Status | f1 Name, LastFullBackup
It will provide name of the database and details of the time of the last backup. For example,
Name : DB432432
Last Full Backup : 2/3/2017 3:52:22 PM
Now you can begin the recovery procedure by following the steps:
- Open Windows Server Backup > Actions tab >click on ‘Recover.’
- Choose the source of the backup. If backup is present in the same volume, then select This Server (ServerName).
- Choose the backup that you want to restore.
- There will be multiple restore types which you can choose, like Files and Folders, Volumes, Hyper-V, System State, and applications. Choose ‘Applications’ and go ahead.
- On the following page, select ‘Exchange.’
- In the Recovery options, choose ‘Recover to the original location.’
- The tool will provide a summary of your choice. Confirm it.
- The recovery begins. After completing the successful recovery, the database will be automatically mounted and available to use. You can check the missing data in Outlook.
Recover Exchange database using the Recovery database
An experienced Exchange Administrator is aware of the importance of the Recovery Database. It is a special kind of mailbox database that lets you extract data from a restored database in the recovery operation. The Recovery Database recovers the data from the backup or a copy of the database. This way, you are not obliged to repair a corrupt Exchange EDB file but restore data from a duplicate database.
After you have created a recovery database, you can use a backup application to restore the data in the restored mailbox or copy the database and its log files directly to the recovery database. After that, you can use the New-MailboxRestoreRequest to run the restore procedure.
Here are the steps to recover the data using a recovery database.
- Copy or restore a database and its log files to a location that is suitable for the recovery database.
- The database must be brought into a clean shutdown condition, and that is possible through the ESEUTIL tool. Run the command;
- Create a recovery database > provide it a name > get the name and path of the database file for the EdbFilePath parameter, and the location of the recovered log files.
- Restart Microsoft Exchange Information Store Service.
- Mount the Recovery database to Exchange Server.
- Make sure the recovery database contain the mailboxes you need to restore.
- Check the status of restoration request on a regular basis.
- After successful completion of the restore job, you can remove it.
Eseutil /R Database32932 /l F:\Databases\Database59343 /d F:\Databases\ Database59343
New-MailboxDatabase -Recovery -Name RecoveryDatabaseName -Server Matt -EdbFilePath “E:\Databases\Database59343\Database59343.EDB” -LogFolderPath “E:\Databases\RecoveryDatabase”
Restart-Service MSExchangeIS
Mount-database RecoveryDatabaseName
Get-MailboxStatistics -Database RecoveryDatabaseName | Format-Table Name,MailboxGUID –AutoSizeCreate a new mailbox restore request.
New-MaiboxRestoreRequest -SourceDatabase Database59343 -SourceStoreMailbox “Matt Goodman” -TargetMailbox Matt@contoso.com –TargetIsArchive
Get-MailboxRestoreRequest
Get-MailboxRestoreRequest -Status Completed | Remove-MailboxRestoreRequest
If you don’t want to follow a lengthy process of creating a recovery database and then running a restore request, then you should opt for the Recoveryfix for Exchange Server recovery tool , which saves your time and takes less efforts for the recovery process. It can also help you to export EDB files to Office 365.
Recoveryfix for Exchange Server Recovery
Here is the process for recovering data using Recoveryfix for Exchange Server Recovery.
- Run the software and click Add Source icon.
- Select Offline EDB file. Click Next.
- Browse the EDB file and click Next.
- Choose standard scan, then Click Next.
- The tool has scanned and recovered the data. Click Finish.
- Choose the version of Exchange Server. Click OK.
- The EDB file content is present in the source list. You can check its folders and see the preview of each file. Now, click Add Destination icon.
- Select ‘Create new PST file’ and click Next.
- Browse the saving location of the PST file and provide a name to the PST file. Click Next.
- The tool adds the PST file now click on Finish button.
- Select the messages from the source mailbox, right-click on it, and select Copy message(s).
- Go to destination PST file, right-click on it and select the Paste Message option.
- After migrating the messages, the tool gives the migration report. Click Cancel.
- The message is now present in the PST file.
After transferring the files, you can access the PST file in Outlook.
Conclusion
In case of corruption in Exchange Server database, the manual methods do not provide any guarantee to recover the complete data, still, Recoveryfix for Exchange Server Recovery removes every issue and brings the data back to you entirely. The software will also recover exchange server 2019 database file without the help of any duplicate database or log entry.