As soon as you select a database in \u2018Protected data\u2019 pane within the DPM Recovery wizard, all the mailboxes belonging to specified database is displayed by the DPM. Using this, you can recover:<\/p>\n
- \n
- Recover a single Exchange mailbox<\/li>\n
- Recover EDB Database<\/li>\n
- Recover entire Exchange Server<\/li>\n<\/ul>\n
Let\u2019s look at each:<\/p>\n
#1: Recover a Single Exchange Mailbox<\/strong><\/p>\n
DPM replicates the entire database to enable recovering the single Exchange mailbox. The policy to copy the full database is recommended by Exchange. Recovery of individual mailboxes is initiated through the recovery database. It is more commendable rather than directly recovering from the database hosting the original mailbox. It is vital that the recovery database exists before you attempt to recover Exchange mailbox<\/a>.<\/span> Follow the steps below:<\/p>\n
1. To initiate the recovery procedure, make sure that the Exchange Server is protected. Next, ensure that recovery mailbox database exists, else, create a new one using New-MailboxDatabase cmdlet. Configure the settings of the recovery database so that it becomes possible to overwrite it by using Set-MailboxDatabase cmdlet.
\nFor Example:<\/strong>
\n\u201cNew-MailboxDatabase -Recovery -Name RDB-CONTROL -Server E2K13-MBX1\u201d<\/em>
\n\u201cSet-MailboxDatabase -Identity \u2018RDB-CONTROL\u2019 -AllowFileRestore $true\u201d<\/em><\/p>\n2. In the DPM Administrator Console, navigate to Recovery view<\/strong> and from All Protected Exchange Data node<\/strong>, select the mailbox database that needs to be recovered
\n3. In the recovery points section, all available recovery points are mentioned in bold on the Calendar.<\/strong> Click the desired date and then select a recovery point navigating through Recovery time<\/strong>> Recover<\/strong> to continue the process to recover the Exchange mailbox<\/span>
\n4. Review the recovery selection from the Recovery wizard and then click on Next<\/strong>
\n5. Specify the recovery type that requires to be performed and click on Next<\/strong>
\n6. In the then appeared Specify Recovery Options<\/strong> page, perform the following:
\na. Click on the checkbox associated with Mount the databases after they are recovered<\/strong>. If you do not wish to mount the database, then make sure to clear the checkbox
\nb. Network bandwidth usage throttling: Click on Modify to enable throttling
\nc. If applicable, click on the option Enable SAN-based recovery using hardware snapshots<\/strong>
\nd. Next, select Send an e-mail when the recovery completes<\/strong> in Notification<\/strong> and specify recipients. Make sure to separate the provided email addresses with commas
\n7. Make sure to review the recovery settings in the Summary<\/strong> page that appears. Once the recovery operation completes, click on the Close<\/strong> button
\n8. Once the recovery procedure finishes, the mailbox is not restored fully. Mailbox database to which the particular mailbox belongs is restored to Recovery mailbox database. The following cmdlet can be executed to restore the mailbox:
\n\u201cNew-MailboxRestoreRequest \u2013SourceDatabase \u2019RDB-CONTROL\u2019 \u2013SourceStoreMailbox \u2018mailbox name\u2019 \u2013TargetMailbox <name>@servername.com \u2013TargetRootFolder Recovery -SkipMerging StorageProviderForSource\u201d<\/em>
\nNote:<\/strong> -SkipMerging StorageProviderForSource must be added to the cmdlet, else an error message will appear.<\/em>
\n9. After the restoration is completed, the Recovery mailbox database can be dismounted and deleted by running Windows PowerShell cmdlet:
\n\u201cRemove-MailboxDatabase -Identity \u2018RDB-CONTROL\u2019\u201d<\/em><\/p>\n#2: Recover an Exchange Database<\/strong><\/p>\n
1. In the DPM Administrator Console, go to Recovery view<\/strong> and in the All Protected Exchange Data<\/strong> node, navigate to the mailbox database that needs to be recovered.
\n2. In the recovery points section, all available recovery points are specified. Click on a particular date and then select Latest<\/strong> to acquire the most recent backup and then click on Recover<\/strong>
\n3. View the recovery selection made earlier in the Recovery wizard<\/strong> and then click on Next<\/strong>
\n4. Mention the type of Exchange Server recovery<\/span> that needs to be performed and then click on Next<\/strong>
\n5. In the Specify Recovery Options<\/strong> page that appears, do the following:
\na. Select Mount the databases after they are recovered<\/strong>
\nb. Click on Modify<\/strong> corresponding to Network bandwidth usage throttling<\/strong>
\nc. If applicable, click on Enable SAN-based recovery using hardware snapshots<\/strong>
\nd. Select Send an e-mail when the recovery completes<\/strong> in Notifications<\/strong> and mention the recipients. Ensure that all the email addresses are separated with commas
\n6. Return to Exchange Server to enable database to overwrite by restoring, else the restore procedure will fail. Open the Exchange Admin Center (EAC) and navigate to Servers<\/strong> and then click on Databases.<\/strong> Next, select appropriate database that requires to be overwritten and then click on Edit<\/strong> to proceed further with Exchange database recovery<\/span> procedure
\n7. Click on Maintenance, select This database can be overwritten by a restore<\/strong> and then select Save<\/strong>
\n8. In the Recovery Wizard,<\/strong> review the recovery settings on the Summary<\/strong> page and then select Recover<\/strong>. Click on Close<\/strong> when the recovery procedure finishes
\n9. Check the mailbox contents for verifying the success of the restore procedure. If the recovered mailbox database is part of the Database Availability Group (DAG), failure and suspension of the procedure will be displayed.
\n10. To resume the DAG operation, select the suspended database copy and click on Resume. Dialog box prompts too reseed the database. Click on Yes.<\/strong><\/p>\n#3: Recover an entire Exchange Server<\/strong>
\n1. In the DPM Administrator Console, navigate to Recovery view<\/strong> and then to the Server<\/strong> that needs to be recovered
\n2. All the available recovery points will be highlighted as bold in the Calendar under recovery points section. Specify a date and then select a recovery point from the provided list. Next, right click on Bare Metal Recovery (BMR)<\/strong> and click on Recover<\/strong>
\n3. Review the recovery selection in the Recovery Wizard<\/strong> and then click on Next<\/strong>
\n4. In the then appeared Select Recovery Type page<\/strong>, click on Copy to a network folder<\/strong> for restoring the Server to separate network location. Alternatively, if you have one, click on Copy to tape<\/strong>
\n5. In the Specify Destination<\/strong> page that appears, select the location where you wish to copy the database files and these files will be further used to perform Bare Metal Recovery (BMR)
\n6. In the Specify Recovery Options page that appears,<\/strong> do the following:
\na. Select Mount the databases after they are recovered<\/strong>
\nb. Click on Modify<\/strong> to enable Network bandwidth usage throttling<\/strong>
\nc. Select Enable SAN-based recovery using hardware snapshots<\/strong> if applicable
\nd. Click on Send an e-mail when the recovery completes<\/strong> in Notification<\/strong> and then specify all recipients by separating their email addresses with commas
\n7. On the Monitoring<\/strong> tab, you can attempt to view the status of the process. \u2018Recovery success\u2019<\/strong> dialog box will appear on completion of the process
\nNote:<\/strong> To make the recovery process easier, rename the recovered files using shorter names and create Share<\/em>
\n8. In order to run BMR, insert the ISO of the Operating System for the boot purposes, then select the Repair<\/strong> option and then select System Image Repair<\/strong> in the Advanced Options<\/strong>
\n9. You can ignore the warning about \u2018system image not found\u2019 displayed in the Re-image your computer<\/strong> wizard
\n10. In the Select a system image backup<\/strong> page that appears, click on Select a system image<\/strong> and then click on Advanced<\/strong> option to select recovery files from network share. Next, click on Search for a system image on the network<\/strong> and click on Yes<\/strong> to connect to the network
\n11. Specify the particular network folder and then select backup along with date and time of the appropriate image that needs to be restored. Specify disk settings as well as additional drivers and then click on Finish<\/strong> to initiate the restore procedure.<\/p>\nEven though the above procedure helps to recover a single Exchange mailbox, edb file but the entire process is too much lengthier. Exchange mailbox data are stored within the EDB files; the corrupt edb file can be recovered and restored back with the help of third party tools.<\/p>\n
Stellar Repair for Exchange Software repairs corrupt edb file & works on MS Exchange Server 2016, 2013, 2010, 2007, 2003, 2000, and 5.5 versions. You simply download the software by visiting official web address http:\/\/www.stellarservertools.com\/recover-exchange-mailbox.php<\/a>\u00a0to repair corrupt edb file.\u00a0The tool restores data from all types of edb file corruption without hampering the Exchange Server Services.You may try the demo Version Here.<\/p>\n
![\"\"](\"https:\/\/www.stellarservertools.com\/blog\/wp-content\/uploads\/2017\/04\/free-download-large.gif\")
<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"