Cloud or On Premise

Chris Kernaghan

Principal Consultant

2

Types of Cloud

Several options exist for deploying SAP Applications

1. On Premise2. Pure Infrastructure as a Service3. Managed Cloud as a Service4. Software as a Service

Important SAP Notes

1380654 - SAP support in public cloud environments

1492000 - General Support Statement for Virtual Environments

3

Deployment stack

Solution stack On Premise Pure IaaS Managed Service Subscription

Applications

Data

Runtime

Middleware

Database

Operating System

Virtualisation

Servers

Storage

Networking

Customer manage

Service Provider manage

Customermanage

Service Provider manage

Customermanage

Service Provider manage

4

Example Simple S/4 HANA LandscapeS4 Landscape DMZ

HANADB/CI

ApplicationServer(s)

Gateway/FioriServer

SLT Server

PIServer

User

OtherSAP GLs

Non-SAP GLs

• Cost Optimised HA/DR• PI assumed in DMZ for interfaces• SLT will be used for replicating

data from SAP and non-SAP Sources

• Gateway/Fiori server required due to additional SAP UI5 development

Example Complex S/4 HANA LandscapeS4 Landscape

HANADB/CI

ApplicationServer(s)

Gateway/FioriServer

SLT Server

User

Internal Network

Other SAPsystems

Non-SAP systems

B.ObjApp tier

B.ObjDatabase

CustomerDMZ

PIServer

• Use of MDC/MCOS to reduce TCO with SLT and B.Obj (Shared workload)

• B.Obj used for reporting directly from S4

6

Hybrid Infrastructure Landscape Scenario

SuccessFactors

Ariba

SAPHanaCloud

Platform

S4 Landscape CustomerDMZ

HANADB/CI

ApplicationServer(s)

Gateway/FioriServer

SLT Server

PIServer

User

Internal Network

Other SAPsystems

Non-SAP systems

SAP Cloud Connector

SAP DataServices

B.ObjApp tier

B.ObjDatabase

7

Commercial and contractual itemsServices • Migration services – how will the provider help you to migrate to their service• Monitoring and alerting – what exactly is monitored and how does that create

action• Full RACI of items – what exactly does the service provide (See Roles and

Responsibilities matrix from SAP HEC)

Business Continuity • Business Continuity services (including DR testing) – what services does the provider

have and how does DR work• Provider certifications – make sure the provider meets your certification

requirements• DNS operation – who controls the DNS addressing• Backup retention periods – does the provider meet your regulatory requirements

Interaction details• Clear billing details• Customer interaction – how does the provider interact with the customer• Service interaction – how does the client interact with the service to determine

operations are optimal• Service Desk integration – how can you track calls and SLAs

8

On Premise ScenarioSystem landscape design

Pros Cons

Customer Full control CAPEx required

Asset to be deprecated Lack of HANA experience

Leverage existing services Limited flexibility

Minimised RPO/RTO Requires Metro-cluster for cost optimised solution

DC2DC1

HANA HANA (HA/DR)

< 100KM

System Replication (synchronous)

Production

App Servers App Servers

S4 Landscape CustomerDMZ

HANADB/CI

ApplicationServer(s)

Gateway/FioriServer

SLT Server

PIServer

User

Internal Network

Other SAPsystems

Non-SAP systems

9

IaaS scenario – example AWS

9

System landscape designPro Con

Utility Billing Virtualisation limit

Flexible landscape No AMS

HANA experience kept in house Complex HA/DR

Extensive certifications Geographic data constraints

Network complexity

AZ2AZ1

HANA HANA (HA/DR)

< 100KM

System Replication (synchronous)

Production

App Servers App Servers

XaaS S4 Landscape CustomerDMZ

HANADB/CI

ApplicationServer(s)

Gateway/FioriServer

SLT Server

PIServer

User

Internal Network

OtherSAP systems

Non-SAP systems

10

MCaaS Scenario – Example VirtustreamLandscape diagram

Pro Con

Utility Billing 1TB virtualisation limit

Flexible landscape No AMS

HANA experience

Extensive certifications

Simple HA/DR

XaaS S4 Landscape CustomerDMZ

HANADB/CI

ApplicationServer(s)

Gateway/FioriServer

SLT Server

PIServer

User

Internal Network

OtherSAP systems

Non-SAP systems

DC2DC1

HANA HANA (HA/DR)

Storage Replication

Production

App Servers App Servers

11

SaaS Scenario – Example HECLandscape diagram

Pros Cons

Subscription pricing Not as flexible

Full AMS service Longer lead times

Single Contract CR for all changes

Transparent service Limited interaction

HA/DR limitations

SaaS S4 Landscape CustomerDMZ

HANADB/CI

ApplicationServer(s)

Gateway/FioriServer

SLT Server

PIServer

User

Internal Network

OtherSAP systems

Non-SAP systems

DC2DC1

HANA HANA (DR)

HANA (HA)

> 100KM

System Replication (asynchronous)

System Replication (synchronous)

App Servers App Servers

Production

12

Comparison of Cloud providers – Appendix Slide

Public Billing TypeStandard Management

Underlying Technology

Supported O/Ss

HANA Support

Connectivity Model

HEC +1 Partner

Certification level

HP Helion No SubscriptionBare metal to App OpenStack

Suse/RHEL/Windows Yes

VPN/MPLS/Leased Line Yes SAS70 Type III

IBM Softlayer No SubscriptionBare metal to Basis

Virtustream xStream

RHEL/Windows Yes VPN/MPLS Yes SAS70 Type III

IBM CMS No SubscriptionBare metal to App IBM

RHEL/Windows/AIX Yes

VPN/MPLS/Leased Line Yes SAS70 Type III

SAP HEC No SubscriptionBare metal to App Xen

SUSE/Windows Yes VPN/MPLS N/A SAS70 Type III

Amazon AWS Yes Utility Bare metal Modified Xen

RHEL/Suse/Windows Yes

VPN/MPLS (Restricted) No SAS70 Type III

Microsoft Azure Yes Utility Bare metal Hyper-V

RHEL/Suse/Windows Yes VPN No SAS70 Type III

Virtuastream No UtilityBare metal to Basis

Virtustream xStream

RHEL/Suse/Windows Yes VPN/MPLS No SAS70 Type III

Verizon o SubscriptionBare metal to App ???

RHEL/Suse/Windows Yes VPN/MPLS No SAS70 Type III