Cisco & MapR bring 3 Superpowers to SAP HANA Deployments

Editor's Notes

• #4: https://commons.wikimedia.org/wiki/File:Spider-Man_-_Mus%C3%A9e_Gr%C3%A9vin.jpg
• #6: 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
• #8: 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
• #10: Unlike typical relational databases, HANA is a memory resident database Hardware vendor certification required for appliance and TDI
• #11: 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
• #12: 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
• #13: 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
• #14: 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.
• #15: 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.
• #16: 24 x 1.8TB = 43.2TB Raw per node
• #18: Linux NFS client on HANA node mounts a Virtual IP address. Initially 2 VIPs per MapR node. NFS Gateway is the MapR "client"
• #23: 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
• #24: 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.
• #26: 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.