Prevent Data Disaster in Your SAP HANA System Landscape With Effective Backup and Restore Strategies

  • by Kehinde Eseyin, Security Architect
  • October 1, 2015
Become acquainted with concepts, best practices, optimal settings, tools, and recommendations that are invaluable for SAP HANA database backup and restore operations.
Learning Objectives
Reading this article, you will learn:
  • Best practices for backing up and restoring an SAP HANA database
  • Basic configurations settings and tools relevant to backup and restore activities
  • Important considerations when planning and implementing a backup strategy for an SAP HANA database
Key Concept

An effective backup and restore strategy is vital to an organization because data and information are important assets of a business enterprise. Backup and restore activities ensure that an organization can get back on track within a reasonable amount of time in the event of a disaster—without compromising the integrity of the database. The adoption of a data-loss prevention strategy is crucial for the SAP HANA system landscape because permanent loss of business data can have adverse legal, regulatory, and business implications.

Database backup is one of the approaches that SAP HANA uses to manage the recovery of the system from failures. Other approaches include storage replication and system replication. The crux of this article, however, is the database backup and restore approach to data-loss prevention and disaster recovery.

At the minimum, implemented backup and restore strategy must satisfy the business requirements of the organization as it relates to recovery time objective (RTO) and recovery point objective (RPO). The SAP HANA database supports file-based backup and BACKINT (via the SAP HANA Backup Application Programming Interface [BAPI]) or a hybrid of both approaches. Irrespective of the approach adopted, the backup strategy should satisfy the following best practices and recommendations:

  • Full database backup to a remote location performed on a daily basis
  • Frequent backups (daily) of database logs to a remote location
  • A retention time for database backup and log backup of at least 28 days
  • Consistency check performed at least once in a backup cycle
  • Periodic disaster-recovery tests performed at defined intervals


Kehinde Eseyin

Kehinde Eseyin is a security architect. He holds a bachelor’s degree in computer science. He has about 12 years of IT security, governance framework, IS risk, and compliance experience gained by working in numerous global organizations. Over the years, he has demonstrated competencies in security design, information assurance, cyber security, data privacy, threat and vulnerability management, penetration testing, business architecture, project management, IT audit, IS controls framework, and identity and access management.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.