In April 2017, we discussed the changes SAP customers face when using SAP HANA 2.0 SPS1 and how the upcoming NetApp® SnapCenter® 3.0 release will be able to protect SAP HANA 1.0 single-container and SAP HANA 2.0 multitenant database container (MDC) single-tenant databases. In today’s blog post, we share a sneak preview of the SnapCenter architecture and describe how the restore and recovery process changes with SAP HANA MDC single-tenant databases. Note that the information in this blog is based on the official beta version, and all restrictions mentioned in the legal disclaimer at the end of this blog post apply.


SnapCenter Architecture Overview

SnapCenter is a unified, scalable platform for application-consistent data protection. SnapCenter Server is a Windows application enabling load balancing and high availability with a single centralized HTML5-based user interface. SnapCenter 3.0 will ship with a SAP HANA plug-in package installable on Windows and Linux servers.


Installing this HANA plug-in along with the SAP hdbsql client and hdbuserstore software on a communication host allows SnapCenter to communicate with SAP HANA databases over the network. In our lab setup, the SAP HANA plug-in uses the SnapCenter Server host as a communication host, a typical setup for smaller deployments. Figure 1 illustrates this lab setup.


Figure 1) Lab Setup

SAP HANA MDC Single-Tenant Databases

One technical change coming to SAP HANA MDC is that, even with only one tenant, the SAP HANA system now hosts two databases: the tenant database and a system database. The underlying storage architecture hasn’t changed, and SnapCenter still has to create a Snapshot® copy of a single datastore to back up an SAP HANA system. However, the SQL communication has changed because now both the tenant database and the system database are treated as separate entities inside SAP HANA.


The SnapCenter SAP HANA plug-in is adapted to these SQL changes and provides a simple but effective user interface for backup, restore, and system clone. What changes for the user is the recovery procedure using SAP HANA Studio or SAP HANA Cockpit when dealing with SAP HANA MDC databases.


A restore based on Snapshot copies restores both the tenant database and system database, which requires that both of these databases be recovered. The following video gives a short overview of the lab setup and shows a complete restore and recovery process using a beta preview version of SnapCenter 3.0.



With the upcoming SnapCenter® 3.0 release NetApp customers can embrace the fast and reliable data protection and integrated SAP HANA catalog management for SAP HANA single-container as well as SAP HANA 2.0 SPS1 MDC single-tenant databases.

Legal Disclaimer

This blog post describes possible future NetApp developments, products, and/or platform directions and functionality that are subject to change without notice. The information in this blog post is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. This blog post is for informational purposes only. NetApp assumes no responsibility for errors or omissions in this blog post.


See also my previous blog post: SAP HANA 2.0 SPS 01 & What It Means for Data Protection.

Bernd Herth

Bernd Herth architects and defines NetApp's SAP solutions as TME at the SAP Partner Port at SAP headquarters in Walldorf. He has over 25 years of experience in SAP software and in planning and architecting infrastructure solutions for SAP and has held various positions in the SAP ecosystem. Herth has published articles and books focused on SAP technology and virtualization. He holds a masters degree in physics and taught computer science classes as assistant professor.

Add comment