SAP HANA
Landscape Denition Guide for SAP HANA® – Best Practices for a Successful Deployment . d e v r e s e r s t h g i r l l A . y n a p m o c e t a i l f a P A S n a r o E S P A S 7 1 0 2 ©
1 / 17
Table of Contents
4
Available Deployment Models
8
Conduct Sizing of Your Hardware Components
9
Dene Your Hardware Requirements
10
Dene Your Cluster Strategy Strategy (Scale-Up or Scale-Out)
12
Decide on Multitenancy Multitenan cy and Virtualization Options
15
Dene a High-Availability High-Availability and Disaster-Recovery Disaster-Recovery Strategy and System Replication Requirements
16
Change Management
2 / 17
© 2017 SAP SE or an SAP aliate 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 ecient IT landscape . The following approach covers some best practices that may help you dene the most suitable IT landscape for your deployment with regard to performance, scalability, adaptability, administration eort, and cost-eectiveness.
SYSTEM LANDSCAPE AND PROJECT PLANNING A system landscape and project planning proce dure for an SAP HANA deployment typically covers the following steps (see Figure 1): 1. Dene the deployment options either options either in the data center (on premise) or in the cloud, per your business needs. 2. Dene the general technical architecture – that is, the components required and the sizing for all components. Map the sizing results to your hardware. 3. Dene the hardware acquisition requirements depending on your deployment model. 4. Dene your cluster strategy (scale-in and scale-out) and number of systems. 5. Deploy dierent components and virtualization virtualization options optio ns for for setting up each system. 6. Dene a strategy for high availability and disaster recovery. 7. Dene a software change management landscape and evaluate evaluate update options. update options.
Figure 1: System Landscape and Project Planning Procedure for an SAP HANA Deployment Deployment model
On premise
Cloud
New hardware?
Private, managed cloud
Public cloud
No Yes Tailored data-center integration
Appliance
Sizing Data volume management and cluster strategy Technical deployment plan
Disaster-recovery and high-availability strategy
Virtualization, multiple components, one database and multiple components, one system, multitenancy Software Softwar e change management landscape
3 / 17
© 2017 SAP SE or an SAP aliate company. All rights reserved.
Available Deployment Models SAP HANA can be deployed in dierent ways. Here is an overview of all available options oered by SAP today. Each of them will be explained and mapped to applicable business scenarios. Options for SAP HANA in your data center (on premise) include: • Appliance – Bare-metal single server or scale-out (see the “Dene Your Cluster Strategy (Scale-Up or Scale-Out)” section) as a precongured validated stack, delivered together with the corresponding hardware hardware • SAP HANA tailored data center integration – Uses the existing hardware and operations in your data center • Virtualized – Hosts multiple, isolated database instances on one or more servers so that each database instance appears as if it is running on a separate machine • SAP HANA, Edge edition, advanced version – Special package dedicated to subject-matter experts, delivered by SAP partners as an appliance or deployed using SAP HANA tailored data center integration Options for SAP HANA in the cloud include: • SAP HANA Enterprise Enterprise Cloud – Private cloud service managed by SAP • SAP HANA Infrastructure Services technology – Public cloud infrastructure as a service (IaaS) that oers 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) oering, with SAP HANA database as a service (DBaaS) and advanced analytical data-processing services
Options for SAP HANA as a development platform include SAP HANA, express edition, which is a plat form to develop data-driven applications appli cations based on SAP HANA, available for download from the SAP developer center free of charge. This version of SAP HANA can be installed on laptop or desktop computers, computers, Linux-based servers, virtual machines, or a private cloud (see the “Which Deployment Deployment Model for Which Business Scenario?” section for more details). Our implementation support team is happy to assist you in developing a business case for your SAP HANA journey and choosing the right deploy ment model that ts your needs exactly. WHICH DEPLOYMENT MODEL FOR WHICH BUSINESS SCENARIO? The following maps the various deployment models for SAP HANA to the most typical business scenarios.
You may choose the appliance oering if you: • Need to comply with industry-specic security, privacy, or control requirements (for example, in banking) • Are looking for the fastest-possible implementation on premise • Are looking for an all-inclusive prepackaged oering ready to run in your data center
4 / 17
You may choose SAP HANA tailored data center integration if: integration if: • Your business model requires running SAP HANA in your own data center • You have already invested signicantly in hardware, storage, and IT infrastructure • You want to be more exible in choosing and maintaining your hardware and infrastructure infrastructure components
• Want to extend your on-premise landscape with innovative applications delivered through SAP HANA Enterprise Cloud You may choose SAP HANA Infrastructure Services and Services and run SAP HANA in a public cloud if you: • Have your own SAP HANA licenses but want to leverage cloud infrastructure for exible scalability • Want to reduce your hardware footprint
You may choose a virtualization approach virtualization approach if you want to make more ecient use of your existing You may choose the SAP HANA One service if you hardware or be more exible with regard to adap - pay for use to perform specic tasks that require one-time high-performance capabilities (for tation of new hardware hardware requirements or both. example, monthly or year-end close). You may choose the express edition of SAP HANA You may choose SAP Cloud Platform if you: if you: • Want to develop data-driven applications based • Want to quickly build, extend, and integrate applications in a complete, cloud-based cloud-based on SAP HANA on your own computer or in the cloud development environment environment based on SAP HANA • Want to evaluate, prototype, or test-drive • Want to use a hybrid approach in which onpremise and cloud deployments deployments are combined. SAP HANA as a developer, partner, or student In such cases, specic requirements for data and process integration apply. The cloud integration You may choose SAP HANA Enterprise Cloud service for SAP Cloud Platform supports these if you: tasks by providing process and data integration • Are a net-new SAP HANA customer who does technology as a service to connect your cloud not want to set up a new or o r extend an existing data center and on-premise enterprise systems in real time • Lack qualied resources resources for operations and Now let’s look at all these deployment options in maintenance of SAP HANA or don’t want to 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 ts your needs.
5 / 17
© 2017 SAP SE or an SAP aliate company. All rights reserved.
APPLIANCES FOR SAP HANA SAP technology partners deliver SAP HANA soft ware together with the corresponding validated hardware as a prepackaged solution to the cus tomer site. The exact bill of materials for hardware components, the operating system, additional software software components (such as a le system), and the SAP HANA software itself are provided by the technology partners (see Figure 2).
SAP HANA runs on SUSE Linux Enterprise Server and Red Hat Enterprise Linux operating system– based platforms and on the IBM Power Systems hardware platform. For details and for choosing the right CPU versus memory ratio for your deployment, please refer to the various SAP notes and technical guidelines available through the SAP Support Portal service. SAP HANA H ANA TAILORED DATA DATA CENTER CENT ER INTEGRATION SAP HANA tailored data center integration oers an additional approach of deploying SAP HANA
on premise. While the deployment of an appli ance is easy and comfortable for customers, appliances impose limitations on the exibility of selecting the hardware hardware components for servers, storage, and networks. SAP HANA tailored data center integration reduces hardware and operations costs by reusing exist ing hardware components and IT operations processes. It further mitigates risk and optimizes time to value by enabling existing IT management pro cesses for an SAP HANA implementation. Finally, with SAP HANA tailored data center integration, you gain more exibility in hardware selection for SAP HANA by using the existing SAP ecosystem and partners. SAP HANA tailored data center integration covers the following three hardware components of an SAP HANA installation that have potential for a more exible and therefore more agile and cost-eective approach: server, enterprise storage, and enterprise network.
Figure 2: Hardware Partners Providing Appliances or Storage Certied for Use with SAP HANA Appliance
Tailored Data Center Integration Processors
Operating Systems
Storage Providers
6 / 17
© 2017 SAP SE or an SAP aliate company. All rights reserved.
SAP HANA in Enterprise Networks Most SAP HANA installations run in so-called enterprise networks to support backup and system replication requirements. SAP HANA tailored data center integration denes the requirements requirements for the appropriate network devices and products. However, SAP does not introduce any certica tion of network components for SAP HANA tailored data center integration setups. Customers may consider involving SAP Digital Business Services to perform a go-live check for their SAP HANA installation prior to going live. SAP HANA, EXPRESS EDITION The express edition of SAP HANA can be installed on your laptop or desktop computer (Windows PC or Apple Macintosh), on Linux-based servers, or on a virtual machine (please note that there are specic requirements for virtual machines – read the “Decide on Multitenancy and Virtualization Options” section for more details). Alternatively, you can deploy it on various popular cloud plat forms, using the SAP Cloud Appliance Library tool. Use the express edition to develop and deploy applications that use up to 32 GB of database memory for free. If additional memory is required, you can purchase it from SAP Store. SAP HANA ENTERPRISE CLOUD SAP HANA Enterprise Cloud is a fully scalable and secure private cloud oering available only from SAP. SAP. It gives you the full power of SAP HANA
in a private, managed cloud environment. The benets include simplicity through rapid deployment, an integrated support model, and a compre hensive portfolio of innovative innovative cloud solutions. SAP HANA INFRASTRUCTURE SERVICES SAP HANA Infrastructure Infrastructure Services is a public cloud IaaS that enables customers to quickly deploy and manage their prelicensed instance of SAP HANA without a hardware investment on AWS, Microsoft Azure, Google Cloud Platform, and IBM Bluemix Cloud. Congurations ranging from 128 GB to 3 TB are available plus scale-out. SAP HANA ONE SERVICE AND PREMIUM SERVICE SAP HANA One is a public cloud pay-as-you-go pay-as-you-go oering with an aordable subscription fee for getting started immediately with a 60 GB instance of SAP HANA One on AWS and Alibaba Cloud. SAP CLOUD PLATFORM SAP Cloud Platform is an open and public PaaS oering that includes SAP HANA as a DBaaS, enabling developers to use advanced data stored in SAP HANA to build, extend, and integrate appli cations without investing investing in separate separate infrastructure or tools. SAP Cloud Platform provides a variety of innovative features and services to enrich your application with advanced analytics, the Internet of Things, and security capabilities and to integrate i ntegrate your cloud and on-premise applications.
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 aliate company. All rights reserved.
Conduct Sizing of Your Your Hardware Components Components Once you have selected your deployment model, it’s time to dene your IT infrastructure require ments. SAP oers tools and procedures that help to determine the required hardware for exactly meeting your volume and performance require require ments (see Figure 3). What makes sizing chal lenging is that, for in-memory databases, databases, careful planning and maintenance have a much higher impact on cost of ownership than with traditional relational database management systems. The most important sizing driver is the memory, while the second most important is the CPU. I/O sizing is also important but can only be performed during the realization phase. Apart from that, there is disk space required for persistence and log data, but this sizing is dependent on memory and thus straightforward.
For an initial sizing recommendation, you may proceed as follows: 1. See www.sap.com/about/benchmark/sizing. quick-sizer.html#quick-sizer (login required). required). 2. Create a sizing project with the relevant information, such as number of users. 3. Get an initial sizing result for CPU, disk, and memory. 4. Possibly Possibly apply additional guidelines on top. 5. Check for sample congurations at www.sap.com/benchmark . 6. Provide your hardware vendor with the Quick Sizer tool project name and information, whether classic Quick Sizer or Quick Sizer for SAP software was used. There are detailed recommendations available from SAP experts, which are described in the guideline Sizing Approaches for SAP HANA (login required). required).
Figure 3: Sizing Process Process for Hardware Running SAP HANA
Customer Requirements Performance • Business service-level agreements • Business gures •
Hardware vendor • • • •
Scalable hardware oering Practical sizing experience Dierent congurations Dierent technology partners
Sizing recommendation CPU (SAP® Application Performance Standard) Memory (GB) Disk space (GB) Component performance
Final sizing Technology partner responsible
SAP • • •
Sizing tools and reports Sizing guidelines Sizing verication
8 / 17
© 2017 SAP SE or an SAP aliate company. All rights reserved.
Dene Your Hardware Requirements To determine your hardware requirements, SAP oers a hardware conguration check tool for SAP HANA – a command-line tool used by storage vendors, SAP Support Portal, and customers. The tool measures the data throughput and latency times between the SAP HANA servers and the enter prise storage system. It does not require SAP HANA software software being installed beforehand and uses the same libraries for le system access and the same I/O patterns as SAP HANA does. Please note that, by using the hardware conguration check tool, you can run a self-assessment; however, there is no self-certication. Certications for hardware components running SAP HANA software can only be done by the SAP Integration and Certication Center. Please also note that the exam required for the deployed support package stack for SAP HANA, HANA, for example, “SAP Certied Technology Associate – SAP HANA (Edition 2016),” or an appropriate delta
exam, needs to be passed successfully to perform SAP HANA installations at customer sites. You You can prepare for this exam with SAP training course “SAP HANA Installation & Operations” (HA200 ( HA200). ). Furthermore, Furthermore, individual support agreements with your hardware partners are required. CERTIFIED SAP HANA HARDWARE DIRECTORY The Certied and Supported SAP HANA Hardware Directory (see Directory (see Figure 4) provides the latest and most detailed information about the validated hardware platforms for SAP HANA software as well as for all enterprise storage oerings certied for use in IT landscapes running SAP HANA and using SAP HANA tailored data center integration. All servers oered through appliances, including entry-level systems running run ning Intel’s Intel’s Xeon E5 v2/v3 v2/v3 CPUs and IBM Power Systems,, are supported, as well as all storage conSystems gurations listed here.
Figure 4: Certied and an d Supported SAP HANA Hardware Directory
9 / 17
© 2017 SAP SE or an SAP aliate company. All rights reserved.
Dene Your Cluster Strategy (Scale-Up or Scale-Out) A typical single-server deployment of SAP HANA can vary from a 2 CPU conguration with 128 GB of RAM as an entry-level system (see the Certied and Supported SAP HANA Hardware Hardware Directory for a complete list of all available entry-level congurations provided by SAP technology partners) to a high-end 8 CPU conguration with 8 TB of RAM (see Figure 5). Special layouts for SAP S/4HANA® support up to 20 TB per host and more. The largest single-server architecture for SAP HANA today runs at PayPal PayPal with with 48 TB of RAM. In a classical three-tier system architecture, with development, quality assurance (QA), and pro ductive systems, you can apply lower hardware requirements for your development and QA sys tems and consolidate your server landscape by running your development and QA instance on
the same physical server by applying the multitenancy and virtualization options SAP HANA has to oer (see the “Decide “Decide on Multitenancy and Virtualization Options” section). If your data volume exceeds the volume applica ble for single-server deployments, deployments, as detailed earlier, a scale-out conguration is the conguration of choice. A typical scale-out cluster consists of 2 to n servers per cluster, where where in theory there is no limit for n. The largest certied conguration is 112 servers, while the largest tested conguration has more than 250 servers. Each server conguration is either 4 CPU/2 TB or 8 CPU/4 TB. Both architectures, scale-up and scale-out, provide full support for high availability and disaster recovery (see the “Dene a HighAvailability and Disaster-Recovery Strategy and System Replication Requirements” section).
Figure 5: Overview of Scale-Up, Scale-Out, and Cloud Deployment Models
Single Server •
•
•
2 CPU/128 GB to 8 CPU/8 TB (special layout for SAP® Business Suite on SAP HANA® or SAP S/4HANA® with up to 20 TB per host) Single deployments of SAP HANA for data marts or accelerators with performance demands (socket-to-memory (socket-to-memory ratio) Support for high availability and disaster recovery
Scale-Out Cluster • • • • •
2 to n servers per cluster Each server either 4 CPU/2 TB or 8 CPU/4 TB Largest certied conguration: 112 servers Largest tested conguration: 250+ servers Support for high availability and disaster recovery
Cloud Deployment SAP HANA instances can be deployed to Amazon Web Services, Huawei, and so on • Limited to developer license • SAP HANA Enterprise Cloud • SAP Cloud Platform • Integration option in on-premise operation (infrastructure as a service) – for example, disaster recovery •
10 / 17
© 2017 SAP SE or an SAP aliate 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 exibility 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 rst and consider scale-out only if this is inevitable. Most customers nd 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. requirements. Its scalability scalabi lity constantly grows, spurred on by advances in multicore technologies, 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 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. HANA.
It is good practice to always scale up rst and consider scale-out only if this is inevitable.
11 / 17
© 2017 SAP SE or an SAP aliate company. All rights reserved.
Decide on Multitenancy and Virtualization Options SAP HANA provides a variety of features that can help make your deployment even more eective, high performing, and cost-ecient, depending on the deployment model you chose. VIRTUALIZATION SAP HANA supports many popular virtualization supervisors, such as VMware vSphere 5.1 or newer, newer, Hitachi LPAR, Huawei FusionSphere, IBM PowerVM, or others for nonproductive environments. You can choose virtualization for a wide variety of
congurations, for single and multiple virtual machines, in single- or multinode congurations, for appliances of SAP HANA and SAP HANA tailored data center integration delivery methods (see Figure 6). VMware vSphere 6.x supports scale-out and auto-failover auto-failover congurations and a theoretical maximum virtual-machine size and conguration of 128 vCPUs and 4 TB of vRAM. For detailed sizing recommendations, please refer to www.sap.com/sizing.
Figure 6: Virtualization Scenarios for Deployment of SAP HANA
ABAP
SAP
SAP
HANA 4
HANA 3
SAP
SAP
SAP
SAP HANA®
HANA
ABAP®
HANA 1
HANA 2
HANA 3
SLES
RHEL
Win*
RHEL
SLES
SLES
SAP
VM1
VM1
VM2
VM1
VM2
SAP
SAP HANA 1 SLES
VM3
SLES
VM1
VM2
HANA 2 SLES
RHEL
VM3
ESXi/LPAR
ESXi/LPAR
ESXi/LPAR
ESXi/LPAR
ESXi/LPAR
ESXi/LPAR
host
host
host
phost
phost
phost
Single VM
Single VM + Other
General support for support for a single instance of SAP HANA running on a virtual machine on a dedicated, certied server for SAP HANA in production
General support for support for a General support for support for single instance of SAP multiple instances of HANA running on a SAP HANA running on virtual machine on a a virtual machine on a dedicated, certied dedicated, dedicated, certied server for SAP HANA server for SAP HANA in production (without production (without in production overprovisioning and with resource priority congured over other virtual machines)
SAP Note 1995460 SAP Note 2063057**
Multiple VMs
SAP Note 2024433** SAP Note 2063057**
MCOS
Scale-Out
General support for a single or multiple instances of SAP HANA running running on a virtual machine in combination with MCOS for production
General support for a scale-out conguration of SAP HANA in a virtualized environment, either production or nonproduction
VM4
MCOS
General support for multiple SAP HANA database installations on one system or OS in production
SAP Note 1681092
*Windows guest OS is currently not supported with Hitachi LPAR for SAP® software workloads. workloads. **Access **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 aliate company. All rights reserved.
other criteria, there are best practices in which virtualizing a deployment of SAP HANA is recommended and in which it is not. See Figure 7 for an overview.
Recommendations on Virtualizing SAP HANA Deployments Depending on performance requirements, num ber of users, and technical parameters, among
Figure 7: Use Cases for SAP HANA Virtualization Virtualization not recommended
Virtualization possible
-
+
Performance Performance critical
Financial Virtual machines > 512 GB of RAM*
Performance Nonperformance Nonperformance critical
Financial Virtual machines ≤ 512 GB of RAM
Users > ~500 named users (SAP® Business Suite)
Technical > 64 virtual CPUs* > 1 TB of memory*
Users 1:1 (server : user) < ~500 named users (SAP Business Suite)
Technical ≤ 64 virtual CPUs* ≤ 1 TB of memory*
Use Cases Mission-critical Mission-critical or high-performance high-performance scenarios • Absolute performance testing (end-to-end elapse time) • Scale-out or host auto-failover of SAP HANA® software (Vsphere 6.x) • Central SAP software system (SAP Business Suite)
Use Cases Sandbox, trial systems, development, and test systems • Relative performance tests (old versus new version on virtual machine) • 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 aliate company. All rights reserved.
SAP HANA AND SAP NETWEAVER® APPLICATION APPLICATION SERVER DEPLOYED ON ONE SERVER For all productive and nonproductive single-node installations, SAP HANA and the SAP NetWeaver® Application Server component for Java or SAP NetWeaver NetWeaver Application Server component for ABAP® 7.4 or newer can be deployed on one server. However, this multicomponent and resourceoptimized deployment approach is not recommended, as it limits exibility. Figure 8 illustrates the pros and cons of deploying SAP HANA and the SAP NetWeaver technology platform on the same server. se rver. MCOD AND MCOS The multiple components, one database (MCOD) and multiple components, one system (MCOS) options give you the exibility to scale your archi tecture and the included components optimally per your needs. While MCOD allows the joint usage of data pools across schemas and schemaoverarching SQL statements, the advantage of MCOS lies in the option o ption to run various software versions of SAP HANA in the same environment.
MULTITENANT MULTITENA NT DATABASE DATABASE CONTAINERS Multitenant database containers (MDCs) are another virtualization option for SAP HANA deploy ments. With MDCs, you can run multiple, strictly separated database tenants on one SAP HANA system. The features are: • Data center operations automation by running multiple tenant databases in one SAP HANA system and managing them as one • Tenant-specic lifecycle management, including backup and restore options • A clear separation of application data and user management • Local user management within each tenant database • Session and transaction management per tenant database • The option to move or copy tenant databases to other systems or hosts
The benets of MDCs are a lower TCO because of a single software software stack, central conguration, and administration at the database level; direct data 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 NetWeaver on the Same Server The SAP HANA® business data platform and the SAP NetWeaver® 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 HANA software system
SAP NetWeaver AS for ABAP System for SAP NetWeaver AS for ABAP
SAP HANA business data platform System for SAP NetWeaver AS for ABAP
SAP HANA software system
Separated deployment approach
SAP HANA and SAP NetWeaver AS deployed on one server
+ Hardware resources isolated – Separate hardware
+ Cost-optimized approach – Shared memory and CPU resources 14 / 17
© 2017 SAP SE or an SAP aliate company. All rights reserved.
Dene a High-Availability and Disaster-Recovery Strategy and Sy System stem Replication Requirements Requirements High availability is a set of techniques, engineering practices, and design principles for business continuity. SAP HANA oers dierent kinds of high-availability high-availability mechanisms, supporting a broad range of scenarios for recovery from various faults – from simple software errors through system and hardware hardware crashes up to disasters that decommission a whole data center. The following four basic high-availability solutions are available: • Backup and recovery – recovery – Regular shipping of data backups to a remote location over a network or by couriers can be a simple and relatively inexpensive way to prepare for a disaster. • Host auto-failover – This covers hardware crashes for scale-out setups. One or more standby hosts are added to an SAP HANA system, usually within the same data center, and are congured to work in standby mode. The standby host has no access to data and does not accept requests requests and queries. • Storage replication – The storage itself replicates replicates all data to another location within one or between several data centers. The technology is vendor-specic hardware, hardware, and multiple concepts are available in the market.
• System replication – SAP HANA replicates all data to another location within one or between several data centers. The technology is independent from hardware vendor concepts and reusable with a changing infrastructure. Depending on your data center operations, hardware conguration, and software landscape, you can select between several options for high-availability high-availability scenarios for your SAP HANA environment. SAP works closely with hardware hardware partners to provide customers a exible choice between dierent but best-suited hardware and software solutions for high-availability and disasterrecovery scenarios. Current capabilities include, for example, single-node failover with multiple standby servers within one cluster conguration and storage-based mirroring of SAP HANA system replication across data centers. For a detailed description of all high-availability and disaster-recovery disaster-recovery oerings available for SAP HANA, please refer to the brochure Protect Enterprise Readiness with the High Availability Availability Features of SAP HANA. HANA.
SAP works closely with hardware partners to provide customers a exible choice between dierent software solutions for high-availability and disaster-recovery scenarios.
15 / 17
© 2017 SAP SE or an SAP aliate company. All rights reserved.
Change Management transaction management between ABAP and the SAP HANA database. This keeps transaction pro cessing on the ABAP layer alive and allows you to change components (software versions) on the layers below on the secondary (shadow) instance of SAP HANA.
EVALUATE UPDATE OPTIONS There are various options for updates. Zero-Downtime Zero-Downtime Maintenance Uptime is the most critical factor that inuences the TCO of an IT organization. Therefore, system administrators are always looking to reduce downtime, be it incidentally by errors or crashes or planned for maintenance reasons. When When run ning the system replication replication conguration for SAP HANA, zero-downtime maintenance allows you to make software updates or hardware exchanges with minimum downtime. This feature is based on the “connectivity suspend” feature of SAP NetWeaver Application Server for ABAP. For other environments, a near-zero-downtime option is available. available.
When applying zero-downtime maintenance, the shared library of the database interface decouples decouples
Capture and Replay To safeguard business continuity, thorough testing is required prior to applying changes in your hardware hardware or software conguration – be it new hardware, software updates, changes in conguration, table distribution, disk partitioning, or indexing. With With the capture and replay tool for SAP HANA (see Figure 9), you can predict perfor mance and the cost impact of updates to comply with service-level agreements and budget con straints. Plus, you can perform stability and per formance checks to nd root causes of system 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
SAP HANA® revision XXX
Capture workload
Analyze results
1 SAP HANA revision YYY
Production system
Test system 16 / 17
© 2017 SAP SE or an SAP aliate company. All rights reserved.
The tool captures real system workloads and replays them in a separate testing environment environment rather than generating test data, so simulations are more accurate. Also, the tool fully integrates with SAP HANA and has an intuitive user inter face based on the SAP Fiori® user experience to make managing and monitoring capture and replay processes easier.
SAP HANA Cockpit The SAP HANA cockpit is a tool built with SAP Fiori technology. It is your single point of access for various native administration tasks for SAP HANA. The cockpit provides a role-based concept that enables you to have a personalized view of the tiles and applications for each system administrator.
And if you can’t aord or don’t want to pay for a separate testing environment environment for running your replay, a hybrid cloud service for SAP HANA can do this for you in a private cloud provided and managed by SAP. For details, please refer to the brochure Upgrade Your SAP HANA Platform with Capture and Replay Performance Management .
SAP Landscape Management SAP Landscape Management software oers operations and automation features features specically for SAP HANA. For instance, provisioning and management of MDCs is simplied. The setup for system replication – in particular, the proce dure for takeover and failback – and the system refresh procedure using backup and restore are fully automated. SAP Landscape Management further provides a near-zero-downtime mainte nance option for SAP HANA.
To nd 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 aliate company. All rights reserved.
Follow us
www.sap.com/contactsap www.sap.com/contactsap
47913enUS (18/04)
© 2018 SAP SE or an SAP aliate compan y. 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 aliate c ompany. 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 specications may vary. These materi als are provided by SAP SE or an SAP aliate compa ny for informational purposes only, without representation or warranty of any kind, and SAP or its aliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP aliate compan y products and servic es 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 particul ar, SAP SE or its aliated compa nies 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 a liated 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 a liated 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 forward-looking statements are subject to various risks and uncertainties that could cause actual results to dier materially from expectations. Readers Readers are cautioned not to place undue reliance on these forward-looking statements, 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 a liate 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.
