last updated: 2025-09-22
Table of Content
Why was this blog post created?How to check/detect if SAP HANA is having an unmanaged database backup issue?What is the conclusion?Everyday issuesOther articleUseful bookmark
Why was this blog post created?
Unmanaged SAP HANA database backup can affect overall system performance (such as, general performance, memory area, CPU usage, and so on). Properly configuring SAP HANA database backup is an essential task. Missing this task can cause various issues (which are sometimes very difficult to identify precisely).
How to check/detect if SAP HANA is having an unmanaged database backup issue?
1. 3284834 – SQL Statement Collection: “HANA_Configuration_Minichecks” report for SAP HANA
The most general report will contain further information about the issue. The minicheck report contains a dedicated section belongs to backup area. With this report we can easily identify if there is issue with the backup. In the below example the Size of backup catalog (MB) and Age of oldest backup in catalog (days) values shows there are issue.
195;**** ;BACKUP ; ; ; ; ;
196; ; ; ; ; ; ;
197; 910;Age of last data backup (days) ; ;0.37 ;<= 1.20 ; ; 1642148
198; 911;Age of last data backup error (days) ; ;2394.37 ;>= 1.20 ; ; 1642148
199; 915;Min. data backup throughput (GB/h, last week) ; ;3583.67 ;>= 200.00 ; ; 1999930
200; 916;Avg. data backup throughput (GB/h, last week) ; ;3810.26 ;>= 300.00 ; ; 1999930
201; 920;Age of last log backup (hours) ; ;0.12 ;<= 1.00 ; ; 1642148
202; 921;Age of last log backup error (days) ; ;1657.16 ;>= 1.00 ; ; 1642148
203; 922;Maximum log backup duration (s, last day) ; ;140 ;<= 300 ; ; 2063454
204; 923;Log backup errors (last month) ; ;0 ;<= 10 ; ; 1642148
205; 930;Automatic log backup ; ;yes ;yes ; ; 1645183
206; 935;Database log mode ; ;normal ;normal ; ; 1645183
207; 940;Size of backup catalog (MB) ; ;463.63 ;<= 50.00 ;X; 2505218
208; 942;Catalog size share (last day, %) ; ;12.43 ;<= 3.00 ;X; 2505218
209; 945;Age of oldest backup in catalog (days) ; ;2532 ;<= 100 ;X; 2505218
210; 950;Log segments not free for reuse ; ;3 ;<= 100 ; ;
211; 952;Log segments free for reuse ; ;22 ;<= 250 ; ;
212; 955;Max. number of log backups / service (last day); ;650 ;<= 300 ;X;
2. 3411878 – Backup related Housekeeping – LEAD SAP Note and 3339034 – SAP HANA multiple issue (Alert ID: 2, 36, 65) caused by large Log Backups due to large Backup Catalog size
The SAP Knowledge Base Articles contains all relevant information to investigate further and the resolution steps.
What is the conclusion?
The best option to setup the proper backup right after the installation of SAP HANA. Retention period needs to choose correctly and the backup activity needs to review periodically. If initial actions missed, right after the backup related issue identified it needs to be solved, so the related issues will be eliminated.
Everyday issues
✍️ Everyday issues: There is no miracle or magic. SAP HANA database needs memory.
Other article
✍️ Where can I find knowledge and information belongs to SAP HANA?
Useful bookmark
🔖 2872774 – Bookmark of Frequently Asked Questions for SAP HANA
🔖 3311408 – Bookmark of SQL Statement Collection reports for SAP HANA
🔖 2658020 – List of SAP HANA SQL Error Codes
Do you have further questions?
Please do not hesitate to contact me if you have question or observation regarding the article.
Q&A link for SAP HANA: https://answers.sap.com/tags/73554900100700000996
Contribution
If you find any missing information belongs to the topic, please let me know. I am happy to add the new content. My intention is to maintain the content continuously to keep the info up-to-date.
Release Information
Release DateDescription2025.09.22First/initial Release of the SAP Blog Post documentation (Technical Article).
last updated: 2025-09-22Table of ContentWhy was this blog post created?How to check/detect if SAP HANA is having an unmanaged database backup issue?What is the conclusion?Everyday issuesOther articleUseful bookmarkWhy was this blog post created?Unmanaged SAP HANA database backup can affect overall system performance (such as, general performance, memory area, CPU usage, and so on). Properly configuring SAP HANA database backup is an essential task. Missing this task can cause various issues (which are sometimes very difficult to identify precisely).How to check/detect if SAP HANA is having an unmanaged database backup issue?1. 3284834 – SQL Statement Collection: “HANA_Configuration_Minichecks” report for SAP HANAThe most general report will contain further information about the issue. The minicheck report contains a dedicated section belongs to backup area. With this report we can easily identify if there is issue with the backup. In the below example the Size of backup catalog (MB) and Age of oldest backup in catalog (days) values shows there are issue.195;**** ;BACKUP ; ; ; ; ;
196; ; ; ; ; ; ;
197; 910;Age of last data backup (days) ; ;0.37 ;<= 1.20 ; ; 1642148
198; 911;Age of last data backup error (days) ; ;2394.37 ;>= 1.20 ; ; 1642148
199; 915;Min. data backup throughput (GB/h, last week) ; ;3583.67 ;>= 200.00 ; ; 1999930
200; 916;Avg. data backup throughput (GB/h, last week) ; ;3810.26 ;>= 300.00 ; ; 1999930
201; 920;Age of last log backup (hours) ; ;0.12 ;<= 1.00 ; ; 1642148
202; 921;Age of last log backup error (days) ; ;1657.16 ;>= 1.00 ; ; 1642148
203; 922;Maximum log backup duration (s, last day) ; ;140 ;<= 300 ; ; 2063454
204; 923;Log backup errors (last month) ; ;0 ;<= 10 ; ; 1642148
205; 930;Automatic log backup ; ;yes ;yes ; ; 1645183
206; 935;Database log mode ; ;normal ;normal ; ; 1645183
207; 940;Size of backup catalog (MB) ; ;463.63 ;<= 50.00 ;X; 2505218
208; 942;Catalog size share (last day, %) ; ;12.43 ;<= 3.00 ;X; 2505218
209; 945;Age of oldest backup in catalog (days) ; ;2532 ;<= 100 ;X; 2505218
210; 950;Log segments not free for reuse ; ;3 ;<= 100 ; ;
211; 952;Log segments free for reuse ; ;22 ;<= 250 ; ;
212; 955;Max. number of log backups / service (last day); ;650 ;<= 300 ;X; 2. 3411878 – Backup related Housekeeping – LEAD SAP Note and 3339034 – SAP HANA multiple issue (Alert ID: 2, 36, 65) caused by large Log Backups due to large Backup Catalog sizeThe SAP Knowledge Base Articles contains all relevant information to investigate further and the resolution steps.What is the conclusion?The best option to setup the proper backup right after the installation of SAP HANA. Retention period needs to choose correctly and the backup activity needs to review periodically. If initial actions missed, right after the backup related issue identified it needs to be solved, so the related issues will be eliminated. Everyday issues✍️ Everyday issues: There is no miracle or magic. SAP HANA database needs memory.Other article✍️ Where can I find knowledge and information belongs to SAP HANA?Useful bookmark🔖 2872774 – Bookmark of Frequently Asked Questions for SAP HANA🔖 3311408 – Bookmark of SQL Statement Collection reports for SAP HANA🔖 2658020 – List of SAP HANA SQL Error CodesDo you have further questions?Please do not hesitate to contact me if you have question or observation regarding the article.Q&A link for SAP HANA: https://answers.sap.com/tags/73554900100700000996 ContributionIf you find any missing information belongs to the topic, please let me know. I am happy to add the new content. My intention is to maintain the content continuously to keep the info up-to-date.Release InformationRelease DateDescription2025.09.22First/initial Release of the SAP Blog Post documentation (Technical Article). Read More Technology Blog Posts by SAP articles
#SAP
#SAPTechnologyblog
