Cisco & MapR bring 3 Superpowers to SAP HANA Deployments
•Download as PPTX, PDF•
0 likes•905 views
SAP HANA is an increasingly popular platform for various analytical and transactional use cases with its in-memory architecture. If you’re an SAP customer you’ve experienced the benefits. However, the underlying storage for SAP HANA is painfully expensive. This slows down your ability to grow your SAP HANA footprint and serve up more applications.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Cisco & MapR bring 3 Superpowers to SAP HANA Deployments
Similar to Cisco & MapR bring 3 Superpowers to SAP HANA Deployments (20)
More from MapR Technologies
More from MapR Technologies (20)
Recently uploaded
Recently uploaded (20)
Cisco & MapR bring 3 Superpowers to SAP HANA Deployments
- 1. Robert Novak and Barbara Miller, Big Data Partners Consulting SEs, Cisco Andy Lerner, Partner Solution Architect, MapR Featuring Cisco IT March 2017 Cisco & MapR bring 3 Superpowers to your SAP HANA Deployments
- 2. For Cisco: Robert Novak, retired UNIX sysadmin, now Consulting Systems Engineer on the Partner Alliance with MapR Barbara Miller, Consulting Systems Engineer on the Partner Alliance with SAP For MapR: Andy Lerner, Partner Solution Architect Works with partners to certify their solutions On the MapR Converged Data Platform
- 3. Sometimes superpowers come later in life, whether for a superhero or an application platform. 1. Context of Cisco and MapR for SAP HANA 2. Defining the Solution – bringing Cisco, MapR, and SAP together 3. Cisco IT implementation of joint solution 4. A peek behind the covers for storage resilience 5. Where do we go from here? What are we talking about today?
- 4. Setting The Context: Cisco and MapR for SAP HANA Production Deployments
- 5. Modern platform scaling enables you to match the compute and storage to the application Traditional applications (like SAP HANA) may not make this easy Ain’t nobody got time for that Last time we talked…
- 6. What if… Your scalable storage and compute platform provided industry-standard access methods like NFS Existing applications like SAP HANA could plug right in with no recoding New applications, including the Hadoop ecosystem, could live side by side with traditional applications
- 7. With Cisco UCS (Unified Computing System) and MapR’s Converged Data Platform… Your infrastructure can do just that. Amazing but true. (Tell me more?)
- 8. Defining the Solution: Validated Design for SAP HANA with MapR Converged Data Platform on Cisco UCS Infrastructure
- 9. • In-memory Database • Scale-up OLTP single node ERP applications (SoH, S4H) • Scale-out OLAP multi node Data Warehouse (BWoH, DM) • SAP HANA delivery models • Appliance • Tailored Data Center Integration (TDI) • Enterprise Storage (November 2013) • Xeon-based Servers (November 2014) • Cloud SAP HANA High-Level Overview ✓ ✓ ✓
- 10. • HANA in memory but still uses storage • Data persisted to disk periodically (/hana/data/<SID>) • Transaction logs persisted to disk on commit (/hana/logs/<SID>) • Database backup (/hana/backup) • Executables, tools, etc (/hana/shared) SAP HANA Storage
- 11. SAP Hardware Certification for HANA * Certification detail available at global.sap.com
- 12. Cisco Integrated Infrastructure for SAP HANA Appliance Launched 3/29/16 HANA Compute / Network HANA Storage • 4-16 x 2TB B460 HANA nodes • 2x 6332 FI • 1x N3K (or N9K / ACI) • Mandatory HWCCT Appliance KPI met • Mandatory Solution Support • Opt-out Cisco Managed Service • Scalable C240 storage • 3-8x C240 Storage Nodes • 24x 1.8T HDD • RHEL 6 • MapR Data Platform HANA Appliance
- 13. TDI Shared Network – Hadoop/Vora HANA Appliance HANA Storage MapR Hadoop, Vora, or other application Cluster
- 14. HANA Nodes Global Storage Pool Other Application Nodes • Scalable C240 storage • NAS Shared File System (NFS v3) • 3-xx C240 Storage Nodes • 24x 1.8T HDD • RHEL 6 • MapR Data Platform SAP Big Data Platform SAP HANA Dynamic Tiering UCS C240 Integrated Solution for SAP SAP HANA Vora Ready
- 15. Cisco SAP HANA Appliance Hardware Appliance Tested Configuration 8:4 – Passes strict SAP fsperf KPI – Validated by SAP 2:1 HANA:MapR node ratio Up to 16:8 ratio supported TDI UCS C240 NFS (MapR based)
- 16. © 2017 MapR Technologies 16 Open Source Engines & Tools Commercial Engines & Applications DataProcessing Search and Others Cloud and Managed Services Search and Others UnifiedManagementandMonitoring Search and Others Custom Apps MapR Converged Data Platform HANA Vora Enterprise-Grade Platform Services Web-Scale Storage MapR-FS MapR-DB Real Time Unified Security Multi-tenancy Disaster Recovery Global NamespaceHigh Availability MapR Streams Event StreamingDatabase HDFS API POSIX (FUSE, NFS) Kakfa APIHBase API OJAI API
- 17. © 2017 MapR Technologies 17 SAP HANA SAP HANA MapR Storage CLIENT NODE(S) SAP HANA SAP HANA SAP HANA SAP HANA SAP HANA SAP HANA SAP HANA MapR cluster
- 18. Real-World Customer Case: How Cisco IT deploys and uses the Cisco/MapR joint solution for its production SAP HANA environment Dileep Moturi, Program Manager, Cisco IT
- 19. SAP HANA Use cases at Cisco IT •Run the Business Dashboards for Sales •Weekly Sales Forecasting Process •Pipeline Analytics for Sales & Finance •Strategy & Planning Analysis Product Sales •Increase Attach Rate and Renewal Rates for Support Contracts •Unified view of Product and Services Sales Services Sales •End-to-End Visibility Across Entire Supply Chain •Improve Order cycle time for Manufacturing and Distribution Supply Chain •Global and Regional Partner Organization Reporting (Channels) •Partner Incentive and Performance Analysis Channel Sales •Real-time visibility in Sales Discounting •Discount Guidance and Pricing Analytics Commerce Pricing Sidecar Approach
- 20. Infrastructure Capacity Growth 2013 2014 2015 2016 2017 HANA Infra Capacity in TB PROD Capacity Non PROD Capacity What’s driving Infrastructure demand at Cisco? • New use cases • Increase in data volume • Increase in users • Fast IT : More non prod instances Challenges • Agility to grow linearly • Cost • Demand for more compute power
- 21. A quick look behind the covers
- 22. Disk Configuration with Hardware RAID • 2x 2.5” SSDs for OS and logs • 24x 2.5” disks for data • 4x RAID5 sets with 6 disks each • 1 virtual disk per RAID5 • Local data protection RAID5 Set 1 RAID5 Set 2 RAID5 Set 3 RAID5 Set 4
- 23. High Available NFS Access • Virtual IP address with automated fail-over • IP addresses are evenly distributed for load balancing Volume 1 Storage Pool RAID5 Set 1 RAID5 Set 2 RAID5 Set 3 RAID5 Set 4 Storage Pool RAID5 Set 1 RAID5 Set 2 RAID5 Set 3 RAID5 Set 4 Volume 2 Volume 3 NFS-Mounts NFS Gateway NFS Gateway A03-0300GA2 10K SAS 300GB N20-BBLKD UCS EX M4 N20-BBLKD UCS EX M4 UCS B460 M4 N20-BBLKD V I P V I P V I P
- 24. • Single disk failure • local RAID5 configuration prevents failure of the storage pool • simply replace single disk, raid controller rebuilds automatically • Multiple disk failure • if two disks of the same raid group fail, the storage pool is lost • MapR takes care of re-replicating lost containers on other storage pools • Node failure • all lost containers will be re-replicated among the cluster • immediately (if "minreplication" value is undershot) or after 1 hour Failure Handling
- 25. Software Defined SAP App Landscape SAP Applications (PRD) •SAP and SAP Related Workloads Storage Pools for HANA Persistence Non-SAP Applications •VDI, SharePoint, Exchange, etc. Hadoop Aggregation and Out-of-Band Management for SAP (Cisco Nexus and UCS Fabric) Storage Pool for SAP HANA SAP BW on HANA (PRD) •Scale-out Cluster SAP Suite on HANA (PRD) •2+ Node Scale-up HA Cluster
- 26. Where do we go from here?
- 27. • MapR & Cisco Make IT Better –Webinar Series continues 1. It's No Use Going Back to Yesterday's Storage Platform for Tomorrow's Applications (Available on mapr.com on-demand) 2. Cisco & MapR bring 3 Superpowers to SAP HANA Deployments (you’re soaking in it; on-demand soon) 3. Join us for “Cisco & MapR for Software-Defined AND Web-Scale Storage” (coming early May) • Check out Cisco Validated Designs (CVDs) for SAP deployments: cisco.com/go/bigdata_design • Follow: @gallifreyan, @mapr, @Cisco, and @CiscoDC on Twitter • Meet us at Cisco Live, MapR Convergence, & Strata+Hadoop World Resources
- 28. Thank you for joining us today.
Editor's Notes
- https://commons.wikimedia.org/wiki/File:Spider-Man_-_Mus%C3%A9e_Gr%C3%A9vin.jpg
- https://commons.wikimedia.org/wiki/File:Sailors_wait_in_their_forklifts_for_incoming_cargo_on_the_flight_deck_of_the_aircraft_carrier_USS_John_C._Stennis_(CVN_74)_during_a_replenishment_at_sea_on_March_30,_2013_130330-N-QI595-008.jpg
- Public domain By Wesso (Hans Waldemar Wessolowski) / Experimenter Publishing - http://www.philsp.com/mags/amazing_stories.html, Public Domain, https://commons.wikimedia.org/w/index.php?curid=42839174
- Unlike typical relational databases, HANA is a memory resident database Hardware vendor certification required for appliance and TDI
- Data Savepoints - Random large block access, mostly write...Read on recovery, restart Log Commits - Sequential small block access, mostly OVERwrite...Read on recovery - replay from Savepoint
- https://global.sap.com/community/ebook/2014-09-02-hana-hardware/enEN/appliances.html#search=cisco&recordid=661 SAP Certifies hardware and filesystems - not Software defined storage
- Cisco Integrated Integrated for SAP Hana (Appliance model) Main use case is for analytics work loads What’s new includes: 40G network speed C240 servers with MapR cluster storage, allows scaling in smaller storage chunks Services are mandatory – Cisco Managed Services where Cisco will fully manage your solution and the customer has the option to opt out. But in so doing then the customer recognizes that the customer is in charge of all the patches and updates Note to PSS: SAP Certifies appliances prior to TDI mode, so configurations on slide 18 and 19 have different storage options (Appliance was a prerequisite certification to TDI which allows traditional enterprise storage
- Today we can run HANA and VORA on the same FI Domain Where your network can be shared for more than one purpose. You can do this based on the TDI architecture. you don’t share the storage or the compute nodes but you can add in more compute for a different application to the network. This allows us to have a flexible resource pool. Now you have C240s that you use for storage or C240s for Hadoop Vora. The HANA side is still dedicated resources for BW and analytics. The non HANA platform can be used for any application.
- UCS C240 Integrated Solution for SAP HANA and Vora. extending the C240 storage pool to include support for multiple HANA workloads, transactional workloads, fewer C240 servers for lower purchase cost, support for dynamic tiering workloads, and support for additional Non-HANA SAP workloads. This configuration runs transactional workloads, storage is based on C240 disk drives. C240 server can be positioned as a storage node or as a application server – in both cases it brings storage closer to server and gives us the ability to have more than one HANA workload in the same node. Ex: You have a lot of C240s and you carve it into 2 separate data storages, one for Hana datastore and one for sybase IQ. THIS IS NOT A REPLACEMENT FOR EMC OR NETAPP, we are simply fulfilling the customer need to move the storage closer to the CPU Note to PSS: Cisco storage had to be certified on SAP Storage PAM in order to run transactional workloads. All SAP customers run transactional workloads while only 1/3 run analytics.
- 24 x 1.8TB = 43.2TB Raw per node
- Linux NFS client on HANA node mounts a Virtual IP address. Initially 2 VIPs per MapR node. NFS Gateway is the MapR "client"
- Our default setup uses two SSD for Boot (mounted inside) and 24 1.8TB HDD per C240 4 sets of 6 disks configured as RAID5 for local data protection. On each RAID5 Disk group one Virtual Disk is defined
- To manage the storage capacity a entity called Volume is created. Each Volume contains at least one Name-Container and one Data-Container with the number of configured replicas for each container.
- Key Message: Cisco’s Integrated Infrastructure with policy-driven programmable infrastructure enables customers to better fit SAP applications into their datacenter. The SAP HANA Appliance is not what customers wanted. It required expensive dedicated resources. It required new processes, and many times broke the customers purchasing and procurement processes. This all resulted in delayed implementation and increased costs. And the irony was SAP HANA was meant to be introduced to avoid those very conditions. The SAP HANA TDI option enables customers and partners to design and deploy SAP HANA in a way that fits better to the Data Center Operations best practices. Cisco is leading this effort in the market. The Cisco UCS solution design can run SAP HANA, SAP Applications and other applications on the same shared infrastructure and fulfill the application requirements based on the programmability and core design of Cisco UCS. This means we can put the SAP HANA, SAP BW, SAP ERP, Microsoft Exchange servers and even Hadoop servers on the same shared infrastructure while providing performance, isolation, security and governance. The introduction of the Application Centric Infrastructure uniquely enables Cisco to deliver infrastructure solutions that delivers on the demands by the application, rather than providing an infrastructure against which an line of business must adapt. SAP recently announced the development of HANA Vora. This is a new capability for Hadoop Spark in memory clusters to work side by side with HANA solutions to deliver unprecedented performance and business insight from structured and unstructured data alike. Cisco UCS is uniquely positioned for this use case because of our shared infrastructure model, and our market leadership position wrt Hadoop and the leading Hadoop vendors. Cisco’s architecture and programmable infrastructure brings together the HANA and Hadoop solutions in a single policy driven solution that can be scaled as needed by the business demand. An excellent way to utilize resources where they are needed, when they are needed. Cisco’s ultimate goal is to define a Software Defined SAP Application Landscape where all applications run on the same components and all definitions on How to use the infrastructure is defined in policies and rules and not locked by the hardware.