You are on page 1of 18

SAP HANA

Landscape Definition Guide for SAP HANA®


– Best Practices for a Successful Deployment
© 2017 SAP SE or an SAP affiliate company. All rights reserved.

1 / 17
Table of Contents

4 Available Deployment Models

8 Conduct Sizing of Your Hardware


Components

9 Define Your Hardware Requirements

10 Define Your Cluster Strategy (Scale-Up


or Scale-Out)

12 Decide on Multitenancy and


Virtualization Options

15 Define a High-Availability and


Disaster-Recovery Strategy and System
Replication Requirements

16 Change Management

2 / 17

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


To get the most out of the SAP HANA® business data platform, it is mission critical
to outline a blueprint for its deployment. One of the main drivers for best total cost
of ownership (TCO) of an SAP HANA deployment is optimizing the management
and operations costs by designing an efficient IT landscape. The following ap-
proach covers some best practices that may help you define the most suitable IT
landscape for your deployment with regard to performance, scalability, adaptability,
administration effort, and cost-effectiveness.

SYSTEM LANDSCAPE AND PROJECT


Figure 1: System Landscape and Project Planning
PLANNING
Procedure for an SAP HANA Deployment
A system landscape and project planning proce-
dure for an SAP HANA deployment typically Deployment model
covers the following steps (see Figure 1):
1. Define the deployment options either in the
data center (on premise) or in the cloud, per On premise Cloud
your business needs.
2. Define the general technical architecture –
that is, the components required and the New hardware? Private, Public
sizing for all components. Map the sizing managed cloud cloud
results to your hardware. No
3. Define the hardware acquisition requirements
Yes
depending on your deployment model.
4. Define your cluster strategy (scale-in and Appliance
Tailored data-center
scale-out) and number of systems. integration
5. Deploy different components and
virtualization options for setting up each
system. Sizing
6. Define a strategy for high availability and
Data volume management
disaster recovery. and cluster strategy
7. Define a software change management
landscape and evaluate update options. Technical
deployment plan

Virtualization, multiple
Disaster-recovery
components, one database
and high-availability
and multiple components, one
strategy
system, multitenancy

Software change management


landscape
3 / 17

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


Available Deployment Models
SAP HANA can be deployed in different ways. Options for SAP HANA as a development platform
Here is an overview of all available options include SAP HANA, express edition, which is a plat-
offered by SAP today. Each of them will be form to develop data-driven appli­cations based
explained and mapped to applicable business on SAP HANA, available for download from the
scenarios. SAP developer center free of charge. This version
of SAP HANA can be installed on laptop or desktop
Options for SAP HANA in your data center com­puters, Linux-based servers, virtual machines,
(on premise) include: or a private cloud (see the “Which Deployment
•• Appliance – Bare-metal single server or Model for Which Business Scenario?” section for
scale-out (see the “Define Your Cluster Strategy more details).
(Scale-Up or Scale-Out)” section) as a
preconfigured validated stack, delivered Our implementation support team is happy to
together with the corresponding hardware assist you in developing a business case for your
•• SAP HANA tailored data center integration – SAP HANA journey and choosing the right deploy-
Uses the existing hardware and operations in ment model that fits your needs exactly.
your data center
•• Virtualized – Hosts multiple, isolated database WHICH DEPLOYMENT MODEL FOR WHICH
instances on one or more servers so that each BUSINESS SCENARIO?
database instance appears as if it is running The following maps the various deployment
on a separate machine models for SAP HANA to the most typical business
•• SAP HANA, Edge edition, advanced version – scenarios.
Special package dedicated to subject-matter
experts, delivered by SAP partners as an You may choose the appliance offering if you:
appliance or deployed using SAP HANA tailored •• Need to comply with industry-specific security,
data center integration privacy, or control requirements (for example,
in banking)
Options for SAP HANA in the cloud include: •• Are looking for the fastest-possible
•• SAP HANA Enterprise Cloud – Private cloud implementation on premise
service managed by SAP •• Are looking for an all-inclusive prepackaged
•• SAP HANA Infrastructure Services technology offering ready to run in your data center
– Public cloud infrastructure as a service (IaaS)
that offers you the ability to run your own licensed
SAP HANA software, including the advanced
version of SAP HANA, Edge edition, on Amazon
Web Services (AWS), Microsoft Azure, Google
Cloud Platform, or IBM Bluemix Cloud
•• SAP® Cloud Platform – Open and public
platform-as-a-service (PaaS) offering, with
SAP HANA database as a service (DBaaS) and
advanced analytical data-processing services

4 / 17
You may choose SAP HANA tailored data center •• Want to extend your on-premise landscape
integration if: with innovative applications delivered through
•• Your business model requires running SAP HANA Enterprise Cloud
SAP HANA in your own data center
•• You have already invested significantly in You may choose SAP HANA Infrastructure
hardware, storage, and IT infrastructure Services and run SAP HANA in a public cloud if you:
•• You want to be more flexible in choosing and •• Have your own SAP HANA licenses but want to
maintaining your hardware and infrastructure leverage cloud infrastructure for flexible
components scalability
•• Want to reduce your hardware footprint
You may choose a virtualization approach if you
want to make more efficient use of your existing You may choose the SAP HANA One service if you
hardware or be more flexible with regard to adap- pay for use to perform specific tasks that require
tation of new hardware requirements or both. one-time high-performance capabilities (for
example, monthly or year-end close).
You may choose the express edition of SAP HANA
if you: You may choose SAP Cloud Platform if you:
•• Want to develop data-driven applications based •• Want to quickly build, extend, and integrate
on SAP HANA on your own computer or in the applications in a complete, cloud-based
cloud development environment based on SAP HANA
•• Want to evaluate, prototype, or test-drive •• Want to use a hybrid approach in which on-
SAP HANA as a developer, partner, or student premise and cloud deployments are combined.
In such cases, specific requirements for data and
You may choose SAP HANA Enterprise Cloud process integration apply. The cloud integration
if you: service for SAP Cloud Platform supports these
•• Are a net-new SAP HANA customer who does tasks by providing process and data integration
not want to set up a new or extend an existing technology as a service to connect your cloud
data center and on-premise enterprise systems in real time
•• Lack qualified resources for operations and
maintenance of SAP HANA or don’t want to Now let’s look at all these deployment options in
invest in them more detail.
•• Want to lower software licensing costs or avoid
high up-front investments

SAP can help you develop a business case for


your SAP HANA journey and choose the right
deployment model that fits your needs.

5 / 17

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


APPLIANCES FOR SAP HANA on premise. While the deployment of an appli-
SAP technology partners deliver SAP HANA soft- ance is easy and comfortable for customers,
ware together with the corresponding validated appliances impose limitations on the flexibility of
hardware as a prepackaged solution to the cus- selecting the hardware components for servers,
tomer site. The exact bill of materials for hardware storage, and networks.
components, the operating system, additional
software components (such as a file system), and SAP HANA tailored data center integration reduces
the SAP HANA software itself are provided by the hardware and operations costs by reusing exist-
technology partners (see Figure 2). ing hardware components and IT operations pro-
cesses. It further mitigates risk and optimizes time
SAP HANA runs on SUSE Linux Enterprise Server to value by enabling existing IT management pro-
and Red Hat Enterprise Linux operating system– cesses for an SAP HANA implementation. Finally,
based platforms and on the IBM Power Systems with SAP HANA tailored data center integration,
hardware platform. For details and for choosing you gain more flexibility in hardware selection for
the right CPU versus memory ratio for your deploy- SAP HANA by using the existing SAP ecosystem
ment, please refer to the various SAP notes and and partners. SAP HANA tailored data center
technical guidelines available through the integration covers the following three hardware
SAP Support Portal service. components of an SAP HANA installation that
have potential for a more flexible and therefore
SAP HANA TAILORED DATA CENTER INTEGRATION more agile and cost-effective approach: server,
SAP HANA tailored data center integration offers enterprise storage, and enterprise network.
an additional approach of deploying SAP HANA

Figure 2: Hardware Partners Providing Appliances or Storage Certified for Use with SAP HANA

Appliance Tailored Data Center Integration


Processors Operating Systems

Storage Providers

6 / 17

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


SAP HANA in Enterprise Networks in a private, managed cloud environment. The
Most SAP HANA installations run in so-called enter- benefits include simplicity through rapid deploy-
prise networks to support backup and system ment, an integrated support model, and a compre-
replication requirements. SAP HANA tailored data hensive portfolio of innovative cloud solutions.
center integration defines the requirements for
the appropriate network devices and products. SAP HANA INFRASTRUCTURE SERVICES
However, SAP does not introduce any certifica- SAP HANA Infrastructure Services is a public cloud
tion of network components for SAP HANA tailored IaaS that enables customers to quickly deploy and
data center integration setups. Customers may manage their prelicensed instance of SAP HANA
consider involving SAP Digital Business Services without a hardware investment on AWS, Microsoft
to perform a go-live check for their SAP HANA Azure, Google Cloud Platform, and IBM Bluemix
installation prior to going live. Cloud. Configurations ranging from 128 GB to 3 TB
are available plus scale-out.
SAP HANA, EXPRESS EDITION
The express edition of SAP HANA can be installed SAP HANA ONE SERVICE AND PREMIUM SERVICE
on your laptop or desktop computer (Windows SAP HANA One is a public cloud pay-as-you-go
PC or Apple Macintosh), on Linux-based servers, offering with an affordable subscription fee for
or on a virtual machine (please note that there are getting started immediately with a 60 GB instance
specific requirements for virtual machines – read of SAP HANA One on AWS and Alibaba Cloud.
the “Decide on Multitenancy and Virtualization
Options” section for more details). Alternatively, SAP CLOUD PLATFORM
you can deploy it on various popular cloud plat- SAP Cloud Platform is an open and public PaaS
forms, using the SAP Cloud Appliance Library tool. offering that includes SAP HANA as a DBaaS,
Use the express edition to develop and deploy enabling developers to use advanced data stored
applications that use up to 32 GB of database in SAP HANA to build, extend, and integrate appli-
memory for free. If additional memory is required, cations without investing in separate infrastructure
you can purchase it from SAP Store. or tools. SAP Cloud Platform provides a variety
of innovative features and services to enrich your
SAP HANA ENTERPRISE CLOUD application with advanced analytics, the Internet
SAP HANA Enterprise Cloud is a fully scalable of Things, and security capabilities and to integrate
and secure private cloud offering available only your cloud and on-premise applications.
from SAP. It gives you the full power of SAP HANA

The express edition of SAP HANA can be installed


on your computer, on Linux-based servers, or on
a virtual machine.

7 / 17

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


Conduct Sizing of Your Hardware Components
Once you have selected your deployment model, For an initial sizing recommendation, you may
it’s time to define your IT infrastructure require- proceed as follows:
ments. SAP offers tools and procedures that help 1. See www.sap.com/about/benchmark/sizing.
to determine the required hardware for exactly quick-sizer.html#quick-sizer
meeting your volume and performance require- (login required).
ments (see Figure 3). What makes sizing chal- 2. Create a sizing project with the relevant
lenging is that, for in-memory databases, careful information, such as number of users.
planning and maintenance have a much higher 3. Get an initial sizing result for CPU, disk, and
impact on cost of ownership than with traditional memory.
relational database management systems. 4. Possibly apply additional guidelines on top.
5. Check for sample configurations at
The most important sizing driver is the memory, www.sap.com/benchmark.
while the second most important is the CPU. I/O 6. Provide your hardware vendor with the
sizing is also important but can only be performed Quick Sizer tool project name and information,
during the realization phase. Apart from that, there whether classic Quick Sizer or Quick Sizer for
is disk space required for persistence and log data, SAP software was used.
but this sizing is dependent on memory and thus
straightforward. There are detailed recommendations available
from SAP experts, which are described in the
guideline Sizing Approaches for SAP HANA
(login required).

Figure 3: Sizing Process for Hardware Running SAP HANA

Customer

Requirements
• Performance
• Business service-level agreements
• Business figures

Sizing recommendation
CPU (SAP® Application
Performance Standard) Final sizing
Hardware vendor
Memory (GB)
Disk space (GB) Technology partner responsible
• Scalable hardware offering
Component performance
• Practical sizing experience
• Different configurations
• Different technology partners

SAP

• Sizing tools and reports


• Sizing guidelines
• Sizing verification

8 / 17

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


Define Your Hardware Requirements
To determine your hardware requirements, exam, needs to be passed successfully to perform
SAP offers a hardware configuration check tool for SAP HANA installations at customer sites. You can
SAP HANA – a command-line tool used by storage prepare for this exam with SAP training course
vendors, SAP Support Portal, and customers. The “SAP HANA Installation & Operations” (HA200).
tool measures the data throughput and latency Furthermore, individual support agreements with
times between the SAP HANA servers and the enter- your hardware partners are required.
prise storage system. It does not require SAP HANA
software being installed beforehand and uses the CERTIFIED SAP HANA HARDWARE DIRECTORY
same libraries for file system access and the same The Certified and Supported SAP HANA Hardware
I/O patterns as SAP HANA does. Please note that, Directory (see Figure 4) provides the latest and most
by using the hardware configuration check tool, detailed information about the validated hardware
you can run a self-assessment; however, there is platforms for SAP HANA software as well as for all
no self-certification. Certifications for hardware com- enterprise storage offerings certified for use in IT
ponents running SAP HANA software can only be landscapes running SAP HANA and using SAP HANA
done by the SAP Integration and Certification Center. tailored data center integration. All servers offered
through appliances, including entry-level systems
Please also note that the exam required for the running Intel’s Xeon E5 v2/v3 CPUs and IBM Power
deployed support package stack for SAP HANA, Systems, are supported, as well as all storage con-
for example, “SAP Certified Technology Associate figurations listed here.
– SAP HANA (Edition 2016),” or an appropriate delta

Figure 4: Certified and Supported SAP HANA Hardware Directory

9 / 17

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


Define Your Cluster Strategy
(Scale-Up or Scale-Out)
A typical single-server deployment of SAP HANA the same physical server by applying the multi­
can vary from a 2 CPU configuration with 128 GB tenancy and virtualization options SAP HANA
of RAM as an entry-level system (see the Certified has to offer (see the “Decide on Multitenancy and
and Supported SAP HANA Hardware Directory Virtualization Options” section).
for a complete list of all available entry-level con-
figurations provided by SAP technology partners) If your data volume exceeds the volume applica-
to a high-end 8 CPU configuration with 8 TB of RAM ble for single-server deployments, as detailed
(see Figure 5). Special layouts for SAP S/4HANA® earlier, a scale-out configuration is the configu-
support up to 20 TB per host and more. The largest ration of choice. A typical scale-out cluster con-
single-server architecture for SAP HANA today sists of 2 to n servers per cluster, where in theory
runs at PayPal with 48 TB of RAM. there is no limit for n. The largest certified configu-
ration is 112 servers, while the largest tested
In a classical three-tier system architecture, with configuration has more than 250 servers. Each
development, quality assurance (QA), and pro- server configuration is either 4 CPU/2 TB or
ductive systems, you can apply lower hardware 8 CPU/4 TB. Both architectures, scale-up and
requirements for your development and QA sys- scale-out, provide full support for high availability
tems and consolidate your server landscape by and disaster recovery (see the “Define a High-
running your development and QA instance on Availability and Disaster-Recovery Strategy and
System Replication Requirements” section).

Figure 5: Overview of Scale-Up, Scale-Out, and Cloud Deployment Models

Single Server Scale-Out Cluster Cloud Deployment


• 2 CPU/128 GB to 8 CPU/8 TB (special • 2 to n servers per cluster • SAP HANA instances can be deployed
layout for SAP® Business Suite on • Each server either 4 CPU/2 TB or to Amazon Web Services, Huawei, and
SAP HANA® or SAP S/4HANA® with 8 CPU/4 TB so on
up to 20 TB per host) • Largest certified configuration: • Limited to developer license
• Single deployments of SAP HANA for 112 servers • SAP HANA Enterprise Cloud
data marts or accelerators with perfor- • Largest tested configuration: • SAP Cloud Platform
mance demands (socket-to-memory 250+ servers • Integration option in on-premise
ratio) • Support for high availability and operation (infrastructure as a service)
• Support for high availability and disaster recovery – for example, disaster recovery
disaster recovery

10 / 17

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


UNDERSTAND THE BENEFITS OF SCALE-UP BEFORE YOU
DECIDE TO SCALE OUT
A scale-out, multinode approach requires you to deploy
multiple server boxes in your data center, which results in
higher requirements for space and power. Further opera-
tional costs for cluster systems are higher than those for
single-node systems. Although scale-out provides more
hardware flexibility and requires less hardware costs initially,
it requires more up-front knowledge about data, application,
and hardware than scale-up.

In summary, it is good practice to always scale up first and


consider scale-out only if this is inevitable. Most customers
find that the high data compression rate of SAP HANA com-
bined with its high scalability (up to 2 TB – online analytical
processing – and up to 12 TB – online transaction processing)
will easily meet their business requirements. Its scalability
constantly grows, spurred on by advances in multicore tech-
nologies, providing new ways to meet the most demanding
scalability requirements of our largest customers.

Single-node SAP HANA deployments are recommended for


data marts or accelerators with performance demands. For
the impact of high-end CPU and memory components on
the performance and energy consumption of servers run-
ning SAP HANA, please refer to the brochure Boosting the
Performance of SAP S/4HANA and Analytical Banking
Applications on SAP HANA.

It is good practice to
always scale up first
and consider scale-out
only if this is inevitable.

11 / 17

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


Decide on Multitenancy and Virtualization
Options
SAP HANA provides a variety of features that can configurations, for single and multiple virtual
help make your deployment even more effective, machines, in single- or multinode configurations,
high performing, and cost-efficient, depending on for appliances of SAP HANA and SAP HANA
the deployment model you chose. tailored data center integration delivery methods
(see Figure 6).
VIRTUALIZATION
SAP HANA supports many popular virtualization VMware vSphere 6.x supports scale-out and
supervisors, such as VMware vSphere 5.1 or newer, auto-failover configurations and a theoretical
Hitachi LPAR, Huawei FusionSphere, IBM PowerVM, maximum virtual-machine size and configuration
or others for nonproductive environments. You of 128 vCPUs and 4 TB of vRAM. For detailed
can choose virtualization for a wide variety of sizing recommendations, please refer to
www.sap.com/sizing.

Figure 6: Virtualization Scenarios for Deployment of SAP HANA

SAP SAP
ABAP HANA 4 HANA 3

SAP SAP SAP SAP SAP


SAP HANA 1
SAP HANA® HANA ABAP® HANA 1 HANA 2 HANA 3 HANA 2

SLES RHEL Win* RHEL SLES SLES SLES SLES SLES RHEL
VM1 VM1 VM2 VM1 VM2 VM3 VM1 VM2 VM3 VM4
ESXi/LPAR ESXi/LPAR ESXi/LPAR ESXi/LPAR ESXi/LPAR ESXi/LPAR
host host host phost phost phost

Single VM Single VM + Other Multiple VMs MCOS Scale-Out MCOS

General support for a General support for a General support for General support General support General support for
single instance of SAP single instance of SAP multiple instances of for a single or for a scale-out multiple SAP HANA
HANA running on a HANA running on a SAP HANA running on multiple instances configuration of database installations
virtual machine on a virtual machine on a a virtual machine on a of SAP HANA SAP HANA in a on one system or OS
dedicated, certified dedicated, certified dedicated, certified run­ning on a virtualized environ- in production
server for SAP HANA server for SAP HANA server for SAP HANA virtual machine ment, either
in production in production (without in production in combination production or
overprovisioning and with MCOS for nonproduction
with resource priority production
configured over other
virtual machines)
SAP Note 1995460 SAP Note 2024433** SAP Note 1681092
SAP Note 2063057** SAP Note 2063057**

*Windows guest OS is currently not supported with Hitachi LPAR for SAP® software workloads.
**Access to the SAP Notes tool is restricted to participants of controlled availability.
LPAR = Hitachi Compute Blade logical partitioning
MCOS = Multiple components, one system
RHEL = Red Hat Enterprise Linux
SLES = SUSE Linux Enterprise Server
VM = Virtual machine

12 / 17

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


Recommendations on Virtualizing SAP HANA other criteria, there are best practices in which
Deployments virtualizing a deployment of SAP HANA is recom-
Depending on performance requirements, num- mended and in which it is not. See Figure 7 for an
ber of users, and technical parameters, among overview.

Figure 7: Use Cases for SAP HANA Virtualization

-
Virtualization not recommended Virtualization possible

+
Performance Financial Performance Financial
Performance critical Virtual machines Nonperformance critical Virtual machines
> 512 GB of RAM* ≤ 512 GB of RAM

Users Technical Users Technical


> ~500 named users > 64 virtual CPUs* 1:1 (server : user) ≤ 64 virtual CPUs*
(SAP® Business Suite) > 1 TB of memory* < ~500 named users ≤ 1 TB of memory*
(SAP Business Suite)

Use Cases Use Cases


• Mission-critical or high-performance scenarios • Sandbox, trial systems, development, and test systems
• Absolute performance testing (end-to-end elapse time) • Relative performance tests (old versus new version on virtual
• Scale-out or host auto-failover of SAP HANA® software (Vsphere 6.x) machine)
• Central SAP software system (SAP Business Suite) • High-availability, disaster-recovery, tolerant system setup

*Relates to VMware vSphere 5.5 release

Multitenant database containers can help you lower TCO.

13 / 17

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


SAP HANA AND SAP NETWEAVER® APPLICATION MULTITENANT DATABASE CONTAINERS
SERVER DEPLOYED ON ONE SERVER Multitenant database containers (MDCs) are
For all productive and nonproductive single-node another virtualization option for SAP HANA deploy-
installations, SAP HANA and the SAP NetWeaver® ments. With MDCs, you can run multiple, strictly
Application Server component for Java or SAP separated database tenants on one SAP HANA
NetWeaver Application Server component for system. The features are:
ABAP® 7.4 or newer can be deployed on one server. •• Data center operations automation by running
However, this multicomponent and resource- multiple tenant databases in one SAP HANA
optimized deployment approach is not recom- system and managing them as one
mended, as it limits flexibility. Figure 8 illustrates •• Tenant-specific lifecycle management, including
the pros and cons of deploying SAP HANA and backup and restore options
the SAP NetWeaver technology platform on the •• A clear separation of application data and user
same server. management
•• Local user management within each tenant
MCOD AND MCOS database
The multiple components, one database (MCOD) •• Session and transaction management per
and multiple components, one system (MCOS) tenant database
options give you the flexibility to scale your archi- •• The option to move or copy tenant databases
tecture and the included components optimally to other systems or hosts
per your needs. While MCOD allows the joint
usage of data pools across schemas and schema- The benefits of MDCs are a lower TCO because of
overarching SQL statements, the advantage of a single software stack, central configuration, and
MCOS lies in the option to run various software administration at the database level; direct data-
versions of SAP HANA in the same environment. base resource management; optimized federation;
and performance advantages because there is no
virtualization overhead. MDC licenses are included
in an SAP HANA license.

Figure 8: Pros and Cons of Deploying SAP HANA and SAP NetWeaver on the Same Server

The SAP HANA® business data platform and the SAP NetWeaver® Application Server (SAP NetWeaver AS) component for ABAP® deployed on
one server is a multicomponent, multiresource, and cost-optimized deployment approach.

SAP HANA business data platform SAP NetWeaver AS for ABAP SAP HANA business data platform

SAP HANA software system System for SAP NetWeaver AS


System for SAP NetWeaver AS
for ABAP
for ABAP

SAP HANA software system

Separated deployment approach SAP HANA and SAP NetWeaver AS deployed


on one server

+ Hardware resources isolated + Cost-optimized approach


– Separate hardware – Shared memory and CPU resources

14 / 17

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


Define a High-Availability and Disaster-Recovery
Strategy and System Replication Requirements
High availability is a set of techniques, engineer- •• System replication – SAP HANA replicates
ing practices, and design principles for business all data to another location within one or
continuity. SAP HANA offers different kinds of between several data centers. The technology
high-availability mechanisms, supporting a broad is independent from hardware vendor concepts
range of scenarios for recovery from various faults and reusable with a changing infrastructure.
– from simple software errors through system and
hardware crashes up to disasters that decommission Depending on your data center operations,
a whole data center. hardware configuration, and software landscape,
you can select between several options for
The following four basic high-availability solutions high-availability scenarios for your SAP HANA
are available: environment.
•• Backup and recovery – Regular shipping
of data backups to a remote location over a SAP works closely with hardware partners to
network or by couriers can be a simple and provide customers a flexible choice between
relatively inexpensive way to prepare for a different but best-suited hardware and software
disaster. solutions for high-availability and disaster-
•• Host auto-failover – This covers hardware recovery scenarios. Current capabilities include,
crashes for scale-out setups. One or more for example, single-node failover with multiple
standby hosts are added to an SAP HANA standby servers within one cluster configuration
system, usually within the same data center, and storage-based mirroring of SAP HANA
and are configured to work in standby mode. system replication across data centers.
The standby host has no access to data and
does not accept requests and queries. For a detailed description of all high-availability
•• Storage replication – The storage itself and disaster-recovery offerings available for
replicates all data to another location within SAP HANA, please refer to the brochure Protect
one or between several data centers. The Enterprise Readiness with the High Availability
technology is vendor-specific hardware, and Features of SAP HANA.
multiple concepts are available in the market.

SAP works closely with hardware partners to


provide customers a flexible choice between
different software solutions for high-availability
and disaster-recovery scenarios.

15 / 17

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


Change Management
EVALUATE UPDATE OPTIONS transaction management between ABAP and the
There are various options for updates. SAP HANA database. This keeps transaction pro-
cessing on the ABAP layer alive and allows you to
Zero-Downtime Maintenance change components (software versions) on the
Uptime is the most critical factor that influences layers below on the secondary (shadow) instance
the TCO of an IT organization. Therefore, system of SAP HANA.
administrators are always looking to reduce
downtime, be it incidentally by errors or crashes Capture and Replay
or planned for maintenance reasons. When run- To safeguard business continuity, thorough test­
ning the system replication configuration for ing is required prior to applying changes in your
SAP HANA, zero-downtime maintenance allows hardware or software configuration – be it new
you to make software updates or hardware hardware, software updates, changes in configu­
exchanges with minimum downtime. This feature ration, table distribution, disk partitioning, or
is based on the “connectivity suspend” feature indexing. With the capture and replay tool for
of SAP NetWeaver Application Server for ABAP. SAP HANA (see Figure 9), you can predict perfor-
For other environments, a near-zero-downtime mance and the cost impact of updates to comply
option is available. with service-level agreements and budget con-
straints. Plus, you can perform stability and per-
When applying zero-downtime maintenance, the formance checks to find root causes of system
shared library of the database interface decouples irregularities during normal operations.

Figure 9: Capture and Replay Tool for SAP HANA

One integrated tool set and simulations based on real workloads

2
Clients Preprocess workload

3
Replay workload

Application servers
4
SAP HANA cockpit Analyze results
1
Capture
workload
SAP HANA®
SAP HANA revision YYY
revision XXX

Production system Test system

16 / 17

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


The tool captures real system workloads and SAP HANA Cockpit
replays them in a separate testing environment The SAP HANA cockpit is a tool built with SAP Fiori
rather than generating test data, so simulations technology. It is your single point of access for
are more accurate. Also, the tool fully integrates various native administration tasks for SAP HANA.
with SAP HANA and has an intuitive user inter- The cockpit provides a role-based concept that
face based on the SAP Fiori® user experience enables you to have a personalized view of the tiles
to make managing and monitoring capture and and applications for each system administrator.
replay processes easier.
SAP Landscape Management
And if you can’t afford or don’t want to pay for a SAP Landscape Management software offers
separate testing environment for running your operations and automation features specifically
replay, a hybrid cloud service for SAP HANA can for SAP HANA. For instance, provisioning and
do this for you in a private cloud provided and management of MDCs is simplified. The setup
managed by SAP. for system replication – in particular, the proce-
dure for takeover and failback – and the system
For details, please refer to the brochure Upgrade refresh procedure using backup and restore are
Your SAP HANA Platform with Capture and fully automated. SAP Landscape Management
Replay Performance Management. further provides a near-zero-downtime mainte-
nance option for SAP HANA.

To find out more about how you can achieve a


successful SAP HANA deployment, please get
in touch with your SAP representative or contact
SAP here.

The capture and replay tool for SAP HANA lets you predict
performance and the cost impact of compliance updates.
It also lets you perform stability and performance checks.

17 / 17

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


Follow us

www.sap.com/contactsap

47913enUS (18/04)

© 2018 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.

In particular, SAP SE or its affiliated companies have no obligation to


pursue any course of business outlined in this document or any related
presentation, or to develop or release any functionality mentioned therein.
This document, or any related presentation, and SAP SE’s or its affiliated
companies’ strategy and possible future developments, products, and/or
platforms, directions, and functionality are all subject to change and
may be changed by SAP SE or its affiliated companies at any time for
any reason without notice. The information in this document is not a
commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks
and uncertainties that could cause actual results to differ materially from
expectations. Readers are cautioned not to place undue reliance on these
forward-looking statements, and they should not be relied upon in making
purchasing decisions.

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.

See www.sap.com/corporate-en/legal/copyright/index.epx for additional


trademark information and notices.