Transcript
  • 8/12/2019 1000040_634403289242805000.ppt

    1/33

    SAP Infrastructure

  • 8/12/2019 1000040_634403289242805000.ppt

    2/33

    SAP Infrastructure

    SAP system landscape

    Servers and software

    Physical facilities Data center

    Network infrastructure

    Operating systems and DBMS

    SAP Technical Support Organization

  • 8/12/2019 1000040_634403289242805000.ppt

    3/33

    Course Organization

    Infrastructure

    Organization

    Infrastructure

    SAP

    Technology

    NetWeaverSAP System

    LandscapeData Center TSO

    Basic SAP

    Technology

  • 8/12/2019 1000040_634403289242805000.ppt

    4/33

    The SAP Solution Stack

    Network InfrastructureRack and other Physical Mounting Infrastructure

    Cooling and Conditioning InfrastructurePower Infrastructure

    SAPGUI/Client Components/Browser ComponentsVarious SAP Integration/Touch Points

    WebAS and ITS/IIS ComponentsSAP Application Server LayerSAP Database Server Layer

    SAP Central Instance Layer

    Database-specific Updates/Service Packs/PatchesDatabase Layer

    OS H igh Availability Layer (clustering, etc.)OS & HW-Specific Driver Overlays

    OS Service Packs/PatchesOperating System Layer

    Disk Subsystem HBA LayerDisk Subsystem/SAN Interconnects, Switches, Cables

    Disk Subsystem/SAN Firmware LayerDisk Subsystem/SAN Hardware Layer

    Server FirmwareServer/CPU/RAM/Local Disk Hardware

    The SAP Solution Stack

    Hardware PlatformsFujitsu, HP, IBM, Sun, Dell, etc.

    Operating SystemsAIX, HP-UX, Windows, Solaris,

    Tru64, OS/400, zOS

    Databases Supported

    Oracle, SQL Server, DB2, MySQL,MaxDB

  • 8/12/2019 1000040_634403289242805000.ppt

    5/33

    The SAP Solution Stack Options

    Source: Wikipedia.com

  • 8/12/2019 1000040_634403289242805000.ppt

    6/33

    SAP System Landscape

    The system landscape consists of the servers in theSAP implementation

    A central repository of system information used byall SAP applications to find connection information

    The system landscape includes production servers

    but also many servers that are required to ensurethat the production servers are isolated from theresults of training, development, testing and otherdisasters

  • 8/12/2019 1000040_634403289242805000.ppt

    7/33

    System Landscape Directory

  • 8/12/2019 1000040_634403289242805000.ppt

    8/33

  • 8/12/2019 1000040_634403289242805000.ppt

    9/33

    SLDs for Dev/QA and Production

  • 8/12/2019 1000040_634403289242805000.ppt

    10/33

    SAP System Landscape

    Technical Sandbox

    Used by technical support team to practiceand to perfect configuration and tuning the

    SAP solution stack

    Used to test installations, upgrades, backupand restore processes, hands-on training, etc.

    Should be identical to production system froma functional standpoint

    Business Sandbox

    Used by development team (ABAP, HTML,

    Java, etc)

  • 8/12/2019 1000040_634403289242805000.ppt

    11/33

    SAP System Landscape

    Development System Continuing SAP configuration and/or customization,

    maintenance, and steady-state updates/bug fixes

    Originator of business-process-related configurationand customization changes that will be promoted tothe production system

    Test/QA System Used for integration and testing of business process

    configuration changes Changes created in the development system are

    promoted here and thoroughly tested

    Technical changes are made here if no technicalsandbox exists

  • 8/12/2019 1000040_634403289242805000.ppt

    12/33

    SAP System Landscape

    Training system

    Used for training end users

    Smaller organizations often use the Test/QA server

    Staging system

    Last stop for changes in largest or mission-critical

    implementations

    Functionally and physically identical to productionsystem

    Subjected to stress/load tests and other performance

    tests

  • 8/12/2019 1000040_634403289242805000.ppt

    13/33

    SAP System Landscape

    Production system

    Supports business groups

    Disaster recovery system Used when the costs of downtime exceeds

    cost of maintaining the system

    Identical to the production system but located

    in a different physical location

    Data and processes are replicated from

    production

  • 8/12/2019 1000040_634403289242805000.ppt

    14/33

    SAP System Landscape

    Not all systems are implemented in all

    companies

    A three-system landscape would includedevelopment, test/QA, and production

    systems

    A four-system landscape would include the

    three above plus a DR/Staging system or

    technical sandbox

  • 8/12/2019 1000040_634403289242805000.ppt

    15/33

    SAP One Server

    For small organizations SAP provides

    Multiple Components in One Box (MCOD)

    and the SAP One Server solution

  • 8/12/2019 1000040_634403289242805000.ppt

    16/33

    Course Organization

    Infrastructure

    Organization

    Infrastructure

    SAP

    Technology

    NetWeaverSAP System

    LandscapeData Center TSO

    Basic SAP

    Technology

  • 8/12/2019 1000040_634403289242805000.ppt

    17/33

    Standardization

    Standards are the most important tool for avoidingproblems

    Every aspect of the data center operation should be

    subject to rigorous standards, for example: Server names

    IP addressing

    Disk naming

    Color coding cables Standard hardware and software

    Standard processes

  • 8/12/2019 1000040_634403289242805000.ppt

    18/33

    Data Center Physical Facilities

    Adequate, robust, redundant power facilities

    Environmental controls

    Physical security Well designed rack layout

    Robust network infrastructure

    Cable management systems

  • 8/12/2019 1000040_634403289242805000.ppt

    19/33

    Disaster Recovery and High Availability

  • 8/12/2019 1000040_634403289242805000.ppt

    20/33

    Causes of Downtime

    Application failure

    Operator error

    Operating system failure Hardware failure

    Power outages

    Natural disasters

  • 8/12/2019 1000040_634403289242805000.ppt

    21/33

    High Availability vs. Disaster Recover

    High availability is tactical

    Disaster recovery is strategic

    Both require analysis of total cost of ownership or

    return on investment to determine the amount of

    unplanned downtime that is allowable

    Both add complexity and constrain system

    landscape options Both implemented at all layers of the solution stack

  • 8/12/2019 1000040_634403289242805000.ppt

    22/33

    HA Objectives

    HA is measured in terms of the percentage of

    time that a system is available

    95% - >18 days 99% - 4 days

    99.9% - 9 hours

    99.999% - 5.5 minutes

    95% is easy but will cost people their jobs,

    99.999% (five nines) may be very expensive

  • 8/12/2019 1000040_634403289242805000.ppt

    23/33

    Availability Planning

    HA and DR objectives must be tied to businessrequirements

    Which business processes are critical?

    What is the cost of downtime in critical processes? TCO and ROI drive HA and DR planning

    How much does each option cost and what are thepotential savings?

    Its the responsibility of the solution architect tooversee HA and DR since it affects every level ofthe solution stack

  • 8/12/2019 1000040_634403289242805000.ppt

    24/33

  • 8/12/2019 1000040_634403289242805000.ppt

    25/33

    High Availability

    Ensuring HA boils down to eliminating Single

    Points of Failure (SPOF) in the solution stack

    This involves providing redundancy ofvulnerable components

  • 8/12/2019 1000040_634403289242805000.ppt

    26/33

    Data Center

    UPS and redundant power systems

    Redundant environmental controls

    Redundant network infrastructures

    Disaster Recovery often involves redundant data

    centers that are mirror images

    Often only core business processes are duplicated

    Duplicate data centers are cost justified by usingthem for development as well as pre-upgrade

    testing/staging

  • 8/12/2019 1000040_634403289242805000.ppt

    27/33

    Servers

    Servers should have inside the box

    redundancy of components that are hot

    swappable when possible

    Power supplies

    RAID Drives

    Disk controllers

    CPUs

    Error code correcting (ECC) RAM

  • 8/12/2019 1000040_634403289242805000.ppt

    28/33

    Servers

    Outside the box HA features include server

    clustering

    Clusters are collections of servers andstorage systems that are combined into a

    single virtual system via clustering software

    From the outside, the cluster appears to be a

    single server but internally work loads are

    allocated across all servers

  • 8/12/2019 1000040_634403289242805000.ppt

    29/33

    SAP Components

    Most critical component (besides the database) isthe Central Instance (CI)

    CI resides on one of the basis servers and

    coordinates communication among all SAPcomponents

    The CI should reside on a highly available server

    SAP is cluster aware meaning that each instance of

    the CI in a server cluster maintains state informationon all processes

    If fail-over occurs the new CI can pick up where theold one left off (called active/active clustering)

  • 8/12/2019 1000040_634403289242805000.ppt

    30/33

    HA Switchover Cluster

  • 8/12/2019 1000040_634403289242805000.ppt

    31/33

    Disk Subsystems

    Redundant Arrays of Inexpensive/Independent

    Disks (RAID)

    RAID systems duplicate data across multiple disks

    HA disk controllers

    Battery backed on-board caches

    Storage system clusters with remote data centers

    Storage area networks (SAN) Data networks dedicated to accessing permanent

    storage

  • 8/12/2019 1000040_634403289242805000.ppt

    32/33

    Database Systems

    Most DBMS have features that provide for

    duplicating the database independent of

    other duplication technologies (i.e. RAID)

  • 8/12/2019 1000040_634403289242805000.ppt

    33/33

    Disaster Recovery

    Administrative organization and processes for DRshould be formalized and tested Recovery manager

    Communication liaison

    Technical recovery team

    Review/certification manager

    A DR crash kit should be prepared including allsoftware (application, utilities, etc.), documentation,

    procedures for recovery Documentation becomes critical after a disaster

    Personnel should be thoroughly trained and haveperiod refreshers on procedures


Top Related