Skip to content

SAP HANA Backup and Recovery: A Practical Administration Checklist for On-Premise Systems

Close-up of an opened hard disk drive illustrating data storage and backup infrastructure

A backup job that finishes successfully is encouraging, but it does not prove that an SAP HANA database can be restored within the business’s recovery objectives. The real test is whether the required data backups, log backups, backup catalog, storage access and recovery procedures work together when a system is unavailable.

This guide focuses on SAP HANA Platform 2.0 SPS 08 on-premise. It explains how administrators can build a practical backup and recovery routine, monitor the backup catalog, prepare for tenant recovery and test recoverability. The procedures and responsibilities differ for SAP HANA Cloud; those differences are called out separately.

Start with RPO and RTO—not with a backup schedule

Before choosing daily or weekly backup intervals, agree on two business requirements:

  • Recovery Point Objective (RPO): how much data loss, measured in time, the business can tolerate.
  • Recovery Time Objective (RTO): how long the business can tolerate the database or application being unavailable.

For example, an organisation might set an RPO of 15 minutes and an RTO of four hours for a critical production database. These are example targets, not SAP defaults. The infrastructure, backup design, data volume, network, storage and recovery procedure must be tested to establish whether the targets are achievable.

A data backup provides a recovery base. Log backups capture subsequent changes and help move the database forward to the required recovery point. The more log backups that must be replayed, the longer recovery can take. SAP therefore recommends using the most recent suitable data backup together with the subsequent log backups when recovering a database.

Understand the backup components in SAP HANA

1. Data backups

A data backup saves the persistent database data needed to establish a recovery base. SAP recommends creating data backups regularly and after the initial load. A backup before a database software upgrade is also a sensible operational safeguard: if the upgrade fails, a suitable backup can help return the database to its earlier state.

2. Log backups

Log backups preserve database changes recorded in the log. Their availability is essential when the recovery target is later than the selected data backup. Confirm that log backup generation is enabled and that the destination has sufficient capacity. Do not assume that a recent data backup alone provides the recovery point the business expects.

3. Backup catalog

The backup catalog records backup history and the information needed to locate backup pieces. SAP documents that the catalog is backed up and versioned when backups are created. Protect the catalog along with the data and log backup files. A backup file that exists but cannot be located or associated with the required catalog information can delay recovery.

4. Backup destination

SAP HANA Platform supports file-based backups and integration with third-party backup tools through Backint. Choose a destination that meets your organisation’s security, retention, throughput and restore requirements. Keep recoverable copies protected from the same failure or administrative error that could affect the database host.

Build a practical backup routine

There is no universal backup frequency suitable for every SAP HANA system. SAP’s Administration Guide describes a possible schedule that combines daily data snapshots, periodic data backups and automatic log backups. Treat this as a planning example, not a mandatory schedule; adapt it to your RPO, RTO, data-change rate, storage platform and operational policy.

  1. Document the landscape. Record the SID, instance number, HANA revision, system database and tenant databases, backup destination, Backint integration (if used), encryption configuration, storage dependencies and responsible support teams.
  2. Agree the recovery objectives. Obtain business-approved RPO and RTO targets for each database or workload. Different tenants may have different criticality.
  3. Configure data and log backups. Use SAP HANA cockpit or the approved administration method for your revision. Confirm that the configuration applies to the intended system database or tenant database.
  4. Protect the backup catalog. Verify where catalog backups are written and whether the catalog copy is included in the external protection and retention process.
  5. Separate backup storage from production risk. Ensure backup copies are not dependent solely on the same host, volume or credentials that production administrators use every day. Apply access controls and retention safeguards.
  6. Monitor capacity and completion. Track failed or delayed jobs, destination capacity, log backup continuity and the age of the latest usable data backup.
  7. Test a recovery. Perform a controlled restore exercise in an isolated, approved environment. Measure the elapsed time and document the actual recovery point achieved.

Monitor backup history instead of trusting a green job status

SAP HANA Platform provides backup catalog monitoring views in the SYS schema. Three useful views documented by SAP are:

  • M_BACKUP_CATALOG — overview of backup activities and catalog entries.
  • M_BACKUP_CATALOG_FILES — details about backup files and their destinations.
  • M_BACKUP_PROGRESS — information about backup progress.

For an initial review, an authorised administrator can inspect recent catalog entries with a query such as:

SELECT *
FROM SYS.M_BACKUP_CATALOG
ORDER BY SYS_START_TIME DESC;

Use the output to review recent backup activity and investigate entries that are missing, failed or older than expected. Check the corresponding file details and destination rather than relying on the catalog summary alone. Access to system views depends on the user’s privileges and the database revision; use the SAP documentation for the exact view definition in your environment.

In SAP HANA cockpit, review the backup and recovery configuration for the system database and each tenant database. Confirm the log mode, backup destination, encryption status, scheduler settings and retention configuration. Do not change production parameters simply to make a dashboard look healthy; assess the impact and follow change control.

Prepare for tenant database recovery

In a multitenant database container (MDC), a tenant database is recovered through the system database. SAP’s recovery guidance distinguishes recovery of an individual tenant from recovery of the system database itself. If only one tenant is affected, do not assume that the whole HANA system must be recovered.

Before starting a recovery:

  • Identify the affected database and the required recovery target: to the state before failure, to a point in time, or to a selected backup.
  • Confirm that the required data backup, any required delta backups, log backups and backup catalog are available.
  • Check that the target system has the required HANA software and compatible configuration.
  • Confirm the recovery window, application dependencies, business approval and communication plan.
  • Validate the intended backup and recovery path before committing to the operation.

SAP provides the hdbrecovercheck.py utility in the HANA installation’s python_support directory to check whether the resources needed for recovery to a specified point in time are available. SAP documents limitations: for example, the tool does not recognise data snapshots and does not support system copy or system replication. Read the version-specific documentation before relying on it.

Be especially careful when choosing a recovery from a complete data backup only. SAP warns that changes made after the latest log backup are irretrievably lost in that recovery scenario. Do not select this option simply because it appears faster; confirm that the business accepts the resulting recovery point.

Common backup and recovery mistakes

  • Never testing restores: successful backup completion is not proof of recoverability. Schedule restore exercises and record measured RTO.
  • Ignoring log backup continuity: missing log backups can prevent recovery to the intended point in time.
  • Forgetting the catalog: protect backup catalog copies and confirm that the recovery team knows where to find them.
  • Allowing backup storage to fill: monitor capacity, retention and housekeeping before a full destination disrupts backup operations.
  • Deleting log files at operating-system level: do not manually remove SAP HANA log segments to free space. SAP warns that this can make the log area unusable and may stop the database.
  • Confusing snapshots with independent backups: snapshots can improve recovery speed, but their consistency, replication and storage dependencies must be understood. Ensure snapshots intended for recovery are replicated outside the SAP HANA storage system as SAP recommends.
  • Mixing cloud and on-premise procedures: SAP HANA Cloud has a managed backup and recovery model. Do not copy its automatic backup frequency, retention or recovery assumptions into an on-premise SAP HANA Platform runbook.

SAP HANA Cloud is a different operating model

SAP HANA Cloud documentation describes managed, automatic data and log backups, configurable retention and recovery operations initiated through SAP HANA Cloud Central. These capabilities and service responsibilities are not interchangeable with customer-managed backup configuration for SAP HANA Platform 2.0 on-premise. Confirm the current service documentation and contract for your instance before writing operational procedures.

A monthly recovery-readiness checklist

  • Latest data backup completed within the agreed schedule.
  • Log backups are being generated and destinations are reachable.
  • Backup catalog copies are protected and retrievable.
  • Backup encryption and access permissions meet policy.
  • Retention and storage capacity have been reviewed.
  • Recovery check or restore test has been completed at the planned interval.
  • Recovery instructions, contacts and escalation paths are current.
  • Measured recovery time and achieved recovery point are compared with the business RTO and RPO.

Conclusion

Reliable SAP HANA administration is not just about scheduling backups. It is about proving that the complete recovery chain works: data backup, log backups, backup catalog, protected destinations, permissions and a rehearsed procedure. Start with business RPO and RTO targets, monitor the catalog and storage continuously, and test recovery in a controlled environment. A short, repeatable recovery exercise is far more valuable than discovering missing backup components during a production outage.

For learners who want structured practice with database operations and SAP technical administration, explore the SAP HANA Administration training program and the SAP HANA 2.0 course. You can also visit RHSoftTech to review the broader SAP training options.

Frequently asked questions

1. Is a daily data backup enough for SAP HANA?

Not necessarily. Recovery objectives and data-change rates determine the appropriate combination and frequency of data and log backups. A daily data backup without the required subsequent log backups may not meet the intended recovery point.

2. Can an SAP HANA tenant be recovered without recovering the system database?

Yes. SAP documents tenant recovery as an operation initiated through the system database. If only a tenant is affected, the system database does not automatically need to be recovered; follow the procedure for the specific failure and HANA revision.

3. What does the SAP HANA backup catalog contain?

It records backup history and related information used to identify backup operations and files. Protect the catalog and its copies along with the backup data.

4. What is hdbrecovercheck.py used for?

It checks whether the resources required to recover a database to a specified point in time are available. It has documented limitations, including lack of support for data snapshots, system copy and system replication.

5. Are SAP HANA Cloud backups configured the same way as on-premise backups?

No. SAP HANA Cloud provides a managed backup and recovery model, while on-premise SAP HANA Platform administration includes customer-managed configuration and operational responsibilities. Use the documentation for the exact product and deployment model.

References

Visual note: The featured server-infrastructure photograph is illustrative and is not an SAP HANA product screenshot. Photo by Taylor Vick via Unsplash.

Leave a Reply

Your email address will not be published. Required fields are marked *