An SAP HANA backup might fail with an error that reports insufficient privileges.
To identify any faults in the system environment, perform the following actions:
Ensure that the credentials of the database user account are recorded correctly in the protection policy setting.
Ensure that the database user account included the protection policy has not been locked out.
Ensure that the database user account included the protection policy has the BACKUP_ADMIN, BACKUP_OPERATOR, and CATALOG_READ privileges. The SAP HANA article
Authorizations Needed for Backup and Recovery provides more details.
Missing duration value for centralized backup
A centralized SAP HANA backup succeeds, but the backup job duration at the asset level appears as 0 ms on the
Step Log tab and
Details tab in the
PowerProtect Data Manager UI.
The
Step Log tab and
Details tab appear in the
Job ID Summary window, which you can access by selecting
Jobs > Protection Jobs and clicking the job ID next to the job name.
As a workaround, view the correct backup duration in the
Duration column in the left pane that has a grid format.
Backup and delete issue with database authentication type of
userkey
With an SAP HANA client version earlier than 19.6 and
PowerProtect Data Manager server version later than 19.6, the SAP HANA backup and delete workflow fails for protection policies with the database authentication type of
userkey.
Perform either of the following workarounds:
Update the SAP HANA client to the latest supported version.
Change the database authentication type to username/password.
Shortened retention issue with SAP HANA full backup
You might encounter an issue with retention of an SAP HANA full backup after the retention time has been shortened.
When you shorten the retention time of an SAP HANA full backup from time T1 to time T2, the retention time value remains at time T1. The full backup is not cleaned up at the expected time T2.
Data is not available for the Topic
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: <>()\