- Notes, cautions, and warnings
- Preface
- PowerProtect Data Manager for SAP HANA Application Agent Overview
- PowerProtect Data Manager overview
- About the SAP HANA application agent
- SAP HANA application agent and File System agent coexistence
- Prerequisites
- Supported Internet Protocol versions
- Encryption in-flight
- PowerProtect Data Manager new deployment overview
- PowerProtect Data Manager existing deployment overview
- Security configuration
- Enabling the SAP HANA Application Agent
- SAP HANA data protection and replication requirements
- Protecting a stand-alone SAP HANA server
- Protecting SAP HANA multinode environments
- Install and configure the SAP HANA application agent
- Install the SAP HANA application agent
- Update the SAP HANA application agent
- Update the application agent in the PowerProtect Data Manager UI
- Uninstall the SAP HANA application agent
- Configure the SAP HANA operations
- Integrate the SAP HANA backup program
- Modify the configuration file parameter settings
- Enable the discovery of database application agent backups
- Configure support of SAP HANA 2.0
- Configure automatic backups of SAP HANA logs
- Configure the SAP HANA parallel backup setting
- Enable multi-stream backups for SAP HANA protection policy
- Deploy the SAP HANA application agent in Microsoft Azure environment
- Manage the SAP HANA application agent
- Managing Storage, Assets, and Protection
- Add protection storage
- Enable an asset source
- Delete an asset source
- Discover an SAP HANA application host
- Add and remove the credentials for SAP HANA assets
- Replication triggers
- Add a protection policy for SAP HANA database protection
- Asset-level configuration for protection policies
- Protection rules
- Cancel a Microsoft Exchange, Oracle, or SAP HANA application agent protection job
- Extended retention for protection policies created in PowerProtect Data Manager 19.11 or earlier
- Edit the retention period for backup copies
- Delete backup copies
- Enable the SAP HANA application agent after hostname change
- Enable the SAP HANA application agent after host IP address change
- Migrate the SAP HANA application agent to a different host
- Migrate the SAP HANA application agent to a different PowerProtect Data Manager server
- Manage the PowerProtect agent service
- Manage the cloud tier operations with PowerProtect Data Manager for application agents
- Performing Self-Service Backups of SAP HANA Databases
- Performing self-service backups of SAP HANA databases
- Restore an SAP HANA application host
- Displaying the restore progress in PowerProtect Data Manager UI
- Performing restore and recovery by using SAP HANA Studio
- Performing restore with dependency chaining or replication storage
- Performing alternate host recovery
- Performing restore of backups performed prior to PowerProtect Data Manager registration
- Performing recovery by using the SAP HANA CLI
- Performing Centralized Restores of PowerProtect Data Manager Backups
- SAP HANA Best Practices and Troubleshooting
- Glossary
PowerProtect Data Manager 19.15 SAP HANA User Guide
Centralized restores of SAP HANA backups
The centralized restore functionality in the PowerProtect Data Manager UI allows you to restore SAP HANA backup copy to an asset that is a part of active PowerProtect Data Manager policy.
The SAP HANA centralized restore is applicable for both stand-alone database and multi-node database environments.
Restore of a full backup copy can be performed either on the original SAP HANA host location or an alternate host or alternate instance.
- Restore to Original: Restore and overwrite the original database.
- Restore to Alternate: Restore to an alternate database on either the original host or an alternate host.
The following topics describe the considerations, prerequisites, and procedures to perform the centralized restores of SAP HANA backups on the PowerProtect Data Manager UI.
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\