Use Case: Secure and Affordable SAP HANA Cloud- Based Solutions. Kevin Knuese, Symmetry SESSION CODE: SM1833

Transcription

1

2 Use Case: Secure and Affordable SAP HANA Cloud- Based Solutions Kevin Knuese, Symmetry SESSION CODE: SM1833

3 LEARNING POINTS There are multiple options, scenarios, and prerequisites when it comes to deploying SAP HANA Migrating to SAP HANA follows a similar course as other OS/DB migrations Interested in SAP HANA, but still have questions; there are Cloud solutions designed for Proof of Concept If cost of infrastructure is a barrier to deploying SAP HANA, a Cloud option may be right for you

4 SAP HANA Cloud-Based Solutions What We ll Cover Why SAP HANA? Technical Requirements for SAP HANA SAP HANA Deployment Options Migrating to SAP HANA Deployment Investment Models Investment Models Example and Comparison Types of Clouds Security in the Private Cloud Wrap Up

6 Why SAP HANA?

7 Why SAP HANA? SAP HANA platform is a flexible, data source agnostic, inmemory data platform that allows customers to analyze large volumes of data in real-time Performance benefits for both data processing and reporting Transactional systems and Analytics systems Future direction of SAP Focus of support Business decisions based on real-time information

9 Technical Requirements for HANA Multiple SAP Notes and Deployment Guides Notes: SAP HANA: Central Note SAP HANA Platform SPS 07 Release Note SAP HANA Database Central Note Release Note for Software Provisioning Manager 1.0 SP Installation Prerequisite Checker Sizing for SAP Suite on HANA Suite on HANA sizing report Inst.Systems based on NetWeaver 7.1 and higher: UNIX

10 Technical Requirements for HANA Multiple SAP Notes and Deployment Guides Notes: Inst. SAP Sys. Based on NW 7.3 and higher: SAP HANA DB, UNIX SAP HANA and SAP NetWeaver AS ABAP on one Server SAP HANA Options: Additional Information Many, many more Master Guide, Server Installation and Upgrade, Client Installation and Upgrade Guide, etc. SAP Roadmaps

11 Technical Requirements for HANA Multiple Use Cases Primary Persistence for SAP NetWeaver Applications SAP Business Suite, BW, CRM, SCM, etc. SAP HANA as Data Mart SAP BW, SAP BObJ, BI Tool Suite, non-sap OLTP system SAP HANA-Based Accelerators Side Car, Single program, Limited portion of data SAP HANA Data Provisioning Loading business data from a source system to SAP HANA SAP HANA as Application and Development Platform SAP HANA Smart Data Access

12 Technical Requirements for HANA Sizing Scenarios for BW on HANA and Suite on HANA are different CPU cores to Memory ratios are different Memory sizing Memory for column store and row store Memory for caches and additional components Disk sizing Disk sizing for data files and log files CPU sizing More memory usually means more CPU cores

13 Technical Requirements for HANA Sizing (continued) Resource requirements (CPU, memory, and disk) Current system measurement (quick estimates) Memory: <db_size>/2 * GB Current db = 2000 GB HANA requires 1250 GB RAM Disk: (((<data_size> + <two_biggest_tables>) / 4) * 1.2) + 25 GB Current db = 2000 GB; two largest tables = 200 GB HANA requires 685 GB disk CPU: SAP recommends a factor of 3 ( ), or 0.2 cores per user ( ) Current db processes are consuming 4 CPU cores HANA would require 12 CPU cores

14 Technical Requirements for HANA Sizing (continued) Resource requirements (CPU, memory, and disk) SAP Strongly recommends using HANA Quick Sizer SAP Certified hardware configurations T-shirt sizing 64 GB, 128 GB, 256 GB, up to 1 TB Scale-up to 6 TB (12 TB) Scale-out to several TB Validation with KPI programs Consider growth

15 Technical Requirements for HANA Deploying SAP and vendor certified equipment Server and Storage Certified installer for HANA server Certified installer for SAP application Validation with KPI programs Deploying virtualized HANA may also be deployed in virtual environments Requirements vary slightly KPI are still the key

16 Technical Requirements for HANA Bottom line Minimum requirements for each segment of environment Certified Hardware CPU, Memory, Disk spindles/iops, Network Operating System for running HANA Specific version and patch level Database Specific version and patch level if migrating to HANA Current SAP version Netweaver 7.1 and up, SPS patch level, Ehp level, Unicode Type of System Suite on HANA, BW on HANA, etc.

17 Technical Requirements for HANA

19 SAP HANA Deployment Options On-Premise Purchase HANA Appliance(s) Deploy within your own data room Repurpose vacated servers In the Cloud Purchase required resources from a Cloud provider Deploy on remote shared infrastructure Extend network to Cloud provider Repurpose vacated servers Flexibility to grow as needed

20 SAP HANA Deployment Options SAP HANA Technical Deployment Options Single Application on One SAP HANA System (SCOS) Multiple Applications on One HANA System (MCOD) Multiple SAP HANA Systems on One Host (MCOS) SAP HANA Multi-tenant Data base Containers SAP HANA System Types SAP HANA with Virtualization

22 Migrating to SAP HANA

23 Migrating to SAP HANA The project will be the same or similar to other OS/DB migrations The flow will look something like the following Perform prerequisite activities Business justification Project planning and timing Identify personnel Notify SAP Goal setting Confirm infrastructure and systems layout Sizing

24 Migrating to SAP HANA The project will be the same or similar to other OS/DB migrations Project Flow (continued) Acquire hardware Identify vendor Validate certification for support from SAP Purchase Acquire software Virtualization software (if utilizing) Operating System Database SAP

25 Migrating to SAP HANA The project will be the same or similar to other OS/DB migrations Project Flow (continued) Deploy hardware Certified configuration Assemble and patch hardware Configure hardware for deployment Acquire certified deployment team SAP consultants Third party consulting firm

26 Migrating to SAP HANA Project Flow (continued) Create Sandbox / Proof of Concept Install operating system for SAP HANA Patch and adjust operating system Install SAP HANA database system Patch and adjust HANA database Install SAP application Patch and adjust SAP application Load/Migrate data Test, tune, validate Release system to power user team for advanced testing Repeat until all programs work properly and are optimized Demonstrate results to business

27 Migrating to SAP HANA Project Flow (continued) Create Quality Assurance / Development systems Follow the exact same routine as with SBX Test, tune, validate, confirm Move to production Create Production system Follow same deployment steps as previous systems Test, tune, validate, confirm Go-Live Reap the benefits of SAP HANA Efficiency through availability of real-time data Less hour glass wait time for users Make more profit

29 Deployment Investment Models On-premise -or- In the Cloud Technical Requirements These are the same Systems version and patch levels Baseline sizing All are based on validation of SAP KPI s SAP HANA Deployment Options These are the same Options available in Cloud that may shorten timeline and risk Financial models may vary (Capital Expense v. Operational Expense) Deployment/Migration process These are mostly the same Options available in Cloud that can shorten timeline and reduce risk

30 Deployment Investment Models On-premise -or- In the Cloud Investment Models Will vary SAP HANA equipment is expensive compared to traditional SAP systems The Cloud offers shared expense for hardware Only have to pay for resources consumed Financial models may vary Capital Expense v. Operational Expense What about growth Additional investment when systems grow In the Cloud, just need to allocate more resources Much less time and money required to process this SAP systems will need to be restarted in either case

31 Deployment Investment Models Quick Cloud Statistics 44% of enterprises considering private clouds (IDC) Cloud computing services will reach that $222.5 billion market by 2015 (Global Industry Analysts) 82% of solution providers expect revenue increase with cloud/saas offerings (CRN State Of The Market) 20% of all businesses will own absolutely no IT assets come 2012 (Gartner)

33 Investment Models (Example) Moving ECC systems to HANA Systems current sizes ECP ECQ ECD Database is 1200 GB Database processes using 4 CPU cores Database is 1200 GB Database processes using 2 CPU cores Database is 420 GB Database process using 2 CPU cores

34 Investment Models (Example) Moving ECC systems to HANA Translated HANA sizing ECP ECQ ECD Memory required = 770 GB RAM Disk required = 439 GB disk CPU cores required = 12 cores Memory required = 770 GB RAM Disk required = 439 GB disk CPU cores required = 6 cores Memory required = 302GB RAM Disk required = 170 GB disk CPU cores required = 6 cores

35 Investment Models (Example) Moving ECC systems to HANA Hardware decision ECP ECQ ECD 1 TB SAP Certified HANA Appliance Shared with ECD 1.5 TB SAP Certified HANA Appliance Virtualized Shared with ECQ 1.5 TB SAP Certified HANA Appliance Virtualized

36 Investment Models (Example) Moving ECC systems to HANA Hardware expense Recent quotes from SAP Hardware Partners (Averaged) Anticipated HW costs ECP 1 TB SAP Certified HANA Appliance $195, ECQ / ECD 1.5 TB SAP Certified HANA Appliance $271, Total hardware investment $467, $12, monthly (36 months)

37 Investment Models (Example) Moving ECC systems to HANA HANA HW deployment expense SAP HANA Certified Implementation (Averaged) Anticipated HW deployment costs ECP Average 45 day to delivery Two to four weeks on floor deployment service $28, (average services cost)

38 Investment Models (Example) Moving ECC systems to HANA HANA HW deployment expense SAP HANA Certified Implementation (Averaged) Anticipated HW deployment costs ECQ / ECD Average 45 day to delivery Two to four weeks on floor deployment service $31, (average services cost) Total hardware deployment cost $60, $1, monthly (36 months)

39 Investment Models (Example) Moving ECC systems to HANA HANA Database installation SAP HANA Certified Implementation (Averaged) Anticipated installation costs ECS (sandbox / proof of concept) Average 1 week to install, test, deliver $6, (average technical installation cost) ECS ready to have data migrated

40 Investment Models (Example) Moving ECC systems to HANA HANA application migration/installation expense SAP HANA Certified Implementation (Averaged) Anticipated migration costs ECS (sandbox / proof of concept / copy of ECP) Average 21 days to delivery technical migration Average 21 days for functional adjustments and tuning $15, (average technical migration cost) $21, (average functional services cost) Total ECS system HANA migration cost $36, $1, monthly (36 months)

41 Investment Models (Example) Moving ECC systems to HANA HANA Database installation SAP HANA Certified Implementation (Averaged) Anticipated installation costs ECQ (quality system) Average 1 week to install, test, deliver $6, (average technical installation cost) ECQ ready to have data migrated

42 Investment Models (Example) Moving ECC systems to HANA HANA application migration/installation expense SAP HANA Certified Implementation (Averaged) Anticipated migration costs ECQ (quality system / copy of ECP) Average 14 days to delivery technical migration Average 14 days for functional adjustments and tuning $11, (average technical migration cost) $14, (average functional services cost) Total ECQ system HANA migration cost $25, $ monthly (36 months)

43 Investment Models (Example) Moving ECC systems to HANA HANA Database installation SAP HANA Certified Implementation (Averaged) Anticipated installation costs ECD (quality system) Average 1 week to install, test, deliver $6, (average technical installation cost) ECD ready to have data migrated

44 Investment Models (Example) Moving ECC systems to HANA HANA application migration/installation expense SAP HANA Certified Implementation (Averaged) Anticipated migration costs ECD (development system / copy of ECD) Average 14 days to delivery technical migration Average 14 days for functional adjustments and tuning $12, (average technical migration cost) $14, (average functional services cost) Total ECD system HANA migration cost $26, $ monthly (36 months)

45 Investment Models (Example) Moving ECC systems to HANA HANA Database installation SAP HANA Certified Implementation (Averaged) Anticipated installation costs ECP (quality system) Average 1 week to install, test, deliver $6, (average technical installation cost) ECP ready to have data migrated

46 Investment Models (Example) Moving ECC systems to HANA HANA application migration/installation expense SAP HANA Certified Implementation (Averaged) Anticipated migration costs ECP (development system / copy of ECP) Average 3 days to delivery technical migration (+ go-live support) Average 3 days for functional adjustments and tuning $15, (average technical migration cost) $15, (average functional services cost) Total ECQ system HANA migration cost $30, $ monthly (36 months)

47 Investment Models (Example) Moving ECC systems to HANA On-Premise HANA migration tally Investment estimates Hardware Hardware HANA DB Migration Migration Systems Acquisition Deployment Deployment Technical Functional ECS 195,912 28,500 6,500 15,000 21,000 ECQ 271,636 31,500 6,500 11,000 14,000 ECD - - 6,500 12,500 14,000 ECP - - 6,500 15,000 15,000 Subtotal 467,548 60,000 26,000 53,500 64,000 Total 671,048

48 Investment Models (Example) Moving ECC systems to HANA On-Premise HANA migration tally Timeline estimates Hardware Hardware HANA DB Migration Migration Time Acquisition Deployment Deployment Technical Functional ECS 45 days 30 days 7 days 21 days 21 days ECQ 45 days 30 days 7 days 14 days 14 days ECD 7 days 14 days 14 days ECP 7 days 3 days 3 days Subtotal 45 days 30 days 28 days 52 days 52 days Total ~ 207 days

49 Investment Models (Example) Business Drivers 5% reduction in expenses can result in up to 45% increase in net income (source: SAPInsider/ASUG/SAP) IT Budgets = 66% for running the business, 19% for growing the business and 15% for transforming the business (source: Gartner) Overall IT mission to do more with less

50 Investment Models (Example) Moving ECC systems to HANA Cloud Based Model Systems current sizes ECP ECQ ECD Database is 1200 GB Database processes using 4 CPU cores Database is 1200 GB Database processes using 2 CPU cores Database is 420 GB Database process using 2 CPU cores

51 Investment Models (Example) Moving ECC systems to HANA Cloud Based Model / Same Translated HANA sizing ECP Memory required = 770 GB RAM Disk required = 439 GB disk CPU cores required = 12 cores ECQ Memory required = 770 GB RAM Disk required = 439 GB disk CPU cores required = 6 cores ECD Memory required = 302 GB RAM Disk required = 170 GB disk CPU cores required = 6 cores

52 Investment Models (Example) Moving ECC systems to HANA Cloud Based Model Hardware decision ECP ECQ ECD 1 TB SAP Certified HANA Appliance Virtualized 1 TB SAP Certified HANA Appliance Virtualized.5 TB SAP Certified HANA Appliance Virtualized

53 Investment Models (Example) Moving ECC systems to HANA Cloud Based Model Hardware No Hardware Acquisition Costs Only acquired necessary resources in the Cloud No Hardware Deployment Costs Already performed by the Cloud Provider Shared and blended across consumers Deployment Moderately Lower Costs for Certified HANA DB Deployment Same Costs for Certified Migrations

54 Investment Models (Example) Moving ECC systems to HANA Cloud Based Model Timeline Shortened Hardware is already in place Fully patched Certified by KPI s No wait time HANA DB Built while source systems are being exported Modeled around preconfigured templates Tuned and tested

55 Investment Models (Example) Moving ECC systems to HANA Cloud HANA migration tally Investment estimates Resource Hardware HANA DB Migration Migration Systems Allocation Deployment Deployment Technical Functional ECS - - 6,500 15,000 21,000 ECQ 101,128-4,500 11,000 14,000 ECD 65,668-4,500 12,500 14,000 ECP 161,543-6,500 15,000 15,000 Subtotal 328,339-22,000 53,500 64,000 Total 467,839

56 Investment Models (Example) Moving ECC systems to HANA Cloud HANA migration tally Timeline estimates Hardware Hardware HANA DB Migration Migration Time Acquisition Deployment Deployment Technical Functional ECS 0 days 0 days 3 days 21 days 21 days ECQ 0 days 0 days 3 days 14 days 14 days ECD 3 days 14 days 14 days ECP 3 days 3 days 3 days Subtotal 0 days 0 days 12 days 52 days 52 days Total ~ 116 days

57 Investment Models (Example) Return on Investment Moving ECC systems to HANA Comparison of HANA On-Premise and HANA in the Cloud Investment Costs Summary HANA On-Premise / In The Cloud Investment HANA On-Premise Investment Total $ 671,048 Monthly Spend $ 18,640 HANA In the Cloud Investment Total $ 467,839 Monthly Spend $ 12,996 Cloud Savings $ 203,209 Monthly Savings $ 5,645

58 Investment Models (Example) Return on Investment Moving ECC systems to HANA Comparison of HANA On-Premise and HANA in the Cloud Time for Deployment Summary HANA On-Premise / In The Cloud Timeline HANA On-Premise Deployment Time 207 days Estimated Number of Months 6.9 HANA In the Cloud Deployment Time 116 days Monthly Spend 3.9

59 Investment Models (Example) Moving ECC systems to HANA Comparison of HANA On-Premise and HANA in the Cloud Advantages of HANA in the Cloud Shorter Time for Deployment Summary Lower Investment Cost Scalable Resources Only pay for what you need Only pay for ECS Sandbox while you are using it Only pay for ECQ when it comes online Don t pay for ECD until it comes online Don t pay for ECP until it comes online Purchase smaller systems until you need to grow resources

61 Types of Clouds SaaS Community Hosted Hybrid PaaS Multi-tenacity IaaS On-demand Elastic Public Utility Computing Private Vertical

62 Types of Clouds Public Cloud A Public Cloud is generally thought of as a place to use computing and storage resources Without capital investment of purchasing physical equipment Without on premise facility requirements to house equipment Usually Self Managed Private Cloud A Private Cloud refers to a structured technical environment that includes computing, storage, and networking resources Better defined as hosting on shared infrastructure Usually includes Managed Services More customer control

63 Types of Clouds Hybrid Cloud A Hybrid Cloud is a combination of systems deployment split between hosted and private cloud resources and equipment Usually includes Managed Services Recommendation for HANA in the Cloud When it comes to ERP solutions like SAP, it is recommended to deploy your systems in a Private Cloud

65 Security in the Private Cloud From the Deployment Options section Private Clouds offer HANA the following ways Single Application on One SAP HANA System (SCOS) Usually for Large systems Special Compliance needs Multiple Applications on One HANA System (MCOD) Single Customer Multiple SAP HANA Systems on One Host (MCOS) Single Customer SAP HANA System Types Variable configurations for Suite on HANA and BW on HANA

66 Security in the Private Cloud From the Deployment Options section Private Clouds offer HANA the following ways SAP HANA with Virtualization Most Common Very Large Equipment Compartmentalized into Private Allocations Separated Memory Allocations Separated CPU Allocations Separated Disk LUNs Multiple Private Virtual Containers on Shared Infrastructure One Customer s Allocations and Virtual Servers are Separated and Unaffected by Any Other Customers Allocations

67 Security in the Private Cloud Customer 1 Customer 2 Customer 3 ECC PROD BI PROD ECC PROD SRM PROD BI PROD APO PROD MPLS Customer 1 Users PORTAL PROD HYPERVISOR SRM PROD DB OS DB OS DB OS WAN Browser VPN Customer 2 Users DISK RAM Cloud Data Center 1 CPU Customer 3 Users

68 Security in the Private Cloud ECC PROD BI PROD PORTAL PROD ECC PROD SRM PROD BI PROD APO PROD SRM PROD DB OS DB OS DB OS HYPERVISOR DISK RAM CPU

69 Security in the Private Cloud From the Deployment Options section Private Clouds generally DO NOT offer HANA the following ways SAP HANA Multi-tenant Data base Containers

70 Security in the Private Cloud Cloud

71 Security in the Private Cloud VPN MPLS T1 DS3

72 Security in the Private Cloud Networking in a Private Cloud Private Clouds offer networking for HANA the following ways Private Networks between Customer and Cloud facility Common types include MPLS, IPSEC VPN tunnels, Other Point-to-Point connections Not recommended to use Public IP addressing without VPN encapsulation Internal Networking within the Private Cloud environment All Customer subnet s are separated by VLANs All subnet s are firewalled between Customer s All subnet s are firewalled between Administration network

73 Security in the Private Cloud Networking in a Private Cloud (continued) Private Clouds offer networking for HANA the following ways SAP Best Practices and Recommendations Follows SAP HANA Security Guide OSS Notes SAP HANA appliance software: Central Security Note SAP HANA content security Reviewed regularly

74 Security in the Private Cloud Systems Access in a Private Cloud Application Access in a Private Clouds Designed to provide defined access to hosted applications Restricted to Customer defined groups Operating System Access Root/Administrative access to the Cloud hosted operating systems are restricted Is available through change management process May effect SLA s Administrative Tools Access No Customer access to infrastructure administrative tools Reports through Customer Portal

75 Security in the Private Cloud SAP HANA Security User Security It is Recommended that you have SAP security experts review and design SAP role based security Deploy and manage SAP security based on a minimized role base defined by business function Component Security SAP software SAP HANA Database OSS Notes SAP HANA appliance software: Central Security Note SAP HANA content security

77 BEST PRACTICES To evaluate potential of moving to SAP HANA, it is recommended that you perform a Proof of Concept first SBX in the Cloud will allow you to visualize changes and improvements before you make a significant financial investment If you plan to move your SAP environment to the Cloud, it is recommended that you select a Private Cloud provider Utilizing private resource containers, private network segmentation, and managed services prevents heartache

78 KEY LEARNINGS There are multiple options, scenarios, and prerequisites when it comes to deploying SAP HANA Migrating to SAP HANA follows a similar course as other OS/DB migrations Interested in SAP HANA, but still have questions; there are Cloud solutions designed for Proof of Concept If cost of infrastructure is a barrier to deploying SAP HANA, a Cloud option may be right for you

79 Contact Info Kevin Knuese Chief Technology Officer Ph: LinkedIn: Symmetry booth# 280

80 STAY INFORMED Follow the ASUGNews team: Tom Chris Craig

81 THANK YOU FOR PARTICIPATING Please provide feedback on this session by completing a short survey via the event mobile application. SESSION CODE: SM1833 For ongoing education on this area of focus, visit