of 44/44
CAS91545 Huge client SAP landscape transformation to SAP HANA on IBM Power Systems with SLES in private cloud Carsten Dieterle IBM Germany [email protected]

CAS91545 Huge client SAP landscape transformation to SAP ... · PDF fileHuge client SAP landscape transformation to SAP HANA ... Program” for selected customers in 3Q 2014 October

  • View
    221

  • Download
    2

Embed Size (px)

Text of CAS91545 Huge client SAP landscape transformation to SAP ... · PDF fileHuge client SAP...

  • CAS91545

    Huge client SAP landscape transformation

    to SAP HANA on IBM Power Systems with

    SLES in private cloud

    Carsten Dieterle

    IBM Germany

    [email protected]

  • 2

    Carsten Dieterle

    Leading SOLAR(SAP Infrastructure SOLution ARchitect)

    Member of the IBM Technical Expert Council (TEC) DACH

    IBM Deutschland GmbH IBM-Allee 171139 EhningenGermany

    Phone/Mobile +49 7034 274 [email protected]

  • Agenda

    SAP HANA on Power Introduction

    IBM Cloud Orchestrator in a cloud environment

    SAP HANA history at client

    Test and Evaluation Phase (TAE)

    SAP HANA on Power Project (Power E880, ESS, ICO)

    next steps (HA / DR setup) and SAP System Replication

    3

  • SAP HANA on IBM Power From Start till To-Date

    4

    History - Development activities

    August 2013

    SAP initiates Product Development Program for HANA on IBM

    Power technology

    December 2013

    HANA code optimized compiled/linked (HANA SPS08,

    SLES11SP2)

    February 2014

    All HANA Servers running, IBM code checked in, full function

    testing commencing, Power 8 optimization agreed

    June 2014

    SaphireNow/Bernd Leukert announces Test and Evaluation

    Program for selected customers in 3Q 2014

    October 2014

    SAP TechEd && d-code/Bjoern Goerke announces HANA on

    POWER SAP Ramp-Up Program beginning 1Q2015

    November, 2014

    BW 7.31+ TEA code ships to customers

    March, 2015:

    SAP Ramp-up opened for customer applications

    July 2015:

    SAP Ramp-up successfully closed

    August, 2015:

    GA SAP HANA on IBM POWER

    December 2015:

    Support for SAP Suite on HANA and

    HANA Platform Edition SPS 11

    May 2016:

    Support for S/4HANA

  • SAP HANA on Power Tailored Data Center Integration

    5

    Solution validation done by SAP and

    partner

    Preconfigured hardware set-up

    Preinstalled software

    Installation needs to be done by customer /

    responsibility of customer

    Customer aligns with the hardware partner on

    individual support mode

    Fast Implementation

    Support fully provided by SAP

    More Flexibility

    Save IT budget and existing investment

    Appliance approach Tailored Data Center approach

  • SAP HANA on IBM Power (Status: 08/2016)

    SAP HANA on IBM Power supports: SAP ERP 6.0 EHP7+8

    SAP SRM 7.0 EHP3+4

    SAP CRM 7.0 EHP3+4

    SAP SCM 7.0 EHP4

    SAP BW 7.31, 7.40, 7.50, BI JAVA 7.40 for SAP HANA

    S/4HANA (native install starting with 1511 SR1 on prem),e.g. S/4HANA 1511 FPS 02, S/4HANA Finance 1605 and S/4 SFinancials 1503

    and a lot of other products on HANA on Power (e.g. BPC 10.1, SAP BO BI 4.1 SP03, CAR 1.0 SPS03, MDG 7.0, Banking 9.0/BA (Bank Analyzer), SolMan 7.2, SLT 2.0, SDI 1.0 SP02, Hybris Commerce / Marketing, etc.)

    Core to Memory ratio (per productive HANA LPAR): higher ratio potentially on individual [email protected]:

    please see SAP Note 1903576 - SAP-HANA-Database: additional main memory in exceptional cases

    BW and other, not exactly specified workload 50 GB per core on E880 (max. 96 cores; at most 4800 GB RAM)

    50 GB per core on E870 (max. 80 cores; at most 4000 GB RAM)

    32 GB per core on E850 (max. 32/48* Cores) and S-models

    SAP Business Suite (SoH: Suite on HANA), S/4HANA, SFINANCIALS, Banking (including SAP Bank Analyzer), SAP

    Solution Manager, SAP Master Data Governance workload 96 GB per core at most 9 TB RAM

    Minimum core count and min. memory per HANA DB LPAR:Production: 4 cores, 128 GB Memory - Non-production: 2 cores, 64 GB Memory

    BW Scale-Up & Scale-Out

    (up to 16x 4800 GB, xfs based

    or SpectrumScale/GPFS based ESS appliance)

    SoH Scale-Up

    http://service.sap.com/sap/support/notes/2218464

    http://service.sap.com/sap/support/notes/2188482

    *) with new models E850 with feature codes EPW5 and EPW6

    6

    http://service.sap.com/sap/support/notes/2218464http://service.sap.com/sap/support/notes/2188482

  • SAP HANA on IBM Power (Status: 08/2016)

    Multiple HANA LPARs supported for production on a single server:

    up to 4 dedicated or 3 dedicated and 1 shared pool

    Support for Clustering Support - HANA BW Scale-out(up to 16 nodes / up to 4800 GB each, xfs or Spectrum Scale/GPFS based ESS appliances)

    HANA Platform Edition (SPS11, SPS12 etc.) availability for POWER (at the same time as with x86)

    Non-Production relaxations of the requirements for SAP HANA on IBM Power Servers

    POWER8 and POWER7+ servers allowed

    No restrictions with regards to the maximum memory per HANA LPAR core

    The minimum core count per HANA LPAR is 2, min. Memory is 64 GB.

    HANA LPARS can be run in a shared processor pool running with a performance penalty

    Standard Network Components are admitted.

    SAP HANA LPARS for test, development and quality assurance systems may run in parallel to

    other LPARs (for SAP HANA or other purposes) on a single physical Power Server as long as

    none of the participating LPARs runs a production SAP HANA system.

    Besides xfs also NFS, GPFS and ext3 filesystems are supported.

    7

  • One (Hybrid) Cloud Orchestration tool for different platforms

    POWER Cloud

    x86 Cloud

    z/VM Cloud

    Storage CloudIBM Cloud Manager

    with OpenStack

    Public Cloud

  • IBM Corporation 9

    IBM Cloud Orchestrator Key Capabilities

    Composable and integrated application development platform

    Pattern Management

    Enabling business transormation

    Self Service Catalog &Orchestration Workflows

    Service Orchestration

    Workload Orchestration

    Infrastructureas a Service

    From a capability point-of-view, IBM Cloud Orchestrator can be represented as a three-tier solution

    Software Defined, Enterprise class, optimized infrastructure

    Infrastructure ManagementNetworkingCompute Storage

    Deploy workloads to multiple virtualization infrastructures and public clouds.

    Configure Compute, Network, Storage resources.

    Automate deployment of whole application, via blueprint

    Composable multi-node patterns

    Automate everything for production-ready

    Workflow engine to automatically configure policies (backup, patching, monitoring)

    Integrate with service management tools

    Self service, multi-tenant platform.

    Public CloudsPrivate Clouds

    7

  • IBM Corporation 10

    Cloud Orchestrator Use Case: Self Service IT Delivery

    Pain Point:

    It takes weeks-months to put a ready-to-run business application system into production with

    many different tools / teams

    LOB creating their shadow IT, by-passing Ops. With no goverance and control

    Customer value:

    Standardization of application infrastructure via multi-tenant catalogbased delivery

    Deliver IT services to LOB in minutes. Same speed as their shadow IT, but in full control.

    Enable choice of best on-premises as well as off-premises clouds: design the service once, deploy

    everywhere

    Cloud Orchestrator Use Case: Self Service IT Delivery

    8

  • SAP and SAP HANA history at client

    11

    Client is using IBM Power servers with Oracle DB and IBM and non IBM storage for a huge number of SAP installations (ca. 500 SAPSIDs)

    Since early 2013 client installed SAP HANA appliances from IBM and HP

    2014: Client installed a SAP BW 4 Node scaleout cluster from IBM

    Client interest about SAP HANA on Power was extremly high, participation in TAE for HoP, installation of HoP in november 2014

    April 2015: end of TAE, Feedback to SAP, RampUp begins and client migrated first SAP SID to HoP

    RfP for SAP HANA infrastructure Q3 / Q4 2016

    HoP installation in a private cloud environment starts in Q1/2016

  • HoP setup from TAE Program @ client: SAP BW on HANA, 1 TB HANA-DB-TDI-Server

    12

    TAE Installation System 8286-42A

    S824 Power8

    1 x 8286-42A

    1024 GB RAM

    24cores @ 3.52 GHz

    4 cores / 8 GB reserved for Dual Vios Setup

    15 cores / 768 GB for SAP HANA

    SLES 11 SP3 with patch

    XIV Gen 3

    2x

    2-p

    ort

    8Gb FC

    attachment

    S824 / PowerVM

    Linux 1024 GB / 24cores

    SAP HANA DB

    Recommended: TDI certified

    SAN Storage

    1Gb-ET

    4-ports

    2* 10 Gb-ET

    4- ports

  • First experiences from Test & Evaluation Program

    Migration from HANA x86 4 Node Cluster 512 GB (3 active, 1 standby)

    to HANA on Power S824 with 1 TB.

    XIV Gen 3 (without SSD's) as a HANA TDI certified storage

    Migration with standard SAP heterogeneous system copy (migration),

    SAPinst / R3Load

    Installation and SAP migration showed no issues

    For these first of a kind installation you need a Linux specialist

    Supporting SAP Solution Architect (Solar) for this case was Carsten

    Dieterle

    13

  • First experiences from Test & Evaluation Program

    14

  • Filesystem layout

    XFS with multipathing

    Minimum of 4 active paths for performance

    Beware of zoning and storage subsystem specifics

    LVM striping required for performance

    Minimum of 4 volumes for each data and log

    Number of volumes should be a multiple of the number of

    active paths

    15

  • Solution: The SAP HANA on Power private Cloud @ client

    14

    Enterprise servers E880

    Compute Cloud

    RHEL

    Linux

    IBM Cloud Ma