SAP HANA Multi Tier Storage edition
SAP HANA converges database and application platform capabilities in memory to accelerate transactions and analytics so that businesses can operate in real time. As customer adoption grows for SAP HANA, the
combined compute and analytics capabilities become more and more
central to customers environments.
Data services demands are high for
even the smallest SAP HANA databases.
SAP HANA Multi Tier Storage
edition will help to optimize the main memory resource management even
further than the concept of active/non-active data. This has a positive
effect on hardware sizing, especially when dealing with a large quantity
of warm data in the persistent staging area tables (PSA tables) and write-optimized DataStore objects, which
need to be available for extended tables.
SAP HANA Tailored Data Center Integration (TDI)
For many customers, SAP HANA is considered mission critical. Your hardware storage solution should meet the high-availability and resiliency demands of SAP HANA. You need to make sure that high availability is built into your hardware storage architecture through full hardware redundancy.
As the SAP HANA database resides in memory,
storage has a different role. Instead of housing the database itself,
storage for SAP HANA provides persistence. Persistence storage holds
copies of the in-memory data, logs, & save point data. While the role
of storage for SAP HANA is different than with traditional database
storage, the demands of performance, availability, and tier 1 data
services remain high.
SAP HANA, Multi-Tier Storage includes the following Runtime Software:
- SAP Sybase IQ Enterprise Edition
- SAP Sybase IQ Enterprise Edition-Very Large Database Management Option
- SAP Sybase IQ Enterprise Edition-Unstructured Data Analytics Option
The key features of SAP HANA include:
- Database and data processing services: SAP HANA is an in-memory, columnar,
massively parallel processing platform that provides a common database
for OLTP and OLAP, reducing redundancy and latency.
- Real-time analytics: With OLAP and OLTP stored together, SAP HANA
provides on-the-fly analysis so that users can make real-time decisions
using data from SAP, custom, or third-party applications.
- Big Data warehousing: Customers can unleash the potential of Big Data by handling large volumes of structured and unstructured data in real time.
SAP HANA TDI can appear to be complex, but this framework, comprised of five phases, breaks down any complexity. Each phase has activities and deliverables to help ensure that your technical and business requirements are met. These five phases are:
Analysis & Strategy: The most important phasesets the business content and requirements for the entire effort.
Architect & Validate: The phase brings all the components together and verifies that requirements are being met.
Detail Design: The phase sets the stage for a successful implementation based on the best and most effective solution.
Implement: The phase provides for a rapid deployed mission-critical infrastructure built and tested for SAP HANA.
Manage: The final phase of the framework that focuses on operational excellence.
SAP HANA Supported Servers: SAP HANA
implementations usually are delivered as highly optimized appliances.
The appliance approach offers a well-defined out-of-the-box hardware and
software solution designed to satisfy the high-performance needs of an
in-memory database solution. A list of validated servers can be found
on the SAP HANA Product Availability Matrix (PAM). SAP builds on open
source and industry standards for processors, memory, and operating
systems as the core platform for SAP HANA to drive TCO reduction. SUSE
Linux®, SUSE Linux Enterprise Server (SLES) 11 SP3, or SLES for SAP
applications SP3 or Red Hat® Enterprise Linux for SAP HANA 6.5 are the
supported operating systems.
SAP HANA Dynamic Tiering
SAP HANA Dynamic Tiering enables you to optimize the main memory resource management in SAP HANA by using extended tables for BW objects with warm data: Extended tables are tables managed by SAP HANA.
SAP HANA Enterprise Storage
In all standard SAP HANA environments, the storage requirement given in the SAP HANA Storage Requirements white paper needs to be fulfilled. All internal disks can be removed from the configuration as the log and data volumes may reside on the enterprise storage array.
Built-in High Availability in Storage Solutions: The
SAP client used with your hardware Storage system configuration should
provide a highly available SAP HANA deployment. If one SAP HANA node
fails, the defined stand-by node request access to the data and log
devices of the failed node and automatically recovers the SAP HANA
persistence of the failed node to enable continued SAP HANA operations.
Storage Virtual Volume (VV) Definition
For each SAP HANA server, a Virtual Volume has to be defined and exported to all SAP HANA servers or server blades. The characteristics of the VVs in terms of RAID level would be a good illustration. The size of the VVs is considered to be usually the same as the amount of memory being used in the scale-out servers.
Backup and recovery
A complete data backup or storage snapshot is required to protect against data loss resulting from corrupt storage. A data backup writes the payload (that is the actual data and not unused space) in the data area and log area to different backup destinations.
A storage snapshot captures the whole content of the data area. Data backups and storage snapshots are created while the SAP HANA database is running. While a backup is being created, the impact on system performance is negligible, and users can continue to work normally. The operating system as well as the SAP HANA configuration needs to be backed up. This needs to be part of the standard backup concept for operating systems.
SAP HANA itself has two types of backups:
- Data backups can be triggered manually or scheduled in the SAP HANA Studio, DBA Cockpit, or by SQL commands. A data backup effectively replicates a database savepoint to the backup destination.
- Log backups occur automatically when a log segment (a log segment is represented by a file on disk with a fixed size) fills up or a configurable time threshold is exceeded. The log segment is copied to the backup destination. This may happen in parallel to a data backup.
Both types of backup are needed to recover the database to a specific point in time.
SAP HANA offers three options to back up the database:
- File system
- Storage snapshot
Storage integration with VMware
As SAP HANA adoption grows, customers are increasingly requesting virtualization of SAP HANA workloads. This capability is a requirement for both appliance and SAP HANA TDI workloads and those implemented in house and by service providers. With the release of VMware® vSphere 5.5, SAP now supports VMware virtualization for production of SAP HANA workloads.