When using a third-party backup tool to back up SAP HANA log segments, if the external storage system cannot be accessed, log backups will fail repeatedly. For example, access to an external storage system could be lost as a result of impacted network response times, an outage due to planned maintenance, or hardware failure.
In high-load scenarios, this can quickly cause the log area to grow until the file system is full. If, as a consequence, no more log segments can be created, this will cause SAP HANA to freeze.
You can enable log backup fallback to automatically detect downtimes in a third-party backup tool, and to temporarily redirect the writing of log backups to the file system. If the backup catalog is also configured to be backed up to the third-party storage system, backups of the backup catalog are also automatically redirected to the file system while log backup fallback is active.
To enable automatic log backup fallback, you need the SAP HANA system privilege DATABASE ADMIN. This can be configured by changing below parameter value to 'true' :
#Parameter change is online and no database restart is needed to affect. log_backup_backint_fallback = true
Controls whether log backups using backint will be automatically written to the filesystem, if backint is not available for several consecutive log backup attempts. A fallback to the filesystem is temporary as HANA will periodically attempt to perform log backups using backint again.
If a fallback is active and HANA finds backint to be available again the fallback ends. Otherwise, the fallback will remain in effect until the next attempt.
Note : - A log backup fallback to the filesystem will also apply to catalog backups if catalog_using_backint=true. - Requires log_backup_using_backint=true in order to take effect.
Log Backup Fallback Location
If automatic log backup fallback is a