Making SAP HANA Mainstream in your Datacenter - Part 1

Part 1: The business case for SAP HANA Tailored Datacenter Integration as the mainstream option for on-premise SAP HANA deployments.

Making SAP HANA Mainstream in your Datacenter

Exec Summary

Introduction

Evolution of SAP Hana

TDI: A New Era

Future Implications

Challenges of SAP Hana

SAP Certification/ EMC Validation

EMC Federation

Conclusion

Next Steps

Resources

Abstract: SAP HANA, being still a young technology, is evolving and maturing. A sign of this maturity is the increased deployment options it increasingly provides. This whitepaper will demystify SAP HANA Tailored Datacenter Integration as a concept, while presenting its business rationale and benefits, helping you to navigate through the currently available options, and showcasing why this is the option most organizations chose when transitioning from a “SAP HANA PoC phase”, to a “SAP HANA mainstream adoption phase”.

Target Audience: This whitepaper is destined for enterprise architects, SAP technical architects, directors of operations, directors of IT engineering, directors of architecture, and all senior technologists involved in defining and deciding the deployment model for SAP software based on SAP HANA in their organizations.

Exec Summary

Introduction


TDI: A New Era

Future Implications



EMC Federation

Conclusion

Next Steps

Resources

2 | Copyright © 2015 EMC Corporation. All rights reserved. Published in the USA.

Table of Contents 4 Executive Summary

5 Introduction • Business Considerations When Choosing a HANA Architecture

7 The Evolution of the SAP HANA Infrastructure: From Appliance to TDI • The Experience of the SAP HANA Early Adopters • Running SAP HANA in “Normal” Datacenter Architectures

8 TDI: A New ERA for SAP HANA • TDI: A Move Toward Openness • Running SAP HANA on Typical Datacenter Architectures

9 Future Implications for SAP HANA Infrastructure Architectures • Data Temperatures • The Internet of Things and Big Data • Unified OLTP & OLAP

11 Challenges of SAP HANA – How EMC’s TDI Portfolio Delivers Value • OPEX Implications of SAP HANA Adoption • The Complexity of HANA Architecture • The Rigidity of HANA Infrastructure Architectures • The Values that EMC Brings to TDI

13 SAPCertificationandEMCValidationofEMCHANASolutions • Rules for SAP’s Support of SAP HANA TDI in Production • Relaxed Requirements for Non-Production SAP HANA Systems • SAP Hardware Certification for SAP HANA • EMC’s Validation Procedure for SAP HANA Solutions • EMC Solutions for Deploying SAP HANA On-Premise •EMCCertifiedStoragePlatformsforSAPHANATDI •EMCCertifiedPlatformsforSAPHANABackupandRecovery(HANA-BRINTCertified) • EMC Validated Solutions for SAP HANA

17 EMC Federation Offerings for SAP HANA On-Premise

17 Conclusion • Next Steps • Resources


Exec Summary

Introduction


TDI: A New Era

Future Implications



EMC Federation

Conclusion

Next Steps

Resources

Executive Summary Early 2015, SAP announced the reinvention of its SAP ERP flagship software—dubbing it S/4—and told the world that future versions will only run on SAP HANA (SAP will discontinue all non-HANA database support for S/4 by 2025).1 Organizations immediately began looking for the most suitable migration and implementation roadmaps to support their mission-critical SAP applications.

But developing and designing the right architectures for an SAP landscape is challenging. Organizations need an architecture that is capable of making SAP more efficient and agile today, but which can also take advantage of future technical innovations. SAP HANA Tailored Datacenter Integration (TDI) is that optimal, future-proof option for organizations planning to make SAP HANA mainstream in their datacenters.

SAP HANA was initially available as an appliance only. This created significant financial and operational challenges for many organizations. However, today SAP HANA TDI offers you a range of choices for deploying HANA, with even more to come in the future. As a result, more and more customers are choosing the flexible and cost-effective TDI model for their HANA deployments.

In fact despite the strange name, SAP HANA Tailored Datacenter Integration represents nothing more nothing less than what SAP customers have always done: right size the infrastructures for their real business requirements, while aligning with existing datacenter standards in terms of infrastructure, tools, operational processes and existing skillsets. It’s all about standardization of IT, and its principles can today be applied to SAP HANA as well.

The reason IT organizations are looking at standardization of IT, is because it has proven to enable you to:

• Achieve lower TCO (Total Cost of Ownership)• Reduce risk• Implement simpler change processes • Free up your IT resources to invest more in business focused innovation

1 See SAP S/4 HANA FAQ - http://www.sap.com/bin/sapcom/en_us/downloadasset.2015-03-mar-02-23.sap-s-4hana-frequently-asked-questions-pdf.bypassReg.html

By the end of this paper, you will have:

• a short overview of SAP HANA evolution – past and near future;

• a perspective on the architecture implications of SAP HANA in terms of what its specific workload profile brings as new;

• a clear view of SAP HANA TDI as the right deployment option for making SAP HANA Mainstream on your datacenter;

• a brief summary of EMC’s wide range of choices for your SAP HANA deployment, as well as where EMC can help you further.


Exec Summary

Introduction


TDI: A New Era

Future Implications



EMC Federation

Conclusion

Next Steps

Resources

http://www.sap.com/bin/sapcom/en_us/downloadasset.2015-03-mar-02-23.sap-s-4hana-frequently-asked-questions-pdf.bypassReg.html

http://www.sap.com/bin/sapcom/en_us/downloadasset.2015-03-mar-02-23.sap-s-4hana-frequently-asked-questions-pdf.bypassReg.html

IntroductionSAP HANA is a truly transformational technology. Its three most significant architectural attributes—enabling in-memory computing, allowing structured and unstructured data on the same platform, and providing for the ability to run OLAP and OLTP systems on the same platform—have allowed organizations to build new and differentiated business models designed for competing in the “Digital Economy.”

But because SAP HANA is such a new and disruptive technology, many IT organizations are still working to understand it, as well as decide the best way to integrate it into their datacenter portfolios. In many cases, organizations have deployed proof-of-concept (PoC) systems to evaluate whether SAP HANA could deliver the results SAP has promised. Unfortunately, in many of these PoCs, organizations failed to consider datacenter integration, operations, and transformation practices when implementing HANA, leading to negative ROI evaluations despite the positive SAP HANA technical outcomes seen. This has led in many organizations for SAP HANA adoption to be halted, re-evaluated or even completely canceled.

Today, as IT organizations take HANA mainstream, they must take a closer look at whether the architectures selected for their PoCs are in fact the best options for running SAP HANA for mission-critical applications.

Some of the top attributes required by mission-critical applications are: • Aggressive performance service-level agreements (SLAs) for large workloads;• Near-zero recovery-point objectives (RPOs) and shorter recovery-time objectives (RTOs);• An automated dynamic change environment that delivers regular lifecycle management activities

with the least possible disruption to the business (DevOps).

Automation

Fundamental Infrastructure Design Variables

Performance Availability

› Introduction


Exec Summary

Introduction


TDI: A New Era

Future Implications



EMC Federation

Conclusion

Next Steps

Resources

Business Considerations When Choosing a HANA Architecture

When choosing a HANA deployment model, organizations need to remember the basic business considerations that all IT groups must take into account when making technology deployment decisions.

You have to think how to best:

• Manage costs—Organizations need to achieve their business goals in ways that keep them competitive. Overspending on technology is only acceptable if there is a clear business benefit;

• Minimize risk—IT must ensure operational stability as key to the business’ reputation and profitability;

• Enable innovation—Increasingly, IT must act as an innovation engine, helping organizations differentiate themselves in crowded markets;

• Simplify changes—Organizations today must be able to respond swiftly to new technologies and changing market conditions, and IT but be a key enabler of change, not a roadblock.

Business units led many of the initial SAP HANA PoC decisions without including the IT organization in the all-important evaluation and deployment processes. As a result, early Hana deployments were often less than successful, in terms of the ROI when considered all the SLO (Service Level Objectives) requirements to the specific business scenario.

Manage RiskReduce Costs

Simplify Change

Drive Business Innovations

Today’s Business Equation Making Change Part of the “Business DNA” is Key to Survival

› Business Considerations

Automation

Automation

Automation

BusinessBenefits

Cost to operate

TCO

Cost to Evolve

over the lifecycle of the solution: 5 to 10 years

grow, expandsustain SLAs

-

CAPEX OPEX+

+

=

=

=

ROI

TCO

OPEX


Exec Summary

Introduction


TDI: A New Era

Future Implications



EMC Federation

Conclusion

Next Steps

Resources

This lack of “strong enough ROI” to move from PoC to “mainstream” SAP HANA adoption, was in many cases due to only considering the Business Benefits and CAPEX, and not considering or severely under-estimating the technical requirements and operations implications (OPEX), which is the area the IT organization is expert on when working together with the business units on new technology adoption decisions.

The Evolution of the SAP HANA Infrastructure: From Appliance to TDI In the beginning, organizations interested in deploying SAP HANA had only one architecture option: a combined hardware and software appliance that acted as a “black box” in their datacenters.

SAP Hana was announced in 2010 and only made available in 2011. Given the newness of the technology, buying an appliance with software pre-installed on it and having a single point of contact for support was a sensible option. However, as organizations became more experienced with SAP HANA, began promoting it to production and requiring more capacity from those systems, they discovered that the appliance-based architecture lacked the flexibility to satisfy the basic business principles of reducing cost, managing risk, and simplifying change.

The Experience of the SAP HANA Early Adopters

Early SAP HANA adopters found that the appliance model resulted in negative operational consequences and made all changes affecting infrastructure more costly and lengthy than what they experienced with previous SAP application stacks. This had not been foreseen.

PEOPLE•Training and Awareness•Expertise and Qualifications•Competent Resources

PROCESS•Management Systems•Change Management•Best Practices

TECHNOLOGY•Innovation Research•Technology Integration•Modeling and Automation

OrganizationalReadiness

› Early Adopters


Exec Summary

Introduction


TDI: A New Era

Future Implications



EMC Federation

Conclusion

Next Steps

Resources

Specifically, the appliance model resulted in significantly higher costs of operation; to a point that any potential CAPEX savings from the initial investment phase were completely absorbed in higher OPEX in just the first year.

The appliance model also required organizations to create “islands of knowledge” in the datacenter. These islands needed different skillsets, architectures, operational procedures, and tools than non-HANA systems. Not leveraging the broad knowledge already existing on the customer’s IT organization made it harder to operate and change the SAP HANA systems that customers had deployed in the old “non-HANA” world. This led to dependence on appliance providers, that in many cases either were not able to deliver at all, or delivered the needed services at high cost and low response time.

Running SAP HANA in “Normal” Datacenter Architectures

What was needed: a way to make SAP HANA mainstream. Organizations needed to apply standard datacenter architecture principles like standardization of technology stacks; standardization of operation practices; integration with existing tools and processes when deploying HANA. Not only would this lower costs and risk on operations and change, but also it would enable a simpler automation of IT.

TDI: A New ERA for SAP HANA TDI: A Move Toward Openness

SAP listened to the concerns of early adopters and the demands of customers and evolved HANA accordingly. In 2013, it introduced a program called TDI that is the embodiment of a new openness in the HANA architecture.

TDI stands for TailoredDatacenterIntegration and describes a program that allows SAP HANA customers to leverage existing hardware, tools and IT processes for their SAP HANA environment. Previously, an SAP HANA appliance was limited to the components already within the certified configuration, which posed significant constraints in terms of tools integration. TDI targets the usage of existing infrastructure components already in the customer’s landscape, and also leverages current skillsets, tools and processes.

With the increased openness manifested in the SAP HANA TDI program, coupled with the increasing availability of skilled HANA resources, and the adoption of mission critical S4 HANA, the appliance model will not be viable for customer with large enterprise environments.

SP1 SP2 SP3 SP4 SP5 SP6

2012-11 2013-05 2013-11 2014-05 2014-11

SP7 SP8 SP9 SP10

APPLIANCE TDI

FUTU

RE

TDIANNOUNCEMENT

2015-07

. . .

› Running SAP Hana

› Move toward Openness


Exec Summary

Introduction


TDI: A New Era

Future Implications



EMC Federation

Conclusion

Next Steps

Resources

Running SAP HANA on Typical Datacenter Architectures

With TDI, an organization can design an SAP HANA architecture strategy based on the principles of standardizing technology stacks, standardizing operations practices, and integration with existing datacenter wide tools and processes.

All this is critical in light of the aggressive service level agreements (SLAs) required by mission-critical systems.

Future Implications for SAP HANA Infrastructure ArchitecturesToday, thanks to the new openness of the HANA architecture, there is no reason why HANA should be siloed. Instead, the same datacenter architecture should be used for both HANA and non-HANA workloads to enable mainstream adoption.

Three trends in particular are of importance to upcoming SAP HANA infrastructure architectures: data temperatures, the Internet of Things (IoT), and Big Data.

Data Temperatures

Considering the costs associated with the storing and processing of information, it is widely accepted today that each piece of data should reside on the most economically suitable repository based on its business value.

Warm Data Cold / Frozen Data Raw Data

SAP HANA

HOT DATA

Dynamic Tiering SAP IQ NLS/ADK HADOOP

+ + +

Data Temperatures

HANA Total Cost of Ownership Evolution

SAP

HAN

A TC

O

2012

Decreasing TCO

2014

ApplianceDelivery

TailoredData Center

Delivery

Virtualization

2013

› Running SAP Hana

› Data Temperatures


Exec Summary

Introduction


TDI: A New Era

Future Implications



EMC Federation

Conclusion

Next Steps

Resources

SAP has introduced this concept into the SAP HANA world through the principle of “data temperatures.” Under this principle, not all data will reside in memory, as that would be cost prohibitive. Instead, each type of information would have its own data-managementserver. That is, every SAP HANA application will have different storage repositories depending on the data type, volume, and value, with repository managed by a different server. One of these functions is dynamictiering2 , and it will have very important implications in terms of datacenter architectures. Among other things, dynamic tiering keeps the in-memory footprint of the application small.

This clearly precludes the use of an appliance for SAP HANA. What will be required: a distributed architecture leveraging multiple servers and storage repositories.

Organizations already have the ability to create virtualized servers using VMware. This suggests a possible architecture where TDI and virtualization together provide the most cost-effective, most flexible, and lowest risk environments, empowering businesses to fully leverage in a timely manner the business innovation that SAP HANA and S/4 delivers.

The Internet of Things and Big Data

Many early adopters of SAP HANA used the platform as a “sidecar” technology to speed up processing of important functions. However, that has now changed with SAP HANA’s integration of structured and unstructured on the same platform. This will enable faster decisions based on real-time business, social, and market data that are the foundation for many Big Data initiatives today.

As Internet of Things (IoT) scenarios gain traction within SAP applications, this will also make it possible to process machine data at increasing speed and integrate that data into business processes.

Most machine data that comes from the IoT is unstructured, and the volume is exceedingly large—easily qualifying as Big Data—thus making it difficult to process on typical database architectures. SAP HANA changes that by allowing you to process both structured and unstructured data on the same platform.

You can even connect HANA and Hadoop to load more IoT information into HANA, on which you can then perform extremely fast analysis. HANA is a great place to store high-value, frequently used data, and Hadoop is where you can store information that you don’t want to structure in advance, like web logs. In short: HANA and Hadoop are very good friends when it comes to IoT.

In these scenarios, there will be the need to provide multiple servers and repositories to the SAP HANA platform, which makes it impossible for the SAP HANA appliance model to respond.

UnifiedOLTP&OLAP

With SAP HANA, OLAP (online analytical processing) and OLTP (online transaction processing) systems will also coexist on the same platform, allowing you to know what your business situation is at any given time. You can also act on real-time operational reporting without having to wait for data movement or data consolidation to get a single source of the truth.

Having said this, the cost of having both current and historical data in memory will just not be cost effective. While it is crucial to have current data in memory to support operational reporting, that’s not necessarily true for the historical data. Being able to offload historical data from memory, while being still integrated in SAP HANA, will allow you organization have a lower TCO in exchange for higher – but acceptable – response times when performing historical data analysis.

New developments like SAP HANA Dynamic Tiering, introduced as a new feature with SAP HANA SPS09, come to enable these scenarios.

2 Dynamic Tiering functionality was introduced in SAP HANA SPS09, and enables SAP HANA to move data to a disk-based repository call the extended store, thus reducing the in-memory footprint of applications. This feature is a key component in SAP’s S/4 communicated characteristic of being able to split “current and historical data”, to different “HANA managed” repositories.

› IoE and Big Data

› Unified OLTP & OLAP


Exec Summary

Introduction


TDI: A New Era

Future Implications



EMC Federation

Conclusion

Next Steps

Resources

Challenges of SAP HANA – How EMC’s TDI Portfolio Delivers ValueAll in all, organizations wishing to deploy HANA, previously faced three main challenges, which made changing HANA infrastructures difficult:• Cost, particularly OpEx• System(s) complexity• Rigidness of non-TDI deployment (appliance model)

With TDI, those challenges are now a thing of the past. EMC’s close partnership with SAP has allowed for the advancement of openness of the HANA platform, which in turn has enabled EMC to offer a broad TDI portfolio to suit your organization’s needs.

OPEX Implications of SAP HANA Adoption

In early PoC installations of SAP HANA, many organizations only considered the capital expense (CAPEX) aspects of the appliance when calculating the return on investment (ROI) of the PoC.

But the operating expenses (OPEX) associated with IT systems over a five-year lifecycle are considerably more than the initial CAPEX requirements. If those operating costs are not carefully evaluated at the start of a project, any ROI calculated using only the implementation capital costs would be swallowed up by the costs of operating, adapting, and evolving the solution in question. This was not good news for HANA.

Although there were obvious business benefits from adopting SAP HANA, many early adoptions found that the total implementation and management costs simply did not provide a strong enough ROI to justify maintaining the systems in question. As a result, many organizations, after limited PoC scenarios, ended up leaving SAP HANA software on the shelf, canceling or postponing further investments until they were able to solve the ROI equation to their satisfaction.

The Complexity of HANA Architecture

The first HANA infrastructure architectures were also very complex to change and evolve. For example, if you had deployed a HANA appliance with 2TB of internal storage, but wished to extend that capacity of that appliance, or upgrade it to the latest CPU, you first had to capture the current state of the system in the backup, upgrade the appliance, and restore the back up to the new appliance. This takes time, and increases the outage window.

ROIOperationsEvaluation

(OPEX)

InvestmentAnalysis(CAPEX)

TechnicalRequirements

Business Needs

Cost

0 10 years

› OPEX

› Complexity

OPEX

CAPE

X

Time5 years


Exec Summary

Introduction


TDI: A New Era

Future Implications



EMC Federation

Conclusion

Next Steps

Resources

On the other hand, using TDI with external storage, you merely have to shut down the system, install the new CPUs, and attach back to the storage unit. No data need be moved at all.

Another example of the complexity is that most organizations want to keep the main database small to reduce the licensed HANA in-memory components. This involves data tiering, or keeping your cold data somewhere else. To implement this, you need to add compute, network, and storage for each tier (unless you put them all on a virtualized VBlock). With TDI, you can simply orchestrate snapshots, backups, or data protection using the same storage infrastructure.

The Rigidity of HANA Infrastructure Architectures

With the appliance, the inflexibility of HANA infrastructures was obvious. You were tied to specific hardware solutions from specific vendors in specific configurations, and to change or update those appliances meant ripping and replacing the hardware at high CAPEX.

But there were also issues of rigidity with other infrastructure architectures as well. For example, if you wished to deploy HANA in a public cloud, you don’t have the ability to upgrade your HANA systems at your own discretion. Instead, you were dependent on the public cloud infrastructure vendors’ update cycles.

The Values that EMC Brings to TDI

EMC has collaborated closely with SAP on the TDI program, and is today a leading vendor with regards to flexible TDI options. Here are the ways that an EMC solution for SAP HANA TDI makes sense:

• Protect your investment—EMC has the largest HANA TDI portfolio in the market, a portfolio that consists of storage, backup, high availability, and replication. For example, EMC offers six SAP-certified storage platforms and two SAP-certified backup solutions, as well as nine EMC-validated data protection and replication solutions (see pp. 14). You can use the same storage platforms for all SAP applications (including HANA) and incorporate a simple extension into non-structured Big Data scenarios with HDFS (Hadoop Distributed File System).

• Manage risk—You get much more flexibility at less risk with VCE pre-build solutions and single vendor support that simplifies change and operations without requiring special infrastructure. This allows you to have fewer IT building blocks in your datacenter, and to leverage your existing IT skill sets and processes. Additionally, system changes are safer with external storage, with less data movement, and shorter outages.

• Run HANA at optimal TCO—You can minimize TCO (total cost of ownership) by running mixed workloads on the same platform, while at the same time, leveraging existing infrastructure components, data protection solutions, and IT processes as well as the skill sets you’ve built up around EMC solutions.

› Rigidity

› EMC Values


Exec Summary

Introduction


TDI: A New Era

Future Implications



EMC Federation

Conclusion

Next Steps

Resources

SAP Certification and EMC Validation of EMC HANA Solutions Two factors make SAP HANA workloads different from previous-generation SAP systems.

• The read/write ratio—Although many organizations have observed ratios of 80 percent to 90 percent of reads and 10 percent to 20 percent of writes on SAP applications like Oracle, on SAP HANA—since all the reads on normal operations are done in memory—we see almost 100% of writes in terms of disk activity under normal operation.

• Larger block writes—Until now, organizations have typically seen block writes of mostly small sizes (between 4K and 8K blocks). However, in SAP HANA we see block writes of very large sizes going higher than 1 MB and even up to 64MB.

Although infrastructure components can be the same, infrastructure configurations will need to be adjusted for the SAP HANA I/O profile. As a result, SAP has established rules for organizations that wish to receive support for SAP HANA TDI architectures on production systems.

Rules for SAP’s Support of SAP HANA TDI in Production

By requiring that hardware providers and installers follow very specific guidelines when deploying SAP HANA the end customer is protected, and the risk of implementing new architectures reduced.

The options for SAP HANA deployment keep increasing, and we believe that there will be a time where there will be no restrictions at all on the infrastructure options to deploy SAP HANA.

But today, there are still certain limitations and rules for those seeking “production support” of their SAP HANA infrastructure architectures:• Choose servers from SAP’s list of certified servers.• Choose storage from SAP’s list of certified storage.• Choose a certified SAP HANA Installation Consultant to perform the installation of the SAP HANA

software.• Confirm that the architecture sustains SAP’s requirements in terms of operating system

configurations, storage, and network performance.

Yet even with these constraints defined by SAP, TDI represents a huge step forward in the openness of SAP HANA in terms of its datacenter integration possibilities.

It is important to remember that all these rules set by SAP aim to ensure performance, and are not about functionality. SAP HANA may run even if these rules are not fulfilled, but stability and performance may not match expectations. SAP conditions performance support on having an infrastructure that fulfills its rules. Having “SAP certified” infrastructure architectures in support of SAP HANA also ensures customers a stable and performant system, which is important to sustain business critical operations.

Read %

0%

*Only HANA log volume block sizes displayed, which is the write heavy area. HANA data volume block sizes range even larger, up to 64MB.

1 10 100 100020% 40% 60% 80% 100%

OLTP

OLAP

HANA*OLAP or OLTP

Write % Max block size KB Min block size KB

90% 10%16

4

164

10244

60% 40%

90%10%

› Rules


Exec Summary

Introduction


TDI: A New Era

Future Implications



EMC Federation

Conclusion

Next Steps

Resources

Relaxed Requirements for Non-Production SAP HANA Systems

On the other hand, a certified infrastructure to run non-production SAP HANA systems is no longer required. The catch here is that SAP will not provide performance support on these platforms. If customers need to use a non-production system to perform performance testing, it is still advised to use a certified configuration.

SAPHardwareCertificationforSAPHANA

To ensure the best results for customers, SAP has set up a certification process.

For example, when certifying enterprise storage, manufacturers need to go through a series of performance and availability tests, and must document the configurations that customers would need to perform in order to achieve the desired performance and availability results. SAP also has a certification process for backup tools integration with SAP HANA “BackInt” interface.

EMC’s Validation Procedure for SAP HANA Solutions

EMC has a tradition of being a reliable partner for our customers’ most critical needs in supporting their most critical business applications: the ones with the most demanding availability and performance requirements.

Because of this, before releasing any technology solution to be used with SAP HANA, EMC puts it through a robust series of internal tests. This way, we can provide guidance to our customers on the best way to configure the solutions when using them to support SAP HANA.

EMC doesn’t experiment with our customers’ businesses. Therefore, even after a certain platform is certified by SAP, EMC continues through the validation of functionalities not covered in SAP’s certification process before releasing those specific functionalities for production use by customers.

The benefit of this approach: by documenting all the knowledge developed, we enable organizations to dramatically reduce both the learning curve and the risks of integrating SAP HANA into their existing datacenter architecture.

For those products within the EMC portfolio where there is no SAP certification process, EMC undergoes a similar validation to SAP’s certification process internally in order to ensure results to our customers.

This validation is not an SAP requirement, but rather an EMC quality-assurance (QA) process aimed at continuing to provide the best solutions to the market in terms of scalability, availability, and stability.

SAP’s Current Certification Rules Certifying Enterprise Storage for SAP HANA TDI

Availability

Validate platform works with...

SAP HANA auto-host failover mechanism

Documentation

Document and make public the...

Configurations used for performance and availability tests

Performance

Ensure platform sustains...

SAP required performance KPIs

› Requirements

› Certification

› EMC Validation Solutions


Exec Summary

Introduction


TDI: A New Era

Future Implications



EMC Federation

Conclusion

Next Steps

Resources

EMC Solutions for Deploying SAP HANA On-PremiseDue to the dynamic nature of all things related with SAP HANA, the list of EMC solutions in this document is not exhaustive. Be sure to visit EMC’s online resources on SAP HANA for the latest news.

EMC CERTIFIED STORAGE PLATFORMS FOR SAP HANA TDI

• VMAX3certifiedforSAPHANATailoredDatacenterIntegration—The EMC VMAX3 is the most scalable storage platform in the market, capable of scaling up to 104 SAP HANA nodes on a single VMAX400K storage array.

• VMAX2certifiedforSAPHANATailoredDatacenterIntegration—To protect our customers’ investments, we have certified VMAX2 with SAP HANA and validated the majority of VMAX2 functionalities.

• VNX2certifiedforSAPHANATailoredDatacenterIntegration—For customers with different datacenter strategies, where price-performance is the key decision consideration, we have also certified the VNX platform.

• XtremIOcertifiedforSAPHANATailoredDatacenterIntegration—By certifying EMC XtremIO with SAP HANA, we are enabling customers for whom datacenter footprint and energy efficiency are top concerns to use that platform for SAP HANA as well.

• VPLEXcertifiedforSAPHANATailoredDatacenterIntegration—With the certification of EMC VPLEX for SAP HANA Tailored Datacenter Integration, EMC is enabling disaster avoidance (or continuous availability) configurations to be leveraged for SAP HANA systems as well.

All Certified Storage Platforms for SAP HANA Tailored Datacenter Integration can be found at SAP’s site: http://global.sap.com/community/ebook/2014-09-02-hana-hardware/enEN/enterprise-storage.html#categories=EMC%20Corporation

Early Adopters

Build on your own

Factory BuildMAINSTREAM ADOPTION

PoC/Non-critical scenarios

Mission Critical System

Highest Reliability and Lowest Risk

Your preferred Server Vendor CertifiedEMCstorage

Converged InfrastructureSingle point of contactStorage

EnterpriseStorage

Application

Database

Operation System

Virtualization

Server

Server

Network

Network

Storage

Storage

SAPHANAServer

SAPHANAServer

Appliance

Dedicated IT

SAP HANA TDI

Shared IT Resources

› Deploying


Exec Summary

Introduction


TDI: A New Era

Future Implications



EMC Federation

Conclusion

Next Steps

Resources

https://community.emc.com/docs/DOC-17151




http://www.emc.com/collateral/technical-documentation/h13984-storage-config-best-practices-sap-hana-tdi-xtremio-cg.pdf

http://www.emc.com/collateral/white-papers/h14283-vplex-sap-hana-sg.pdf

http://global.sap.com/community/ebook/2014-09-02-hana-hardware/enEN/enterprise-storage.html#categories=EMC%20Corporation

http://global.sap.com/community/ebook/2014-09-02-hana-hardware/enEN/enterprise-storage.html#categories=EMC%20Corporation

EMC CERTIFIED PLATFORMS FOR SAP HANA BACKUP AND RECOVERY (HANA-BRINT CERTIFIED)

SAP has defined an integration where SAP HANA Studio can manage the backup and recovery processes, hold the backup catalog and scheduling, and integrate with external tools to store the backed-up data, while enabling at the same time centralized management of backups across the enterprise.

• EMC Data Domain Boost for Databases and Applications—EMC DataDomain Boost for Databases and Applications (DDBDA) is a new product from EMC: a server-side application that enables organizations choosing to use the SAP HANA Studio as the backup scheduler and catalog, to leverage all the benefits of deduplication and compression offered by EMC’s DataDomain and DataDomain Boost, reducing backup times, impact and footprint.

• EMC Networker—EMC Networker is EMC’s leading backup software. This is the option for those organizations that want to have a centralized backup and recovery management across the datacenter. It provides all the benefits of enabling the usage of SAP HANA Studio for backup scheduling, and DataDomain boost, alongside with centralized catalog management and monitoring.

All SAP HANA-BRINT certified backup solutions from EMC can be found at SAP’s site: http://global.sap.com/community/ebook/2013_09_adpd/enEN/search.html#search=HANA-BRINT&recordid=5813&tab=certifications

EMC Validated Solutions for SAP HANA

• EMC ScaleIO for SAP HANA persistency support in production—EMC has not only worked to do an internal validation of ScaleIO with SAP HANA, both on bare-metal installations as well as virtualized scenarios, but has also worked with SAP to have it supported with SAP HANA. ScaleIO is a solution mostly suitable for service providers with a datacenter wide strategy around either hyper-converged infrastructures or adoption for virtual Storage Area Networks. SAP statement on support for productive use of EMC ScaleIO with SAP HANA can be found on SAP Note 800326.

• DataDomain appliances for SAP HANA backup and archive—DataDomain is the backup destination when using either EMC Networker or EMC DataDomain Boost for Databases and Applications integration with SAP HANA as per the HANA-BRINT certification. DataDomain is also certified with known industry SAP Data Archiving solutions and can become the single repository both for backup and archive data, providing disaster recovery to such data through its long distance remote replication capabilities.

• EMC VNX1 for SAP HANA persistency non-productive use—EMC has released VNX 1st generation systems to be used in a TDI scenario only for usage with non-production systems.

• EMC validated replication solutions for productive use with SAP HANA—EMC has been progressing internal validation for all its replication technologies.

• EMC VNX technology for synchronous and asynchronous replication—“MirrorView /S and /A” have been released.

• EMC VMAX2 and VMAX3 technology for synchronous and asynchronous replication—s“SRDF /S, /A and /Star” have been released.

• EMC RecoverPoint—Currently being tested, and until all testing is completed, has been released with restrictions.

• EMC validated snapshot technologies for productive use with SAP HANA—Snapshot technologies simplify daily operational tasks of SAP HANA environments, being in support of comprehensive backup strategies, to build production copies of the system, to refresh data on Quality Assurance systems, or just as a rollback point in time image when performing software upgrades or changes.

• EMC has validated the snapshot technologies included in the currently certified storage platforms, namely: VNX SnapView, VMAX TimeFinder and XtremIO Snapshots.

› EMC Validation Solutions


Exec Summary

Introduction


TDI: A New Era

Future Implications



EMC Federation

Conclusion

Next Steps

Resources

https://support.emc.com/docu52462_Data-Domain-Boost-for-Databases-and-Applications-Release-1.0-Administration-Guide.pdf

https://support.emc.com/docu57630_NetWorker-Module-for-SAP-8.2-SP1-Administration-Guide.pdf

http://global.sap.com/community/ebook/2013_09_adpd/enEN/search.html#search=HANA-BRINT&recordid=5813&tab=certifications



http://www.emc.com/collateral/white-papers/h13731-storage-configuration-best-practices-sap-hana.pdf

https://service.sap.com/sap/support/notes/800326


http://www.emc.com/collateral/white-papers/h13955-vnx-storage-mirrorview-snapview.pdf



EMC Federation Offerings for SAP HANA On-PremiseOn-premise SAP HANA can be made even easier by deploying VCE vBlock systems for HANA TDI. VBlock Systems are factory-integrated, fully functioning systems that deliver the best of both appliance and TDI worlds.• The best of an appliance

Fully configured from factory• The best of TDI

Platform that can be used to run all datacenter workloads, including SAP HANA

The Vblock is a “datacenter in a box,” powered by the industry’s best server and storage components and virtualized using the industry-leading hypervisor VMware. Those components are certified under SAP’s HANA TDI program to be used for both HANA and non-HANA workloads.

ConclusionWhy is EMC the right partner to help you navigate the SAP HANA adoption journey?

Not only does EMC have a long history in partnering with SAP and leading server vendors on joint engineering and best practices around performance and availability, EMC IT runs SAP and specifically SAP Applications on SAP HANA, being as well an SAP reference customer.

This combination provides EMC a unique position to both solve today’s efficiency challenges and at the same time pave the ground for a future safe transformation to HANA.

When focusing specifically on the on-premise deployment of SAP HANA, which may serve as well as the infrastructure foundation for cloud providers, EMC’s goal is to simplify SAP HANA adoption.

Our joint innovation projects are designed to make SAP HANA a normal application in the datacenter.

› Offerings

› Conclusion

CRM BW

HANA HANA

SAP HANA Optimized Infrastructure

VBlock System for HANA TDIFactory built, single point of support ... in a shared infrastructure!

S4

servers+network+storage

AnyDB

Virtualization


Exec Summary

Introduction


TDI: A New Era

Future Implications



EMC Federation

Conclusion

Next Steps

Resources

http://www.vce.com/asset/documents/sap-hana-tdi-whitepaper.pdf

http://scn.sap.com/docs/DOC-60470

Making SAP HANA a mainstream component in the datacenter architecture, implies making it work with existing datacenter standards, skillsets and tools, principles that are valid for individual customers and cloud service providers alike.

As we discussed through this paper, driving architecture standards across the datacenter and including SAP HANA, will drive lower TCO, lower risk, enable simpler change and growth, while enabling you to free up resources from IT operations to focus further on supporting business innovation initiatives.

It’s this holistic view of datacenter architecture and operations, supported in our vast experience in supporting aggressive SLO’s, represents a unique asset for any organization designing their roadmap and future architecture blueprints when planning to make SAP HANA mainstream on their datacenter

SAP HANA is indeed evolving towards becoming a normal application in the datacenter, one that can be deployed on the same infrastructures you use today for all your other business applications.

So, when making your adoption decisions, take into consideration the following aspects:• Keep a close watch on SAP HANA datacenter integration options, and challenge all your providers

to make SAP HANA work on your existing architectural standards, as this will drive massive benefits in terms of cost, risk and change. And remember that SAP HANA is evolving towards increasingly reducing its datacenter integration restrictions.

• Tailored Datacenter Integration is the natural evolution of SAP HANA Datacenter Integration options, similar to the evolution from R/2 to R/3 more than 20 years ago. As simple as that.

• Converged Infrastructures provide the lowest amount of risk for customers who do not wish to manage infrastructure integration variables, but aim to build a standard foundation for a private cloud, one that can be common across SAP HANA and non-HANA workloads.

• Virtualization enhances all these possibilities, with more flexibility and lower TCO. Frame your virtualization discussion in context and evaluate whether the potential performance impact to your business when compared with all the benefits virtualization will bring to your operations.

› Conclusion

Driving standard architectural practices for SAP HANA and

non-HANA appliction

Making “all time” datacenter technologies and operations

practices work for HANA as well

Greatest EMC Win: SimplificationMaking SAP HANA “a normal application” in the datacenter

Simplifying SAP HANA datacenter deployment

and operations


Exec Summary

Introduction


TDI: A New Era

Future Implications



EMC Federation

Conclusion

Next Steps

Resources

Next StepsEMC is prepared to help you navigate through your IT transformation and assure your organization is “SAP HANA ready.”

Take a look at EMC’s SAP Travel Guide where you’ll find the locations in which the EMC SAP Team will be next. Meeting with our experts in person will provide you a unique opportunity to learn about our latest solutions, have access to our team’s learnings from engaging with multiple other customers that have already gone through SAP HANA implementation projects, and get advice in regards to your SAP HANA adoption strategy and architecture.

Contact your EMC sales representative today, or send a message to [email protected], to book a meeting or request your participation on one of EMC’s next SAP events.

And, watch out for the Part 2 of this whitepaper (coming soon). There you’ll find deeper information on EMC’s advice in regards to SAP HANA infrastructure architecture options.

ResourcesMore information on EMC Solutions for SAP can be found at the EMC Community Network page for SAP: https://community.emc.com/community/connect/everything_sap

More information on SAP HANA Solutions can be found at: https://community.emc.com/docs/DOC-17151

More information on SAP HANA TDI certified and validated solutions can be found at: https://community.emc.com/docs/DOC-31784

More information on Backup and Recovery Solutions for SAP HANA can be found at: https://community.emc.com/docs/DOC-31785

Learn from the experience of EMC as an SAP customer by following the EMC IT blog: http://itblog.emc.com/?s=sap

For an updated list of EMC’s next SAP events, consult our travel guide at: https://community.emc.com/docs/DOC-33218

› Nest Steps

› Resources


Exec Summary

Introduction


TDI: A New Era

Future Implications



EMC Federation

Conclusion

Next Steps

Resources



mailto:HANAsalessupport%40emc.com?subject=


https://community.emc.com/community/connect/everything_sap




http://itblog.emc.com/?s=sap


EMC2,EMC,RSAandtheirrespectivelogosareregisteredtrademarksortrademarksofEMCCorporationinthe UnitedStatesandothercountries.Allothertrademarksusedhereinarethepropertyoftheirrespectiveowners. ©Copyright2015EMCCorporation.Allrightsreserved.EMCCorporation,Hopkinton,MA01748-9103

Documents

Making SAP HANA Mainstream in your Datacenter - Part 1