HANA Journey at emc

  • 93 views
Uploaded on

 

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
93
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
4
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • Here’s the broad agenda we will cover today. There’s a lot to cover so lets get started with a high level overview of EMC IT.
  • Note: This slide sets the context of where we started - It’s about the change to the business between these time frames which resulted in a change in our IT environment.It is important for customer to understand size, scope, scale, complexity of EMC IT in relation to their own environments – this helps set perspectiveOur EMC IT organization has access to world-class IT technology (and technologists) We have grown as an organization despite our constant budget and unvarying use of physical spaceWe use this timeframe because 2004 was when we started our virtualization journey using VMware ESX technology. We are a very different company from 2004:Our revenues and number of employees have grown dramaticallyWe’ve acquired a lot of companies during this timeframe and added a lot to our product portfolio as well as entered new marketsWe have greatly expanded our business footprint outside of developed economiesThe data that we manage has grown 10x in this periodThis growth has caused added demand on ITWe have 5 data centers: Our two Enterprise Data Centers are in: Hopkinton, MA, Durham NCThe Westboro data center will be decommissioned by the end of 2012Our Regional Data Centers: Cork, Ireland & Santa Clara, CAKEY POINT: In a span of 7 years we have gone from having a 100% physical infrastructure to achieving a remarkable 86% infrastructure virtualization in our IT environment.Along our Journey we have won some awards and recognition
  • So we embarked on an SAP implementation, which took us approx 2 ½ years for our first PROPEL Release.We really stressed alignment of business processes onto the ‘out of the box’ software capabilities, and not over-customizing SAP to support existing business processes. As the Foundation Release was heavy in the Manufacturing and Finance space, this meant a lot of major changes to the business, and thus lots of resources to support, both from the business as well as IT.At the same time, we within IT threw out a challenge of implementing this new ERP system on completely state-of-the art technology, fully virtualized.Mention Hockey Stick! - Scalable infrastructure!
  • Here’s the broad agenda we will cover today. There’s a lot to cover so lets get started with a high level overview of EMC IT.
  • SAP HANA:Business RequirementsHeavy Reporting Needs during EOQ Quote to Order to Ship Business ProcessEliminate performance risk during EOQ – operational reports on ECCMeet critical real time reporting requirementsConsiderationsSAP Suite Accelerator / BW on HANA /SAP HANA Modeling StudioAll Require SAP System Landscape Transfer (SLT) to replicate dataRoad AheadAddressing Real-Time Operations and Analytics HANA Modeling Studio BW / Suite on HANA ?? - Roadmap
  • We started our POC on HANA during Dec 2011. HANA v1.0 SP stack 0.3 Rev 21Right Now we have SPS 0.7 and Rev 7.0Story line – this appliance showed up in our Data Center, and nobody knew what to do with it!! What happens if it ‘goes bump’? How are we supposed to support / maintain this thing?
  • Modeling Approach – Not all complex business processes can be markedAFL (Application Function Libraries)‘Zuite Accelerator’ – this was done to help support business adoptionXS Engine – not an ideal reporting scenario, but was a need here on our Mfg Floors and Security & User management : Granular level access was a challengeSoftware Lifecycle Management -Non-SAP source integration – walk through the issues we had with ‘null’ value in key fields
  • ‘Zuite Accelerator’ – this was done to help support business adoptionXS Engine – is a part of HANA which allows you to build HANA applicationsXS Engine – not an ideal reporting scenario, but was a need here on our Mfg Floors and Non-SAP source integration – walk through the issues we had with ‘null’ value in key fields
  • Show the realtime vs. batch resultsAlso cover how secondary DBCON connection is allowing this to be visible from GUI
  • We, i.e, EMC are the market leaders in Enterprise Backup Solution. As we couldn't deploy any solution in HANA Appliance, we had to be innovative for HANA Backup Solution. For HANA Backup, necessary config files(*.ini) apart from Data and Log Volumes to be taken into consideration.All the above data has to be placed into external file system and from there EMC DataDomain taking care on its own.Streamline backup/recovery and reduce or eliminate tape with EMC Data Domain disk- and network-efficient de-duplication storage systems. One can deploy the same in automatic, ad-hoc or scheduled manner.
  • EMC IT has been running a ‘Sidecar’ implementation of HANA (data replicated from ECC via SLT) for close to a year now. This has been running on an appliance. BPC technically runs on a BW engine, and can be isolated to run as its own application or run on the same platform as a customers’ BW implementation. EMC IT runs BPC as a standalone application, and as a result it has a rather small database (<200 GB). As the business is looking to leverage HANA for BPC, we are positioning vHANA to support this as a single-node deployment, as early as November 2014.We also see opportunities to further enable vHANA to support the initial Dev and QA/Test instances of CRM (2 year project with mid-2015 Go Live).Regarding BW, Nearline Storage enablement is critical path for our BW on HANA migration, thus managing growth on the HANA database longer term. BW databases tend to get very large, so will need to factor in scale out capabilities of vHANA. EMC IT intends to engage in testing scale-out, as well as many of the other expected benefits of VMWare (HA, VMotion, etc).We have started a Twitter feed to start to tell our story as we go through the next few years of further enabling HANA within EMC IT. We have been sharing lessons learned, capabilities enabled, etc. Please feel free to follow us @putitonhana !!
  • Here’s the broad agenda we will cover today. There’s a lot to cover so lets get started with a high level overview of EMC IT.
  • Since HANA Go-Live, we had 3 systems Landscape – DEV, QA/PERF, PROD; all having 4 nodes scale-out HANA appliance.After sometime, we had gone for this option for Development HANA Appliance, mainly due to Optimize the usageOn-demand POC/Project requirementsfor internal HANA Training, Sandbox environmentAnd of course, from cost perspective.So what we have done – we kept the main node intact for HANA Development environment; but de-associate other 3 nodes from the original SAP HANA Development Appliance and used for various requirements as and when demand appears. We have used the same EMC storage at the back-end. For this, we have used SAP Tools and Guides only.
  • To protect the existing SAP implementation, EMC IT has been leveraging an SRDF Star configuration to support replication of mission critical data to an alternate data center. EMC IT now plans to further leverage this configuration to support a zero-data loss solution for HANA. This slide shows how SRDF on VMAX will protect, most notably, the HANA log directories synchronously to a bunker site, where they are then asynchronously replicated to the DR site.At the compute layer, VMware SRM will be used to manage a DR copy of the Virtual HANA nodes. The benefit of this design is that we are not required to run full DR copies of the HANA nodes, thus freeing up the huge memory chunks (associated with HANA) for use on other non-Prod / Testing activities while in normal operations. The HANA nodes will obviously need to be started in the event of a disaster, but RTO and RPO objectives will still be achieved.This configuration will also support a local source for System Copy activities at the DR site.We have also started a new consistency group for HANA, so as we migrate more and more applications to HANA, we have a common consistency point across SAP applications (to support federated refresh).This slide shows an example of using the SRDF Migration option to facilitate the migration of an existing R1 or R2 device to a new device, while reconfiguring the relationships for the change.We built out three separate and repeatable SAN-based tiers-Mission Critical, Business Critical, and Business important-for data replicationThese SAN data replication tiers are designed to meet Service Catalog-defined RTO and RPO service levels for application and data backup and restore, and enable a consistent model for consumption-based chargebackThe mission-critical tier uses EMC SRDF synchronous and asynchronous replication technologies in a star-configured, cascading bunker approach to achieve instantaneous data replication and duplication of data for Zero Data LossAsynchronous replication is used by the SAN-based Business Critical and Business important tiers-to limit maximum data loss to up to 15 minutes for Business Critical applications and up to 24 hours for Business Important applicationsA new SAN-based backup infrastructure eliminates all tape, and uses bi-directional EMC Avamar and EMC Data Domain deduplication at the source and target to reduce online backup size and offsite archivingNotes”
  • EMC IT is positioning HANA as critical piece of SAP deployment. As such, we have a number of initiatives requiring HANA deployments to support. Environment demands are quite high, but we have met challenges around multi-tenancy and availability, not to mention the large costs implied with continuing down the appliance-based model. Furthermore, a core strategy within EMC IT’s implementation was to virtualize wherever possible. We went live in mid-2012 with a fully virtualized environment, and have maintained that thus far, other than the HANA appliances. EMC IT and VMWare have worked together in the past on co-innovation projects, such as enabling RAC on VMWare.The Concept and Goal we’re after is to run SAP, non-SAP, and HANA all on same VBlock!
  • Here’s the broad agenda we will cover today. There’s a lot to cover so lets get started with a high level overview of EMC IT.
  • Many of the skills required to make your HANA implementation a success are not native to a ‘traditional’ SAP implementation. Modeling skills – obviously nothing like ABAP or anything else you have built with Business Objects (i.e., Universes) Security – DB-level security, which your normal SAP Security Admin has not seen before. Also requires close coordination and management with the Modeling team. DBA – definitely nuances to HANA platform that are not seen on a traditional storage-based RDBMS (i.e., indexing is dead). At the end of the day, you’re redefining your entire database platform over time, so a transition needs to occur.

Transcript

  • 1. 1EMC CONFIDENTIAL—INTERNAL USE ONLY Empowering EMC IT with SAP HANA Ajayan Narayanan Senior Director, EMC IT
  • 2. 2EMC CONFIDENTIAL—INTERNAL USE ONLY Agenda  EMC’s IT Transformation  EMC Big Data Overview  HANA Implementation  Application Enablement Roadmap  Environment Management  Wrap Up / Takeaways
  • 3. 3EMC CONFIDENTIAL—INTERNAL USE ONLY INTERNAL USERS IT ENVIRONMENT BUSINESS APPLICATIONS VIRTUALIZATION EMC IT At A Glance 2004 2013 24,000 5 DATA CENTERS, 960 TB STORAGE ~400 60,000 5 DATA CENTERS, ~13 PB STORAGE ~500 Finalist 2,000 Physical Servers ~10,000 OS IMAGES 93% VIRTUALIZED
  • 4. 4EMC CONFIDENTIAL—INTERNAL USE ONLY PROPEL Overview ALIGN PREPARE EXECUTE DELIVER Transform EMC’s Core Business Functions −125 Business Processes Redesigned 18GLOBAL SITES BUSINESS SIMULATION AT 103 TRAINING CLASSES 1,200 BUSINESS SUPER USERS 20 MODULES 65 INTEGRATED APPLICATIONS 470 VIRTUAL HOSTS 40,000+ END USERS 316 GLOBAL SITES 4 FLASH CUTOVER DAY
  • 5. 5EMC CONFIDENTIAL—INTERNAL USE ONLY Agenda  EMC’s IT Transformation  EMC Big Data Overview  HANA Implementation  Application Enablement Roadmap  Environment Management  Wrap Up / Takeaways
  • 6. 6EMC CONFIDENTIAL—INTERNAL USE ONLY Analytics Data Governance Data Sources Big Data Platform Tools & Consulting MASTER DATA MANAGEMENT D A T A QUALITY PLANNING / WHAT-IFPREDICTIVE T E X T ANALYTICS UNSTRUCTUREDSTRUCTURED D A T A INTEGRATION DATA SCIENTIST VISUALIZATION REPORTINGDASHBOARDS COLLABORATION TRAINING SOLUTION DESIGN/ DEVELOPMENT O T H E R STRANSACTIONAL D A T A MACHINE DATA SOCIAL EXTERNAL Big Data Analytics
  • 7. 7EMC CONFIDENTIAL—INTERNAL USE ONLY HINDSIGHT TO INSIGHT Unified Analytical Platform  Business Analytics As A Service  Multi-Platform Data Integration  Seamless Visibility From Aggregated To Transactional Detail Optimized For Consumption  Collaborative Analytic Tools  Advanced Data Scientist Services  Mobile Access Deployed Globally Big Data Reference Architecture Global DW BAaaS GP DB/HD GP DB/HD Tableau Reporting Tool BOBJ Analytic Workspace SAS Visual Analytics Tool OBIEE MSFT Reports GP DB/HDAnalytic Workspace SAS Analytics R + Madlib + Visual Explorer SAP BW Solution Manager GP DB/HDAnalytic Workspace Local Data SFDC Master Data eBus SAP HANA SQL Fire
  • 8. 8EMC CONFIDENTIAL—INTERNAL USE ONLY Agenda  EMC’s IT Transformation  EMC Big Data Overview  HANA Implementation  Application Enablement Roadmap  Environment Management  Wrap Up / Takeaways
  • 9. 9EMC CONFIDENTIAL—INTERNAL USE ONLY How we started Expected Challenges – Long-running operational reports during testing – Concerns about EOQ decision making enablement Let’s see what it can do? Infrastructure – Cisco appliance (4-node scale out), EMC Storage
  • 10. 10EMC CONFIDENTIAL—INTERNAL USE ONLY Lessons Learned Development Lifecycle Management – Leverage Delivery Units to support Migration Control Modeling approach – Graphical Modeling capabilities have some limitations – More complex models need to be augmented with SQLScript functions Security & User Management – Analytical privileges – User Provisioning Software Lifecycle Management – Requires aggressive patch schedule – Enable new capabilities (i.e., AFL, etc)
  • 11. 11EMC CONFIDENTIAL—INTERNAL USE ONLY Capabilities Enabled Custom Accelerator – Using secondary DBCON connection to provide custom HANA report outputs within GUI screen(s) XS Engine – Supporting batch input Integration – Leveraged SLT to support non-SAP source (legacy) DB Single Sign On
  • 12. 12EMC CONFIDENTIAL—INTERNAL USE ONLY Backlog Report – GUI-based access
  • 13. 13EMC CONFIDENTIAL—INTERNAL USE ONLY Log Volume Data Volume Configuration Files (*.ini) HANA Studio Ad-hoc Solution Manager DBA Cockpit Scheduled Linux/SQL Script Cron Job Config Settings Automatic NFS Mount HANA Backup Solution Implementation
  • 14. 14EMC CONFIDENTIAL—INTERNAL USE ONLY Agenda  EMC’s IT Transformation  EMC Big Data Overview  HANA Implementation  Application Enablement Roadmap  Environment Management  Wrap Up / Takeaways
  • 15. 15EMC CONFIDENTIAL—INTERNAL USE ONLY HANA Implementation Scenarios – EMC IT EMC SAP Core Apps ECC HDB ECC BWBPC SCM SUS SRM CRM HANA as a ‘Sidecar’  SAP attempt to gain early market  Replication Support for real time analytics  Development standards / governance  Opportunities: – Operational data models (front-ended by BOBJ tools) – Further leverage Accelerator opportunities? – HANA Live? – Mobility / Dashboarding HANA as a DB Platform  Data Center Readiness (DR, zero data loss)  Build skills and competencies (outside of Basis)  Organization-wide adoption  Capacity management / ILM  Hardware costs: environment expansion  Opportunities: – Reduced overhead (remove replication) – Governance challenges brought back into SAP standard – Virtualize HANA to control costs
  • 16. 16EMC CONFIDENTIAL—INTERNAL USE ONLY HANA Platform Roadmap – EMC IT Next on the horizon… BW • NLS w/ Sybase IQ to control footprint • Operationalize with Scale Out HANA • Embed capabilities of Sidecar into BW, supporting a complete Realtime Analytics Engine S&OP • Enhance statistical forecasting • Planning Virtualized HANA deployment Key accomplishments • Skills building on HANA modeling, DBA, etc • VMWare Virtualized HANA • SAP BPC fully running on Virtualized HANA in Production • Storage-based replication supporting Zero Data Loss solution (for single-node instances) • Continuing to leverage Virtualized HANA to support projects, POC’s, training, etc SAP Go-Live Roadmap Planning • Mission Critical, OLTP support • Mixed workloads CRM • vHANA to support Build & Test phases (2013/14) • Enable HANA capabilities from start of project ECC • Ensure business commitment via previous migrations • Streamline realtime reporting & enhance User Experience PS Go-Live CRM Go-Live BW on HANA Feb’1 4 Sybase IQ (NLS) for BW 2012 2013 2014 2015 vHANA BPC on HANA vHANA CRM on HANA @putitonHANA - Follow EMC IT’s journey on SAP HANA 2016 vHANA S&OP on HANA OLAP Suite (OLTP) Major PROPEL Go Live Operational Data Mart (HANA as a ‘Side Car’) Data replication from ECC
  • 17. 17EMC CONFIDENTIAL—INTERNAL USE ONLY Agenda  EMC’s IT Transformation  EMC Big Data Overview  HANA Implementation  Application Enablement Roadmap  Environment Management  Wrap Up / Takeaways
  • 18. 18EMC CONFIDENTIAL—INTERNAL USE ONLY HANA System Splitting (Multi-tenancy) SAP HANA Development Scale-out Appliance We have created four separate SAP HANA systems  For optimizing the usage  Internal HANA training  On-demand POC requirement  Followed SAP Tools/Guides  Remove host(s)  Redistribution or move tables/data to other hosts  Blocking Memory per system  Sharing same storage SAP HANA NODES in Scale-out Solution  HANA Training  Non-SAP side-car CRM on HANA POC  BPC on HANA POC  BW on HANA POC SAP HANA side-car SAP HANA Development System
  • 19. 19EMC CONFIDENTIAL—INTERNAL USE ONLY /log /data HANA VM HANA VM HANA VM HANA VM /log /data Business Continuity Strategy - vHANA Leverage Multi-Site Remote Replication SRDF/S 10 Miles Bunker Site Franklin, MA Primary Hopkinton, MA Bunker Site Research Triangle Park, NC DR Durham, NC SRDF/S 10 Miles Tier 1 Durham Primary Tier 1 Hopkinton Primary /log /data SRM SRDF/A 600 Miles SRDF/A 600 Miles /log /data HANA VM HANA VM HANA VM HANA VM /log /data /log /data VMAX
  • 20. 20EMC CONFIDENTIAL—INTERNAL USE ONLY Virtualized HANA for EMC IT  EMC IT working on extensive HANA enablement roadmap − Environment demands exceeding supply  Established partnership with EMC IT & VMWare engineering − First to deploy RAC on VMWare (non-SAP, circa 2011) − EMC IT’s SAP implementation to date has been completely virtual DRIVERS & BACKGROUND  Host traditional SAP applications/DBs and HANA-enabled SAP applications on same converged infrastructure − As well as non-SAP apps!  Reduced CAPEX & OPEX hardware costs for HANA deployments − Supportability, Multi-tenancy, Portability, Availability, etc BENEFITS
  • 21. 21EMC CONFIDENTIAL—INTERNAL USE ONLY Agenda  EMC’s IT Transformation  EMC Big Data Overview  HANA Implementation  Application Enablement Roadmap  Environment Management  Wrap Up / Takeaways
  • 22. 22EMC CONFIDENTIAL—INTERNAL USE ONLY Takeaways 1. Invest in Skills Development – Analytics Architecture, Modeling, BASIS, DBA 2. Start Simple – Reports that require a handful of tables, little translation 3. Executive Sponsorship & Commitment 4. Dare to Innovate – ―Best Practices‖ still being developed, don’t be afraid to get creative 5. Plan for Environment Management – Systems per landscape, different applications, etc. @putitonHANA — Follow EMC IT’s journey on SAP HANA
  • 23. 23EMC CONFIDENTIAL—INTERNAL USE ONLY Resources www.EMC.com/emcitproven