SAP Knowledge Base Article - Preview

3330415 - Managing disk space issues from Backint-Based SAP HANA Log Backups on /hana/shared

Symptom

  • SAP HANA log backups stored on the /hana/shared path are causing disk space accumulation.
  • The procedures outlined in KBAs 2988616, 2505218, and 2096851 were applied to clear the log backups; however, the used space remains unchanged because older log backups from previous years still exist at the operating system level.
  • The ALTER SYSTEM RECLAIM LOG command also fails to resolve the issue.
  • Running the SQL command BACKUP CATALOG DELETE ALL BEFORE BACKUP_ID <Backup_Id> COMPLETE successfully removes entries from the backup catalog, but the physical files persist in the /usr/sap/<SID>/backup/log/SYSTEMDB folder.


Read more...

Environment

SAP HANA, platform edition

Product

SAP HANA, platform edition 2.0

Keywords

Backint log backup cleanup, /hana/shared disk full, SAP HANA log backup accumulation, BACKUP CATALOG DELETE ALL BEFORE BACKUP_ID, ALTER SYSTEM RECLAIM LOG ineffective, physical log files remain, /usr/sap/<SID>/backup/log/SYSTEMDB, Backint #NOTFOUND, Backint #NOTDELETED, orphaned HANA log backup files, third-party backup tool issue, manual deletion of old log backups, SAP HANA backup catalog housekeeping, HAN-DB-BAC, SAP Note 2031547 , KBA , HAN-DB-BAC , SAP HANA Backup & Recovery , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.