Hello. In this video, we will see how to use the PowerProtect Data Manager UI to perform a centralized restore of Microsoft Exchange databases. The centralized restore of Exchange databases is supported starting with PowerProtect Data Manager version 19.15. When Exchange Server data is backed up as part of a protection policy in PowerProtect Data Manager, you can recover the Exchange Server backups by using the centralized restore functionality in the PowerProtect Data Manager UI.
The centralized Exchange Server restore and recovery operations include the restore of a full or synthetic full backup of a standalone database or Database Availability Group (DAG) database. With centralized restore, you can restore and overwrite the original database, or restore the database to an alternate database on either the original Exchange host or an alternate Exchange host.
For this demo, I have already integrated and registered the Exchange hosts with PowerProtect Data Manager. On the application agents page, we see that the Exchange standalone and DAG hosts are registered successfully. After successful registration, we can see that the hosts are discovered on the asset sources page, and after the successful discovery of the asset sources, we can see that the Exchange databases are discovered as assets on the assets page.
For this demo, we are using one standalone database and one DAG database for performing the centralized restore. I have already added them to the protection policy and have run a couple of backups for these databases.
In the restore section, we can see the assets that have backup copies for the standalone database and DAG database for performing the centralized restore. First, let's perform an Exchange standalone database restore to its original location and to an alternate location. To perform a restore to a database's original location, select the standalone database asset DB 32_1 and click restore. On the copy selection page, select the backup copy. On the locations page, we can choose to restore to the original or an alternate location. For this standalone restore, I choose restore to original. On the options page, we can enable the compressed restore option and also enable troubleshooting mode to enable troubleshooting logging.
Then we click next. On the summary page, review the copy selection, location, and options information to ensure that the restore details are correct. When we finish checking the summary page, we click restore. The restore operation now starts. To monitor the restore progress, click the view details link to display the protection jobs page. Here we see that the restore job is in progress. When we click the job ID to view the detailed step log details, we can see that the step called moving the data from protection storage to the target database DB 32_1 is in progress. Let's wait for the restore to complete.
The restore is now complete and the Exchange standalone database has been restored successfully to its original location. Note that you can also restore a standalone database to an original DAG database location.
To perform a database restore to an alternate location, select the standalone database asset DB 32_1 and click restore. On the copy selection page, select the backup copy. On the locations page, we can choose to restore to an alternate location. We also have the option to discover the Exchange server from this page. Select the alternate location and we see a reminder warning that the restore will overwrite the existing database when the specified database name matches the name of an existing database in the restore location. We click continue to proceed. On the options page, we can enable the compressed restore option and enable troubleshooting mode to enable troubleshooting logging. Then click next. On the summary page, review the copy selection, location, and options information to ensure that the restore details are correct.
When we finish checking the summary page, we click restore. The restore operation now starts. To monitor the restore progress, click the view details link to display the protection jobs page. Here we see that the restore job is in progress. When we click the job ID to view the detailed step log details, we can see that the step called moving the data from protection storage to the target database DB 32 is now in progress. Let's wait for the restore to complete.
The restore is now complete and the Exchange standalone database has been restored successfully to the alternate location. Note that you can also restore a standalone database to an alternate DAG database.
We will now perform a restore of the DAG database to its original location and to an alternate location. To perform a DAG database restore to its original location, select the DAG database asset and click restore. On the copy selection page, select the backup copy. On the locations page, we can choose to restore to original. For this DAG database restore, I will choose restore to original. On the options page, we can enable the compressed restore option and enable troubleshooting mode to enable troubleshooting logging.
Then we click next. On the summary page, review the copy selection, location, and options information to ensure that the restore details are correct. When we finish checking the summary page, we click restore. The restore operation now starts. To monitor the restore progress, click the view details link to display the protection jobs page. Here we see that the restore job is in progress. When we click the job ID to view the detailed step log details, we can see that the step called moving the data from protection storage to the target database DAG 2 is in progress. Let's wait for the restore to complete.
For the DAG database restore, we see that there are two additional steps compared to the standalone Exchange database restore. Before performing the restore, the Database Availability Group replication is suspended, and after the restore is complete, the replication is resumed. The restore is now complete. The Exchange DAG database has been restored successfully to its original location. Note that you can also restore a DAG database to an original standalone database location.
To restore a DAG database to an alternate location, select the DAG database asset and click restore. On the copy selection page, select the backup copy. On the locations page, we can choose to restore to alternate and choose the alternate location. We also have the option to discover the Exchange server from this page. After we select the alternate location, we see a reminder warning that the restore will overwrite the existing database when the specified database name matches the name of an existing database in the restore location. Also, if the database is in a replicated state, the replication is suspended on all the DAG nodes before proceeding with the restore.
Click continue to proceed. On the options page, we can enable the compressed restore option and enable troubleshooting mode to enable troubleshooting logging. We then click next. On the summary page, review the copy selection, location, and options information to ensure that the restore details are correct. When we finish checking the summary page, we click restore. The restore operation now starts. To monitor the restore progress, click the view details link to display the protection jobs page. Here we see that the restore job is in progress. When we click the job ID to view the detailed step log details, we can see that the step called moving the data from protection storage to the target database DAG is in progress. Let's wait for the restore to complete.
The restore is now complete and the Exchange DAG database has been restored successfully to an alternate location. Note that you can also restore a DAG database to an alternate standalone database. For more details about this topic, see our technical white paper, Dell PowerProtect Data Manager Exchange Backup and Recovery. Thanks for watching.
