Skip to Content

Introduction

In the upcoming weeks, we will be posting new videos to the SAP HANA Academy to show new features and functionality introduced with SAP HANA 2.0 Support Package Stack (SPS) 02.

The topic of this blog is database backup and recovery.

For the previous versions of this blog, see

For the full SAP HANA 2.0 SPS 02 blog list, see

 

Tutorial Video

URL: https://youtu.be/jPCYSpBplvM

What’s New?

Backup Encryption in Cockpit

SAP HANA 2.0 SPS 01 introduced (native) backup encryption (see SAP HANA 2.0 SPS 01 What’s New: Database Backup and Recovery, which could be managed using SQL.

In SAP HANA cockpit SP 03, Backup Encryption has been added to the Data Encryption tile in the Security section and the Data Encryption Configuration app has been added to make configuration of backup encryption a little bit easier.

From the Data Encryption Configuration app you have direct access to the Manage Keys app.

For more information, see

 

Database Copy in Cockpit

Restoring a backup of an SAP HANA database to another system and create a database copy is nothing new but as of SAP HANA cockpit SP 03 this is now made more accessible and a bit easier to perform.

A Copy database link has been added to the Overview page, DB Administration section.

Selecting this link will open the Copy Database app and here you can create a copy of a database within the same system or to a different system. Your source backups can be either file-based or from a third-party backup tool (Backint).

For more information, see

 

Backup and Recovery of Extension Node(s)

Extension nodes provide an alternative for the SAP HANA dynamic tiering option when running SAP Business Warehouse on SAP HANA for those scenarios that involve a multi-temperature memory strategy (hot, warm, cold).

For more information about extension nodes for BW, see

 

 

Extension nodes are distinguished from regular SAP HANA hosts through the usage of worker groups.

As of SPS 02, the worker group value is now included in the backup header, which allows for more flexible handling during recovery.

You can use the hdbbackupdiag tool to analyze a data backup to verify the name of worker group

hdbbackupdiag -v -b <BACKUP FILE NAME>

 

Additionally, the IGNORE WORKERGROUPS clause has been added to the RECOVER DATABASE and RECOVER DATA statement. This enables you to reset the worker group when restoring a backup to the target system value. Otherwise, the restore would fail.

 

What’s in a name?

For the purists, a storage snapshot in the SAP HANA documentation is no longer called a storage snapshot but a data snapshot.

Particularly when using any of the third-party backup tools through the backint API, it was not always clear how HANA’s storage snapshot related to the storage snapshot functionality of the backup tool. For this reason, SAP HANA cockpit already used data snapshot. For consistency, this term is now used in the documentation as well.

In the system views, a storage snapshot is called a data snapshot.

In the cockpit, a storage snapshot is called a data snapshot.

Only in SAP HANA studio, a data snapshot is still called a storage snapshot.

For more information about storage snapshots, see

 

Playlist

On the SAP HANA Academy, there is a full playlist covering all aspects of database backup and recovery:

Documentation

For more information, see:

SAP Blogs

SAP Documents

SAP Help Portal

SAP Notes

 

Thank you for watching

The SAP HANA Academy provides technical enablement, implementation and adoption support for customers and partners with 1000’s of free tutorial videos.

For the full library, see SAP HANA Academy Library – by the SAP HANA Academy.

For the full list of blogs, see Blog Posts – by the SAP HANA Academy.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply