Hello. In this video, we will see how to use the Power Protect Data Manager UI to perform a centralized restore of an SAP HANA database. The centralized restore of an SAP HANA database is supported starting with Power Protect Data Manager version 19.15. The SAP HANA centralized restore is applicable for both standalone database and multi-node database environments.
When an SAP HANA database is backed up as part of a protection policy, you can recover it from backup using the centralized restore functionality in the Power Protect Data Manager UI. You can restore and overwrite the original database, or restore the database to an alternate database on either the original host or an alternate host. For this demo, I have already integrated and registered the SAP HANA hosts with Power Protect Data Manager on the application agents page. We see that the SAP HANA hosts have been registered successfully. After they are successfully registered, the hosts are discovered on the asset sources page.
After the successful discovery of the asset sources, we see that the SAP HANA databases are discovered as assets on the assets page. For this demo, we use a tenant database and a system DB database for performing the centralized restore. I have set the asset-level credentials for these databases, added them to the protection policy, and run a couple of backups for these databases.
In the restore section, we see the assets system DB and test two that have backup copies for performing the restore. First, let's perform a system DB restore to the original location. To perform a centralized restore, select the asset and click restore. On the copy selection page, select the backup copy. On the locations page, it prompts us to restore to original or restore to alternate. For this system DB restore, we choose to restore to original. Note that you can restore to a standalone and multi-node database to an original database location. On the configuration page, select any of the following options. Because I have set the asset level to credentials for system DB, I choose to use the credentials that are set at the asset level or protection policy level.
We can choose to restore to a recent state or use a specific backup or choose a point in time, depending on the requirement. For this demo, I choose the recent state. In the OS username section, enter the name of the operating system user that is associated with the target instance. We can set the stream count and provide the transaction log data path. We can optionally enable clear log area, enable ignore delta backups, check access in file system, check access in back end, and enable compressed restore. We can also select troubleshooting mode to enable troubleshooting logging. When we are finished, we click next. On the summary page, we can review the information in the copy selection, location, and configuration areas to ensure that the restore details are correct.
When we finish, we click restore. As the restore operation starts, to monitor the restore progress, we click the view details link to display the protection jobs page. Here, we can 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 of database system DB from protection storage to the target database system DB is in progress. Let's wait for the restore to complete. The restore is now successful.
We'll go on to perform a restore of the tenant database to an alternate location. To start, we navigate to restore assets, select the tenant database called test two, and click restore. Select the copy and click next. On the location page, select restore to alternate and choose the alternate database. Note that you can restore a standalone or multi-node database to an alternate database. For an alternate restore, note that the target SAP HANA host that is considered for the alternate host recovery must be registered to the same Power Protect Data Manager server and must have an associated protection policy.
To proceed with the restore, on the configuration page, select any of the following options. I have chosen to use the credentials that are set at the asset level or protection policy level. Restore to recent state. In the OS username field, enter the name of the operating system user that is associated with the target instance. We can set the stream count and provide the transaction log data path. Additionally, when restoring the tenant database, we have the option to stop the database before restoring. Enabling this option will cause the agent to stop the database before starting the restore process. Otherwise, we would need to manually stop the database.
We can optionally enable clear log area, ignore delta backups, check access in file system, check access in backend, and enable compressed restore. When we're finished, we click next. On the summary page, we can review the information in the copy selection, location, and configuration areas to ensure that the restore details are correct. When we finish, we click restore.
As the restore operation starts, to monitor the restore progress, we click the view details link to display the protection jobs page. We can 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 moving the database test two from protection storage to the target database test one is in progress. Let's wait for the restore to complete. The restore is now successful. For more details about this topic, see our technical white paper, Dell Power Protect Data Manager SAP HANA, Agent Backup and Recovery. Thanks for watching.
