- Notes, cautions, and warnings
- Preface
- PowerProtect Data Manager for SAP HANA Agent Overview
- Enabling the SAP HANA 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 agent
- Install the SAP HANA agent
- Update the SAP HANA agent
- Update the application agent in the PowerProtect Data Manager UI
- Uninstall the SAP HANA agent
- Decommission the SAP HANA agent version pre-19.8
- Recommission the SAP HANA 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 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
- Cancel an application agent protection job
- Extended retention
- Edit the retention period for backup copies
- Delete backup copies
- Enable the SAP HANA agent after hostname change
- Manage the PowerProtect agent service
- Manage the cloud tier operations with PowerProtect Data Manager
- Performing Self-Service Backups of SAP HANA Databases
- Performing self-service backups of SAP HANA databases
- Restore an SAP HANA application host
- SAP HANA Best Practices and Troubleshooting
- Troubleshooting storage units
- Troubleshooting PowerProtect Data Manager UI display of localhost.localdomain hostname
- Troubleshooting agent registration
- Troubleshooting PowerProtect agent service operations
- Troubleshooting missing assets in PowerProtect Data Manager UI
- Troubleshooting a negative Reduction % value for self-service catalog backup
- Troubleshooting a backup failure with getPreferredNode error
- Troubleshooting a backup failure with insufficient privileges error
- Troubleshooting a missing duration value for centralized backup
- Troubleshooting a catalog restore issue for assets with the same SID and database name
- Troubleshooting a backup and delete issue with database authentication type of userkey
- Troubleshooting a shortened retention issue with SAP HANA full backup
- Troubleshooting issues after DD change in protection policy
- Troubleshooting an auto-configuration failure in multinode environment
- Troubleshooting an issue with onboarded backup copies
- Troubleshooting a restore of replicated backup from secondary DD
- Troubleshooting an issue with protection policy in multihost configuration
PowerProtect Data Manager 19.11 SAP HANA User Guide
Troubleshooting an auto-configuration failure in multinode environment
PowerProtect Data Manager might not discover a newly created SAP HANA database until the database is operational. As a result, auto-configuration might fail in a multinode SAP HANA environment.
NOTE Once the database is operational,
PowerProtect Data Manager will automatically discover the database in subsequent scheduled discovery calls.
As a workaround, once the database is operational, you can retry the auto-configuration. You can use one of the following methods to trigger the auto-configuration:
- Click the set lockbox option on the protection policy.
- Add a new asset with the same SID to the protection policy.
- Re-create the protection policy from scratch.
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: <>()\