Master Guide | PUBLICSAP HANA Dynamic Tiering 2.0 SP 04Document Version: 1.0 – 2019-04-05

SAP HANA Dynamic Tiering: Master Guide

© 2

020

SAP

SE o

r an

SAP affi

liate

com

pany

. All r

ight

s re

serv

ed.

THE BEST RUN

Content

1 SAP HANA Dynamic Tiering: Master Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

2 Getting Started with SAP HANA Dynamic Tiering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42.1 About This Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42.2 What is Dynamic Tiering?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.3 SAP HANA Dynamic Tiering Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Dbspaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Extended Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

3 Dynamic Tiering Use Cases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143.1 SAP HANA Dynamic Tiering for Older Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143.2 SAP HANA Dynamic Tiering in SAP HANA Data Warehousing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.3 SAP HANA Dynamic Tiering for Big Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.4 SAP HANA, with Dynamic Tiering, as Data Mart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.5 SAP HANA Data Provisioning, with Dynamic Tiering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.6 Business Use Case Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

4 Dynamic Tiering Implementation and Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204.1 Sizing Dynamic Tiering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204.2 SAP HANA Dynamic Tiering Hardware and Operating System Requirements . . . . . . . . . . . . . . . . . . 214.3 Installation Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224.4 Configuration and Follow-Up Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224.5 Administering or Managing Dynamic Tiering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Licensing for Dynamic Tiering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Managing Extended Storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Security Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Backup and Restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26High Availability and Disaster Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26SQL Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

2 PUBLICSAP HANA Dynamic Tiering: Master Guide

Content

1 SAP HANA Dynamic Tiering: Master Guide

This master guide is the entry point for planning your installation of SAP HANA dynamic tiering.

SAP HANA Dynamic Tiering: Master GuideSAP HANA Dynamic Tiering: Master Guide PUBLIC 3

2 Getting Started with SAP HANA Dynamic Tiering

SAP HANA dynamic tiering is part of the SAP HANA landscape.

In this section:

About This Document [page 4]This master guide is the starting point for the technical implementation of SAP HANA dynamic tiering.

What is Dynamic Tiering? [page 5]SAP HANA dynamic tiering is an optional add-on to the SAP HANA database for managing less frequently accessed warm data. Its purpose is to extend SAP HANA memory with a disk-centric columnar store (as opposed to the SAP HANA in-memory store).

SAP HANA Dynamic Tiering Architecture [page 8]You can install SAP HANA and SAP HANA dynamic tiering each on a dedicated server (referred to as a dedicated host deployment) or on the same server (referred to as a same host deployment).

2.1 About This Document

This master guide is the starting point for the technical implementation of SAP HANA dynamic tiering.

This guide provides the following information about dynamic tiering:

● Overview● Architecture● Use cases● Implementation and operation

For information about new features introduced in this release, see What's New in SAP HANA Dynamic Tiering (Release Notes).

Related Information

What's New in SAP HANA Dynamic Tiering 2.0 SP 04

4 PUBLICSAP HANA Dynamic Tiering: Master Guide

Getting Started with SAP HANA Dynamic Tiering

2.2 What is Dynamic Tiering?

SAP HANA dynamic tiering is an optional add-on to the SAP HANA database for managing less frequently accessed warm data. Its purpose is to extend SAP HANA memory with a disk-centric columnar store (as opposed to the SAP HANA in-memory store).

Warm data has relaxed performance requirements compared to highly active hot data. Data in the extended store is online, and available for both queries and updates. Although it is possible to add dynamic tiering to small SAP HANA databases, dynamic tiering is targeted at SAP HANA database sizes of 512 GB and larger, where large data volumes begin to necessitate a data lifecycle management solution.

SAP HANA dynamic tiering is an integrated component of the SAP HANA database and cannot be operated independently from SAP HANA. It provides the ability to create, load data into, and query disk-based, columnar database tables – called extended tables and multistore tables – a type of partitioned SAP HANA column table that has partitions in both SAP HANA default column storage, and dynamic tiering extended storage.

Like in-memory tables, extended and multistore tables are first-class database objects with full ACID compliance. All database requests regarding extended and multistore tables are integrated into SAP HANA’s transactional context. Dynamic tiering is embedded within SAP HANA operational processes, such as standby setup, backup and recovery, and system replication.

Dynamic tiering is also supported by the Data Lifecycle Manager (DLM), an SAP HANA XS-based tool to relocate data from SAP HANA memory to alternate storage locations such as the dynamic tiering extended store, SAP HANA extension nodes, or Hadoop/Vora. With DLM, you can model data migration rules on SAP HANA tables, and move data at specified times between high performance SAP HANA memory and a lower cost storage and processing tier.

Why Use Dynamic Tiering?

The main use case for dynamic tiering is to offload less active data in an SAP HANA data mart from SAP HANA memory to the dynamic tiering disk-backed store.

SAP BW on SAP HANA and SAP BW/4HANA now use HANA extension nodes instead of dynamic tiering for warm data management. Please see the blog SAP BW/4HANA Data Tiering Optimization for additional information about the Data Tiering Optimization framework in SAP BW/4HANA.

The data aging framework of the SAP Business Suite (including S/4HANA) does not support using dynamic tiering. Individual applications of the Business Suite family may support dynamic tiering in an application-specific way – please refer to the documentation of the respective application.

New Features

For summaries of new features, and links to documentation showing new features in use, see What's New in SAP HANA Dynamic Tiering 2.0 SP 04.

SAP HANA Dynamic Tiering: Master GuideGetting Started with SAP HANA Dynamic Tiering PUBLIC 5

High-Level System Characteristics

SAP HANA dynamic tiering exists within the SAP HANA system architecture as a dedicated database process, named esserver. Like the indexserver process, which stores and processes in-memory data, the esserver process stores data in columnar, disk-based structures and offers disk-optimized data processing.

Dynamic tiering is an integrated storage and processing tier within the SAP HANA database. There is a common transaction context across all processes of the SAP HANA system. Relevant processes such as backup and recovery, and system replication include dynamic tiering data if dynamic tiering is installed on the SAP HANA system.

In production environments, the esserver process is normally operated on a dedicated host, but esserver may be co-deployed on the same host as SAP HANA for scale up (single node) systems. For SAP HANA scale out systems, esserver should still be installed on its own machine. Comparable to setting up an SAP HANA standby server, you can set up a standby dynamic tiering server with automatic failover capability.

SAP has begun to validate public cloud environments for dynamic tiering. See SAP Note 2555629 - SAP HANA 2.0 Dynamic Tiering – Hypervisor and Cloud Support .

With multiple tenant databases, a dedicated esserver process and dynamic tiering extended store is required for each tenant database using dynamic tiering. Currently, dynamic tiering does not support high tenant isolation.

Dynamic tiering is not scale-out enabled. Only one dynamic tiering worker host and one optional dynamic tiering standby host is allowed for each database in an SAP HANA system. The in-memory part of the SAP HANA system can be a scale-out setup with multiple hosts running indexserver processes.

Sizing and Implementation Characteristics

Since SAP HANA dynamic tiering is disk-centric technology rather than memory-only technology, it is sized differently from a pure SAP HANA system. Sizing is described in the SAP HANA 2.0 Dynamic Tiering Best Practices Guide . If you plan to build a production SAP HANA setup including dynamic tiering, contact SAP for expert sizing advice.

For a given SAP HANA system, the size of the dynamic tiering extended store should not be arbitrarily large compared to the memory size of the SAP HANA system. See SAP Note 2086829 - SAP HANA Dynamic Tiering Sizing Ratios .

Functional Restrictions

NoteFor the latest information on known functional restrictions in SAP HANA dynamic tiering SP 04, see SAP Note 2636634 - SAP HANA Dynamic Tiering 2.0 SP 04 Release Note .

6 PUBLICSAP HANA Dynamic Tiering: Master Guide

Getting Started with SAP HANA Dynamic Tiering

There are several functional restrictions of an SAP HANA system with dynamic tiering compared to an SAP HANA system without dynamic tiering. Many of these functional restrictions will be addressed in future releases:

Functional Restriction Details

Backup and Recovery; High Availability

Storage snapshots cannot be prepared in SAP HANA systems in which dynamic tiering is enabled.

SAP HANA system replication is supported with dynamic tiering, but there are some behavioral differences compared to an SAP HANA system without dynamic tiering. See SAP Note 2447994 - SAP HANA Dynamic Tiering Support for SAP HANA System Replication .

Dynamic tiering supports file-based full backups, delta backups, point-in-time recover, and the BACKINT interface. See SAP Note 2375865 - SAP HANA Dynamic Tiering 2.0: Backup and Recovery Functional Restrictions .

Platform Scale-out of dynamic tiering is not available. There can be only one dynamic tiering worker host for the esserver process of a given SAP HANA database.

Each tenant database that requires dynamic tiering needs a dedicated esserver process and storage.

Encryption Encryption of the data in the SAP HANA dynamic tiering extended store is supported, but changing the encryption key or encryption state of the extended store requires a full data backup and recovery operation.

Dynamic tiering supports encrypted full backups. Delta and log backups have the encryption state of the HANA database.

Point-in-time recovery is not possible when performing a recovery to a target system with a different encryption state from the source system.

Data Loading There is no automatic movement of data between memory and dynamic tiering for extended tables or multistore tables. Such movement must be triggered explicitly by applications or administrators. The DLM tool of the SAP HANA Data Warehousing Foundation helps split a single table into in-memory and disk-based parts, based on configurable rules, including scheduling for the data movement.

Binary EXPORT and IMPORT are available for extended tables and multistore tables.

Data Modeling There are a small number of known differences for data types supported by SAP HANA and dynamic tiering. These differences are documented in Supported Data Types.

Geospatial and time series data types and related functions are not supported on extended or multistore tables.

The creation of information models that read from extended or multistore tables is limited to calculation views.

Calculated columns (DDL: GENERATED ALWAYS AS) are not supported for extended or multistore tables.

SAP HANA Dynamic Tiering: Master GuideGetting Started with SAP HANA Dynamic Tiering PUBLIC 7

Functional Restriction Details

SAP HANA full-text indexes cannot be added to extended tables or the dynamic tiering partitions of multistore tables. Similarly, data in dynamic tiering cannot be used in text search, text analysis, and text mining.

Extended tables and the dynamic tiering partitions of multistore tables can be used in the context of application function libraries such as PAL or BFL, but the data will first be copied into SAP HANA memory for execution in the SAP HANA column store.

2.3 SAP HANA Dynamic Tiering Architecture

You can install SAP HANA and SAP HANA dynamic tiering each on a dedicated server (referred to as a dedicated host deployment) or on the same server (referred to as a same host deployment).

The main SAP HANA dynamic tiering host is known as the worker. You can also install a second dynamic tiering host, known as the standby, to provide failover functionality for high availability. A standby does not require a separate dynamic tiering license but it does require its own dedicated server in a dedicated host deployment.

Only one dynamic tiering license is allowed per SAP HANA system. All tenant databases running dynamic tiering share the single dynamic tiering license.

The SAP HANA host and SAP HANA dynamic tiering worker communicate over a secure, encrypted internal connection. For network and communication security information, see the SAP HANA Security Guide.

Use the SAP HANA client interfaces to manage and monitor dynamic tiering. Use SAP HANA cockpit to monitor system information for the dynamic tiering host, including resource utilization and table usage statistics, and to manage extended storage. Use the HANA studio for dynamic tiering administration tasks, including managing extended store tables. The OS process for the dynamic tiering host is hdbesserver, and the service name is esserver.

To maximize native query performance, query optimizations ship the query operations to either the hot store or extended storage. Query operations against extended storage data are pushed down to the dynamic tiering worker, minimizing the load on the SAP HANA host.

SAP HANA dynamic tiering only supports low tenant isolation. Any attempt to provision the dynamic tiering service (esserver) to a tenant database with high-level tenant isolation fails. If you raise the isolation level to high for an existing installation, the dynamic tiering service stops working. To lower the isolation level, see Decrease the System Isolation Level in the SAP HANA Administration Guide.

8 PUBLICSAP HANA Dynamic Tiering: Master Guide

Getting Started with SAP HANA Dynamic Tiering

In a dedicated host deployment, each tenant using dynamic tiering has its own dedicated host on which the dynamic tiering service runs. The landscape of this type of deployment could look similar to the following:

Figure 1: Components of SAP HANA Dynamic Tiering – Dedicated Host Deployment

In a same host, single-tenant deployment, the dynamic tiering service (esserver) and the SAP HANA service (indexserver) coexist on the same host. For a single tenant system with multiple SAP HANA indexservers,

SAP HANA Dynamic Tiering: Master GuideGetting Started with SAP HANA Dynamic Tiering PUBLIC 9

the dynamic tiering service (esserver) can coexist with any one of the indexserver hosts. The landscape of this type of deployment could look similar to the following:

Figure 2: Components of SAP HANA Dynamic Tiering – Same Host Deployment – Single Tenant

Finally, if there are multiple tenants running dynamic tiering, the dynamic tiering service (esserver) and SAP HANA service (indexserver) can coexist on the same host for only one tenant. Additional tenants running dynamic tiering require a dedicated host for the dynamic tiering service. The landscape of this type of deployment could look similar to the following:

10 PUBLICSAP HANA Dynamic Tiering: Master Guide

Getting Started with SAP HANA Dynamic Tiering

Figure 3: Components of SAP HANA Dynamic Tiering – Same Host Deployment – Multiple Tenants

In this section:

Dbspaces [page 12]SAP HANA dynamic tiering introduces the dbspace object to SAP HANA.

Extended Tables [page 12]Like all other SAP HANA tables, extended tables are maintained in the SAP HANA catalog as first class elements of the database, but their data resides in a dbspace in disk-based extended storage.

Related Information

Administering or Managing Dynamic Tiering [page 22]High Availability and Disaster Recovery [page 26]SAP HANA Administration GuideSAP HANA Master Guide

SAP HANA Dynamic Tiering: Master GuideGetting Started with SAP HANA Dynamic Tiering PUBLIC 11

2.3.1 Dbspaces

SAP HANA dynamic tiering introduces the dbspace object to SAP HANA.

On-disk storage is divided into units called dbspaces. A dbspace is a logical name for a container of files or raw partitions. Dynamic tiering uses these dbspaces:

● ES_SYSTEM● ES_TEMP● ES_USER● ES_DELTA (Optional)

Only one ES_USER dbspace is allowed per dynamic tiering host.

For details on managing dbspaces, see the SAP HANA Dynamic Tiering: Administration Guide.

Related Information

SAP HANA Dynamic Tiering: Administration Guide

2.3.2 Extended Tables

Like all other SAP HANA tables, extended tables are maintained in the SAP HANA catalog as first class elements of the database, but their data resides in a dbspace in disk-based extended storage.

Not all SQL statement clauses are supported by extended tables. For details on functional restrictions for extended tables, see Extended Store Table Functional Restrictions in the SAP HANA Dynamic Tiering: Administration Guide.

An extended table can be delta-enabled, meaning it supports multiple concurrent writes using row-level versioning (RLV).

With extended tables, you can perform the following import and export scenarios:

● Insert data from an external database directly into an extended table.● Import data from a file into an extended table.● Export extended table data to a file.

Since it's the application that has the best understanding of data temperature — for example, when data can be considered old, and what data is not needed as frequently — data movement is handled at the application level. To move data between the in-memory tier, and the extended storage tier, you should use the Data Lifecycle Manager tool. You can specify rules and schedules in Data Lifecycle Manager for automating the movement of in-memory data to extended storage. You will, however, need to specify rules for each table you want the tool to age to extended storage. See the Tools for Administration and Monitoring in the SAP HANA Dynamic Tiering: Administration Guide for more information on the Data Lifecycle Manager, which is part of the SAP HANA Data Warehousing Foundation option

12 PUBLICSAP HANA Dynamic Tiering: Master Guide

Getting Started with SAP HANA Dynamic Tiering

Related Information

SAP HANA Dynamic Tiering: Administration GuideTools for Administration and MonitoringExtended Store Table Functional Restrictions

SAP HANA Dynamic Tiering: Master GuideGetting Started with SAP HANA Dynamic Tiering PUBLIC 13

3 Dynamic Tiering Use Cases

Use SAP HANA dynamic tiering when it is more cost-effective to move cooler data out of SAP HANA tables and into extended tables.

In this section:

SAP HANA Dynamic Tiering for Older Data [page 14]Migrate hot SAP HANA data to warm or cold disk-based extended storage as the data ages. Extended storage reduces the footprint of your SAP HANA in-memory database, and applies cost-efficient storage and processing technologies to your data, depending on its value.

SAP HANA Dynamic Tiering in SAP HANA Data Warehousing [page 15]SAP HANA dynamic tiering is a component in the SAP HANA data warehouse platform.

SAP HANA Dynamic Tiering for Big Data [page 16]Use SAP HANA dynamic tiering to add a big data extension to SAP HANA using disk-based, columnar extended storage.

SAP HANA, with Dynamic Tiering, as Data Mart [page 16]Data mart is an industry term for a repository of data gathered from operational data originating in transactional systems (or other sources), designed to serve a particular community of information workers by forming a basis for analytics, reporting, or a specific use in another type of application.

SAP HANA Data Provisioning, with Dynamic Tiering [page 18]In-memory reporting and analysis of business data require loading business data from a source system to the SAP HANA database. You can add SAP HANA dynamic tiering to your SAP HANA system for warm data management.

Business Use Case Examples [page 19]Use SAP HANA dynamic tiering when it is more cost-effective to move cooler, or large-volume data, out of SAP HANA tables and into extended tables.

3.1 SAP HANA Dynamic Tiering for Older Data

Migrate hot SAP HANA data to warm or cold disk-based extended storage as the data ages. Extended storage reduces the footprint of your SAP HANA in-memory database, and applies cost-efficient storage and processing technologies to your data, depending on its value.

To move data to warm storage, convert HANA tables to extended tables using SQL or SAP Cockpit. See Extended Store Tables in the SAP HANA Dynamic Tiering: Administration Guide.

Related Information

Extended Store Tables

14 PUBLICSAP HANA Dynamic Tiering: Master Guide

Dynamic Tiering Use Cases

Extended Tables [page 12]

3.2 SAP HANA Dynamic Tiering in SAP HANA Data Warehousing

SAP HANA dynamic tiering is a component in the SAP HANA data warehouse platform.

Large enterprise data warehouse (EDW) solutions manage massive amounts of data — even more than can fit in SAP HANA memory. In an EDW where the data is mostly read-only, you can use SAP HANA dynamic tiering and Hadoop as different storage tiers.

Figure 4: Dynamic Tiering in EDW

Dynamic tiering adds scalability to your EDW, with extreme storage capability to accommodate future data growth.

SAP HANA Dynamic Tiering: Master GuideDynamic Tiering Use Cases PUBLIC 15

3.3 SAP HANA Dynamic Tiering for Big Data

Use SAP HANA dynamic tiering to add a big data extension to SAP HANA using disk-based, columnar extended storage.

Extended tables provide a cost-effective solution for storing massive amounts of infrequently used business data. Store warm and cool data in extended storage when the inherently lower latency of in-memory data is a lower priority. Hot data remains in the SAP HANA hot store, while cooler data is stored in extended tables.

Figure 5: Big Data Use Case

3.4 SAP HANA, with Dynamic Tiering, as Data Mart

Data mart is an industry term for a repository of data gathered from operational data originating in transactional systems (or other sources), designed to serve a particular community of information workers by forming a basis for analytics, reporting, or a specific use in another type of application.

With SAP HANA, operational data marts offer real-time analytics and reporting on data replicated from a transactional system database. The raw tables themselves are copied (structure and data) from the transactional system database into SAP HANA. You can add SAP HANA dynamic tiering to the SAP HANA system to provide warm data management.

16 PUBLICSAP HANA Dynamic Tiering: Master Guide

Dynamic Tiering Use Cases

Figure 6: Data Mart Use Case

For information on the use case SAP HANA as Data Mart, see the SAP HANA Master Guide.

Related Information

SAP HANA Master Guide

SAP HANA Dynamic Tiering: Master GuideDynamic Tiering Use Cases PUBLIC 17

3.5 SAP HANA Data Provisioning, with Dynamic Tiering

In-memory reporting and analysis of business data require loading business data from a source system to the SAP HANA database. You can add SAP HANA dynamic tiering to your SAP HANA system for warm data management.

Figure 7: Data Provisioning Use Case

For information on the use case SAP HANA Data Provisioning, see the SAP HANA Master Guide.

Related Information

SAP HANA Master Guide

18 PUBLICSAP HANA Dynamic Tiering: Master Guide

Dynamic Tiering Use Cases

3.6 Business Use Case Examples

Use SAP HANA dynamic tiering when it is more cost-effective to move cooler, or large-volume data, out of SAP HANA tables and into extended tables.

Example Description

Public utility The utility company stores hot enterprise data in SAP HANA tables and massive amounts of cooler smart meter data in extended tables. Queries identify operational problems and estab­lish incentive pricing for more efficient energy use.

Financial services Stock ticker data streams into SAP HANA tables for immediate price fluctuation analysis and trading actions, while historical stock price data is stored in extended tables for trend analysis and portfolio management.

Telecommunications The telecommunications company stores customer loyalty data in SAP HANA tables, and net­work service data in extended tables. Analyzing the network service data and correlating with customer loyalty data anticipates customer loss, and initiates customer retention programs.

SAP HANA Dynamic Tiering: Master GuideDynamic Tiering Use Cases PUBLIC 19

4 Dynamic Tiering Implementation and Operation

The implementation and operation of SAP HANA dynamic tiering depends on the chosen installation use case and the technical deployment.

In this section:

Sizing Dynamic Tiering [page 20]This topic describes sizing for just the SAP HANA dynamic tiering host machine.

SAP HANA Dynamic Tiering Hardware and Operating System Requirements [page 21]SAP HANA dynamic tiering has its own software and hardware requirements, which are not the same as SAP HANA. However, both SAP HANA and dynamic tiering hosts require the same operating system and support patch level.

Installation Procedure [page 22]Installation scenarios vary depending on your business requirements, but regardless of scenario, all instructions assume that you have a working SAP HANA system to which you are adding dynamic tiering.

Configuration and Follow-Up Activities [page 22]Post-installation configuration steps are not in the SAP HANA Dynamic Tiering: Installation and Update Guide.

Administering or Managing Dynamic Tiering [page 22]SAP HANA dynamic tiering administration features include security administration, backup and restore of extended storage, extended storage management, and SQL commands specific to dynamic tiering.

4.1 Sizing Dynamic Tiering

This topic describes sizing for just the SAP HANA dynamic tiering host machine.

For sizing information for the machine where SAP HANA is installed, see the SAP HANA Master Guide.

For SAP HANA dynamic tiering sizing guidelines, see SAP Note 2086829 – SAP HANA DT: Sizing of Dynamic Tiering component of SAP HANA .

Related Information

SAP Note 2086829 - SAP HANA Dynamic Tiering Sizing RatiosSAP HANA Master Guide

20 PUBLICSAP HANA Dynamic Tiering: Master Guide

Dynamic Tiering Implementation and Operation

4.2 SAP HANA Dynamic Tiering Hardware and Operating System Requirements

SAP HANA dynamic tiering has its own software and hardware requirements, which are not the same as SAP HANA. However, both SAP HANA and dynamic tiering hosts require the same operating system and support patch level.

SAP HANA Dynamic Tiering Version Compatibility

Ensure that you are installing the version of dynamic tiering that is compatible with your version of SAP HANA. For a list of compatible versions, see SAP Note 2636634 – SAP HANA Dynamic Tiering 2.0 SP 04 Release Note.

SAP HANA Dynamic Tiering Host Operating System Requirements

Dynamic tiering is available for:

● Intel-based hardware platforms● IBM Power Systems

Dynamic tiering supports the same operating systems as SAP HANA core. For an SAP HANA landscape with dynamic tiering, both products must be running using the same operating system.

NoteIBM Power Systems environments require the appropriate IBM XL C/C++ redistributable libraries. Download and install the appropriate runtime environment from the Latest updates for supported IBM C and C++ Compilers page on the IBM Support Portal. Install the libraries on both the SAP HANA and dynamic tiering hosts. These libraries are not required for an Intel-based hardware platform environment.

SAP HANA Dynamic Tiering Host Hardware Requirements

The dynamic tiering worker and (optional) standby and secondary worker hosts require the same hardware layout; otherwise, there are no specific hardware requirements. Its specifications do not need to match those of the SAP HANA host. Choose the hardware to meet your dynamic tiering requirements.

SAP HANA Dynamic Tiering: Master GuideDynamic Tiering Implementation and Operation PUBLIC 21

4.3 Installation Procedure

Installation scenarios vary depending on your business requirements, but regardless of scenario, all instructions assume that you have a working SAP HANA system to which you are adding dynamic tiering.

There are two installation scenarios for installing SAP HANA dynamic tiering.

● SAP HANA 2.0 and SAP HANA dynamic tiering services each have a dedicated host.● SAP HANA and SAP HANA dynamic tiering services share a common host.

The SAP HANA Dynamic Tiering: Installation and Update Guide provides detailed steps for each scenario.

To upgrade or install SAP HANA, see the SAP HANA Server Installation and Update Guide. To install dynamic tiering, see the SAP HANA Dynamic Tiering: Installation and Update Guide.

Related Information

SAP HANA Dynamic Tiering: Installation and Update GuideSAP HANA Server Installation and Update Guide

4.4 Configuration and Follow-Up Activities

Post-installation configuration steps are not in the SAP HANA Dynamic Tiering: Installation and Update Guide.

SAP HANA dynamic tiering configuration information is in the SAP HANA Dynamic Tiering: Administration Guide.

Procedures for starting and stopping the SAP HANA dynamic tiering service are in the SAP HANA Dynamic Tiering: Installation and Update Guide or SAP HANA Dynamic Tiering: Administration Guide.

Related Information

SAP HANA Dynamic Tiering: Installation and Update GuideSAP HANA Dynamic Tiering: Administration Guide

4.5 Administering or Managing Dynamic Tiering

SAP HANA dynamic tiering administration features include security administration, backup and restore of extended storage, extended storage management, and SQL commands specific to dynamic tiering.

22 PUBLICSAP HANA Dynamic Tiering: Master Guide

Dynamic Tiering Implementation and Operation

In this section:

Licensing for Dynamic Tiering [page 23]SAP HANA dynamic tiering requires its own license, separate from the SAP HANA license.

Managing Extended Storage [page 24]As a database administrator, you perform operational tasks related to the administration, monitoring, and maintenance of SAP HANA dynamic tiering.

Security Administration [page 24]Security features ensure the security of SAP HANA dynamic tiering.

Backup and Restore [page 26]A full backup automatically backs up and restores dynamic tiering data.

High Availability and Disaster Recovery [page 26]SAP HANA dynamic tiering supports system replication and both automatic and manual failover.

SQL Reference [page 26]For SQL reference information specific to SAP HANA dynamic tiering, see the SAP HANA SQL and System Views Reference.

4.5.1 Licensing for Dynamic Tiering

SAP HANA dynamic tiering requires its own license, separate from the SAP HANA license.

SAP HANA dynamic tiering is licensed by the amount of data in extended storage. Only one dynamic tiering license is allowed per SAP HANA system.

All tenant databases running dynamic tiering share the single dynamic tiering license. In a multitenant database container environment, licenses need to be installed on the System DB. See 2665297 .

Consistent with SAP HANA, a new installation of dynamic tiering includes a temporary license allowing dynamic tiering to run without a permanent license for 90 days. After 90 days, a permanent license is required. If a temporary license expires without a permanent license being installed, dynamic tiering ceases to function until you install a valid permanent license. If an installed permanent license expires, a temporary license is issued, valid for 28 days.

Depending on whether SAP HANA and dynamic tiering were installed together or at different times, the expiration dates of the individual temporary licenses may differ.

For more information on license types, checking the current license key, and installing or deleting a permanent license, see System Administration > Managing SAP HANA Licenses in the SAP HANA Administration Guide.

Related Information

Managing SAP HANA Licenses

SAP HANA Dynamic Tiering: Master GuideDynamic Tiering Implementation and Operation PUBLIC 23

4.5.2 Managing Extended Storage

As a database administrator, you perform operational tasks related to the administration, monitoring, and maintenance of SAP HANA dynamic tiering.

Administration tasks include:

● Creating extended storage● Removing extended storage● Managing space● Managing extended tables● Managing data● Monitoring extended storage

See the SAP HANA Dynamic Tiering: Administration Guide.

Related Information

SAP HANA Dynamic Tiering: Administration Guide

4.5.3 Security Administration

Security features ensure the security of SAP HANA dynamic tiering.

Secure Internal Communications

Internal communications between the dynamic tiering host and the SAP HANA database are secured by the SSL protocol and certificate mutual authentication.

24 PUBLICSAP HANA Dynamic Tiering: Master Guide

Dynamic Tiering Implementation and Operation

Figure 8: Secure Communications in Dynamic Tiering with Tenant Databases

Technical Database User

SAP HANA dynamic tiering adds the user _SYS_ES to the list of SAP HANA standard users. _SYS_ES is a technical user used by dynamic tiering. _SYS_ES logs on internally through the dynamic tiering service. You cannot log on with this user.

System Configuration and Administration Privileges

SAP HANA system configuration and administration privileges support SAP HANA dynamic tiering.

For more information on SAP HANA dynamic tiering security, see the SAP HANA Security Guide.

Related Information

SAP HANA Security Guide

SAP HANA Dynamic Tiering: Master GuideDynamic Tiering Implementation and Operation PUBLIC 25

4.5.4 Backup and Restore

A full backup automatically backs up and restores dynamic tiering data.

Once you install SAP HANA dynamic tiering, perform a full backup to back up the entire system, including extended storage. During a backup, SAP HANA Studio shows dynamic tiering backup progress.

For details on dynamic tiering backup and restore, see the SAP HANA Dynamic Tiering: Administration Guide.

Related Information

SAP HANA Dynamic Tiering: Administration Guide

4.5.5 High Availability and Disaster Recovery

SAP HANA dynamic tiering supports system replication and both automatic and manual failover.

System replication requires a secondary system with the same SID and the same number of SAP HANA and dynamic tiering worker hosts. The number of standby hosts does not need to be identical.

Automatic failover is available when the dynamic tiering worker and standby hosts are assigned to the same high availability group. Manual failover is available when the worker and standby hosts are assigned to different, unique, high availability groups.

For information on configuring high availability options, see the SAP HANA Dynamic Tiering: Administration Guide.

Related Information

SAP HANA Dynamic Tiering: Administration Guide

4.5.6 SQL Reference

For SQL reference information specific to SAP HANA dynamic tiering, see the SAP HANA SQL and System Views Reference.

Related Information

SAP HANA SQL and System Views Reference

26 PUBLICSAP HANA Dynamic Tiering: Master Guide

Dynamic Tiering Implementation and Operation

Important Disclaimers and Legal Information

HyperlinksSome links are classified by an icon and/or a mouseover text. These links provide additional information.About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any

damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Videos Hosted on External PlatformsSome videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within the control or responsibility of SAP.

Beta and Other Experimental FeaturesExperimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the experimental features in a live operating environment or with data that has not been sufficiently backed up.The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example CodeAny software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Gender-Related LanguageWe try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

SAP HANA Dynamic Tiering: Master GuideImportant Disclaimers and Legal Information PUBLIC 27

www.sap.com/contactsap

© 2020 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.

Please see https://www.sap.com/about/legal/trademark.html for additional trademark information and notices.

THE BEST RUN