As we are part of rapidly changing data world, the upto dated data need to be maintained safely. This will help business to restore the business in case of  critical failures.

Like any other Database, HANA Data backup and Log backup need to be maintained on regular basis in different location.

Since HANA is an in-memory database and the complete data is available in In memory. In case of instance crash ..etc, upto dated data need to be available which can be loaded while starting the HANA DB next time.

Since the DB is in-memory, all the changes are written to DATA volume in persistence storage asynchronously in regular intervals ( generally 5 mins and can be changed). but to ensure consistency  all the changes happening in HANA instance will be logged to log volume in persistence storage synchronously when ever a commit happened. The data in log volume will be cyclical overwrite

In case of Persistence storage failure…!!!! we need a backup and restoration solution.

To recover HANA from any disk failures / crash , we need Data volumes backup / log volumes backup, latest redo logs updated to log volume and configuration files ( .ini files ).

By default the data backup from HANA studio will not take backup of configuration files ( which should be done manually). this can be achieved with cron in Linux.

The below are the capabilities of Backup and recovery

Data Backup

Storage snapshots

log backups

Recovery to the most recent state

Point in time recovery

recovery of a specific data backup

backup life cycle management

checking the integrity of backups

Backups using 3rd party backup tools

-> data backup is only available in operational mode online

-> during data backup, the system is available

-> during recovery , the system can not be accessed

->backup supports the file backups and 3rd party backup tools using the backint interface.

-> all required files must be accessible

->Configuration path for both data and log backups must be accessable from the whole system not only from any specific instance.

-> the target software must be either equal /  higher version than the source.  Recovery on the lower version software is not possible.