How Microsoft Moves Their SAP Landscape into AzureMatt Ordish, Hans ReutterMicrosoft CorporationSession ID 5713

Title• How Microsoft Moves Their SAP Landscape into Azure

Abstract• Microsoft runs a large SAP landscape with more than 500

operating system images either on bare-metal servers or virtual machines. Microsoft is on a path to move a major number of their SAP systems from on-premise to Azure public cloud in order to run a SAP landscape cross premises. This session will report experiences and best practices.

SESSION TITLE

3 KEY LEARNING POINTS

• Understand what Hybrid Cloud is• Understand advantages of Hybrid Cloud especially

for large SAP landscapes• Learn from how Microsoft approached the move

into Hybrid Cloud

• Reduce infrastructure costs for your SAP landscape by aggressively leveraging public cloud infrastructure

RETURN ON INVESTMENT

• Method to evaluate suitability of SAP system for public cloud

• Special thoughts about usage in Azure

BEST PRACTICES

AGENDA

Current SAP Landscape And Infrastructure

Private Cloud On-Premise

Microsoft Azure And SAP

MSIT Deciding For The Right Infrastructure

MSIT Final State

SAP APPLICATIONS AT MICROSOFT

SCM 7.0 EhP2

ERP ECC 6.0 EhP6

GTS 10.1Finance/Corporate Services: Finance, Controlling, Accounting, Enterprise Controlling, Treasury, Project Systems, Financial Services, Real Estate, Corporate Finance Management, InHouse Cash Center

Human Capital Management: Personnel Administration, Benefits, Organizational Management, Talent Management, Personnel Time Management, Payroll

Supply Chain Management: Sales and Distribution,Materials Management, Logistics, Logistics Execution

FI CO AC EC TR

PS FIN RE CFM IHC

PA BN OM TM PT

PY

SD MM LO LEAdd-On: Core Country Version for Central and Eastern Europe

CEE

E-REC ECC 6.0 EhP4

AT RM

E-Recruiting: Applicant Tracking, Requisition Management

TREX: for Candidate Resumes

TREX

CI ECC 6.0 EhP7

RM CA

Convergent Invoicing: Receivables Management, Contract Accounting

IS: Telecommunications

IS-T

CON CUS

Global Trade Services: Compliance Management, Customs Management

TREX: for Sanction Party List Screening

TREX

DP EM

Supply Chain Management: Demand Planning, Event Management, Supply Network Planning

SNP

SMG 7.1 EhP1

CDM MAI

Solution Manager: Custom Development Management Cockpit, Maintenance Optimizer, SAP Support Services

SER

BI/BPC 8.1

BIBusiness Planning&Consolidation,BI

CC 4.0

RTConv.Charging: Direct Billing,Rating

BL

OER NW 7.0 EhP2

STT

Object Event Repository: Secure Track and Trace Scenario

Add-On: Auto-Infrastructure ID

AIN

Others BOBJ Data Services 4.2PI/XI NW 7.3 Process IntegrationDUET Enterprise 2.0Tidal Enterprise SchedulerBSI Tax FactoryVertex Sales TaxEsker Faxing

RealTechOthers

MDG ECC 6.0 EhP7

BPMaster Data Gov:Business Partners

OERDSC NW 7.4 9.2

STT

Object Event Repository: Secure Track and Trace Scenario

Add-On: Auto-Infrastructure ID

AIN

GRC 10.1

GRCGovernance,Risk & Compliance

SAP ServicesAriba NetworkIBP (HCI)

BPC

SAP SYSTEMS PER LANDSCAPE

QuarterlyDevelopment

never refreshed from production

Production

QuarterlyUnit Test

Unit testing

refreshed quarterly

QuarterlyIntegration TestBPRTStress testingDRrefreshed quarterly

Transports

Sandbox

POC, special use as required

refreshed on demand

Transports

Monthly & Prod. supportDevelopment

refreshed quarterly from development

Monthly & Prod. supportUnit Test

Unit testingrefreshed quarterly

Transports

Transports

Transports

SAP SYSTEM LANDSCAPE – 02/2016

XI/PIDUET

Prod.

Sandbox

ERP GTS MDG CFMGRC

SOLOER1DSC

ADSCC

OEROEMSCMBI CI/

RMCABOBJ

DS E-REC

Prod. Support, OOC,& MonthlyDE

V

QA

QuarterlyReleaseSystems

DEV

SIT

UAT

Virtualized

Physical

Azure VM

Quarterly Release & Prod. Support

AGENDA

Current SAP landscape And Infrastructure

Private Cloud On-Premise

Microsoft Azure And SAP

MSIT Deciding For The Right Infrastructure

MSIT Final State

Features for unprecedented virtualization of SAP workloads:• 64-node cluster running up to 4,000 VMs• 64 logical CPUs inside a single VM• 1TB memory in a single VM• Many improvements in the areas of network and storage• Asynchronous VM replication• Live- and storage migration much faster than before• Cluster Aware Update (CAU) on the host cluster• Windows Server 2016 allows node by node upgrade from Windows Server 2012R2 to

Windows server 2016 running private cloud clusters with a mixed Windows OS versions

Details:http://technet.microsoft.com/en-us/library/hh831410.aspxhttp://technet.microsoft.com/en-us/windowsserver/hh968267.aspxhttp://www.microsoft.com/en-us/server-cloud/windows-server/server-virtualization.aspx

WINDOWS SERVER 2012 (R2) HYPER-V

Windows power mode on host server has a similar impact on performance of SAP application instances as if those were deployed on bare-metal• High Performance power mode on host server does benefit performance

significantly• Power mode setting within VMs have no impact

For large VMs (16+ vCPUs) that run in role of dedicated DBMS VMs, it is highly recommended to use Windows Server 2012 R2 as host and guest OS• Introduction of vRSS on host and within VM avoids getting bottlenecked on

one CPU performing the network handling

EXPERIENCES WITH CUSTOMER DEPLOYMENTS

AGENDA

Current SAP landscape And Infrastructure

Private Cloud On-Premise

Microsoft Azure And SAP

Deciding For The Right Infrastructure

MSIT Final State

HYPER SCALE INFRASTRUCTURE IS THE ENABLER

30 Regions Worldwide, 22 Generally Available…

100+ datacenters Top 3 networks in the world 2.5x AWS, 7x Google DC Regions

Central US

Iowa

West USCaliforni

a

East USVirginia

US GovVirginia

North Central US

Illinois

US GovIowa

South Central US

Texas

Brazil SouthSao Paulo

State

West Europe

Netherlands

China North *

BeijingChina

South *Shanghai

Japan EastTokyo,

Saitama

Japan West

OsakaIndia South

Chennai East AsiaHong Kong

SE AsiaSingapo

re

Australia South East

Victoria

Australia EastNew South

Wales

India CentralPune

Canada EastQuebec City

Canada CentralToronto

India West

Mumbai

Germany North East **

Magdeburg

Germany Central **Frankfurt

North EuropeIreland

East US 2

Virginia

United KingdomRegions

United KingdomRegions

US DoD EastTBD

US DoD WestTBD

OperationalAnnounced/Not Operational

* Operated by 21Vianet ** Data Stewardship by Deutsche Telekom

Platform Services

Infrastructure Services

OS/Server Compute Storage

Datacenter Infrastructure (30 Regions, 22 Online)

Web and Mobile

Web Apps

MobileApps

APIManagement

API Apps

Logic Apps

Notification Hubs

Media & CDN

Content DeliveryNetwork (CDN)

Media Services

Integration

BizTalkServices

HybridConnections

Service Bus

StorageQueues

HybridOperations

Backup

StorSimple

Azure SiteRecovery

Import/Export

Networking

Data

SQL Database

DocumentDB

RedisCache Azure

SearchStorageTables

DataWarehouse Azure AD

Health Monitoring

Virtual Network

ExpressRoute

BLOB Storage AzureFiles

PremiumStorage

Virtual Machines

AD PrivilegedIdentity Management

Traffic Manager

AppGateway

OperationalAnalytics

Services ComputeCloud Services

Batch RemoteApp

ServiceFabric

Developer Services

Visual Studio

AppInsights

Azure SDK

VS Online

ContainerService

DNS VPN GatewayLoad Balancer

Domain Services

Analytics & IoT

HDInsight MachineLearning

StreamAnalytics

Data Factory

EventHubs

MobileEngagement

Data Lake

IoT Hub

Data Catalog

Security & Management

Azure ActiveDirectory

Multi-FactorAuthentication

Automation

Portal

Key Vault

Store/Marketplace

VM Image Gallery& VM Depot

Azure ADB2C

Scheduler

AZURE SERVICES

AZURE INFRASTRUCTURE AS A SERVICE (IAAS)

virtual network

data

servicestableHDInsight

blob storage

SQL database

app

services

media

hpcintegration analytics

caching identity service bus

web sitesmobile services

cloud services

infrastructure

services cdnvirtual

machinesvirtual

network vpntraffic

manager

Azure datacenters,your datacenters.

vpn

virtual network

virtual machines

vpn

Two major Azure scenarios so far in regards to SAP• Run parts of SAP landscape or whole SAP landscape on Azure (see details

later)– Have Site-To-Site or Express Route connectivity between Azure and on-premise

datacenter– Extend Active Directory into Azure to achieve network transparency– Deploy SAP systems in Azure VMs

Use Azure as DR site for SAP landscape• Run complete SAP landscape virtualized on-premise• Use Azure Site Recovery Service to replicate SAP application layer VM from

on-premise into Azure• Use DBMS methods to replicate DBMS data into Azure

AZURE SCENARIOS USED BY CUSTOMERS

Microsoft needs to certify Azure infrastructure with SAP:• Certify VM types by conducting SAP SD benchmark• Officially have these benchmarks approved and released by SAP:

http://global.sap.com/campaigns/benchmark/appbm_cloud.epx • Get SAPS throughput numbers or every certified VM noted in SAP Note:

1928533 – SAP Applications on Azure: Supported Products and Azure VM types• Document Reference architecture and deployment processes:

https://azure.microsoft.com/en-us/documentation/articles/virtual-machines-sap-getting-started/

Not all Azure VM types are certified for SAP. Minimum requirements for VMs are:• At least 2 vCPUs• Ratio between memory and vCPU at least 6:1• No Basic SKU supported

CERTIFICATION PROCESS WITH SAP

SAP Note 1928533 – SAP Applications on Azure: Supported Products and Azure VM types

*) The DS series in a 3-tier configuration is only supported with DB data files and DB transaction log files placed on Azure Premium Storage.**) The GS series (2-tier and 3-tier) is only supported with DB data files and DB transaction log files placed on Azure Premium Storage.

AZURE VM SKUS SUPPORTED FOR SAP

VM Type VM Size 2-Tier SAPS 3-Tier SAPSDB Server for 3-Tier Supported

Required Azure Storage for Database

Files A5 2 CPU, 14 GB 1,500 12,000 Yes Standard A6 4 CPU, 28 GB 3,000 25,000 Yes Standard A7 8 CPU, 56 GB 6,000 50,000 Yes Standard A8 / A10 8 CPU, 56 GB 11,000 No Standard A9 / A11 16 CPU, 112 GB 22,000 No Standard D11 2 CPU, 14 GB 2,325 Yes Standard D12 4 CPU, 28 GB 4,650 Yes Standard D13 8 CPU, 56 GB 9,300 No Standard D14 16 CPU, 112 GB 18,600 No Standard DS11* 2 CPU, 14 GB 2,325 Yes Premium DS12* 4 CPU, 28 GB 4,650 48,750 Yes Premium DS13* 8 CPU, 56 GB 9,300 91,050 Yes Premium DS14* 16 CPU, 112 GB 18,600 Yes Premium GS1** 2 CPU, 28 GB 3,580 34,415 Yes Premium GS2** 4 CPU, 56 GB 6,900 78,620 Yes Premium GS3** 8 CPU, 112 GB 11,870 137,520 Yes Premium GS4** 16 CPU, 224 GB 22,680 247,880 Yes Premium GS5** 32 CPU, 448 GB 41,670 Yes Premium

Azure Standard Storage• Working in conjunction with all VM-Series:• Costs of disks based on stored data in disk and not by nominal size of disk

– E.g. Disk defined with 1TB size and filled with 100GB data – charges will be for 100GB only

• Standard Azure disk has a limited IOPS quota of 500 IOPS• Use Striping or Storage Pools to overcome IOPS limits per VHD – IOPS

quota multiply with number of disks engaged in Storage Pool– E.g. build Storage Pool over 4 disks means roughly a limit of 4 x ‘limit of single

disk’– Not really suitable for DBMS storage traffic when SAP system has some

workload– Expect storage write latency like SQL Server Tlog writes being in the 15-40ms

and read latencies also in the double digit space

AZURE STORAGE – STANDARD STORAGE

Azure Premium Storage• Working with DS/GS VM series so far• Provides fast read/write cache that is backed by local SSD drives on compute

node. Up to 1TB disk cache – size dependent on VM type• Three different types of disks (see table)• Moving disks from Standard Azure Storage to Premium Storage that don’t hit

the exact sizes of the three different categories are snapped to next larger category. E.g. a disk defined with 200GB would be categorized as P20 disk

• Charged by nominal size independentof data stored in disk – even pay forempty disks

• Preferred for DBMS layer of SAP deployments

AZURE STORAGE – PREMIUM STORAGE

Guest OS• Windows – certified since May 2014• SUSE Linux – planned for Q2/CY2016• Red Hat Linux – planned after SUSE Linux

DBMS releases• SQL Server• SAP ASE• Oracle (Limited to Windows Guest OS)• MaxDB• IBM DB2

CURRENT MS/SAP AZURE ROADMAP –OS/DBMS

SAP applications• SAP applications based on SAP NetWeaver• SAP HANA Dev Edition through SAP Cloud Appliance Library and/or Azure

Marketplace (http://cal.sap.com )• SAP BusinessObjects – certified. See 2145537 - Support of SAP

BusinessObjects BI platform on Microsoft Azure • SAP HANA Enterprise Edition Roadmap working on it

• Customers can use Azure for non-production systems already• SAP LiveCache (part of SCM) • SAP Content Server • SAP TREX• Hybris – Deployments possible today as pure IaaS

CURRENT MS/SAP AZURE ROADMAP –SAP APPLICATIONS

SAP NETWEAVER CERTIFICATIONS

SAP Solution Guest OS Database VM TypeSAP Business Suite Windows Server;

SUSE Linux Enterprise Server (SLES)

SQL Server; Oracle; DB22; SAP ASE3

A5-A11, D11-D14, DS11-DS14, GS1-GS5

SAP Business All-in-One

Windows Server;SLES

SQL Server; Oracle; DB22; SAP ASE3

A5-A11, D11-D14, DS11-DS14, GS1-GS5

SAP Business Objects (BI)

Windows Server NA A5-A11, D11-D14, DS11-DS14, GS1-GS5

SAP NetWeaver1 Windows Server;SLES

SQL Server, Oracle; DB22; SAP ASE3

A5-A11, D11-D14, DS11-DS14, GS1-GS5

SAP and Microsoft have tested and certified Microsoft Azure IaaS against the same standards as those used for on-premises infrastructure. The table below shows a list of product certified today.

1Only NetWeaver 7.00 and later SAP releases of NetWeaver are supported for deployment in Azure2Oracle Database 11g R2 Patchset 3 (11.2.04 ), Single Instance

3SAP Adaptive Server Enterprise 16

SAP HANA CERTIFICATIONSSAP Solution Supported OS Azure OfferingsSAP HANA Developer Edition(including the HANA client software comprised of SQLODBC, ODBO-Windows only, ODBC, JDBC drivers), HANA studio, and HANA database)1

SUSE LinuxEnterprise Server

(SLES)

A5-A11, D11-D14, DS11-DS14, GS1-GS5

SAP HANA One SLES DS14_v2 (upon general availability)

SAP S/4HANA SLES Controlled Availability for GS52SAP HANA on Azure (Large Instances) upon general availability

SAP Business Suite on HANA (OLTP) SLES SAP HANA on Azure (Large Instances) upon general availability

SAP HANA Platform or Enterprise Edition for SAP BW (OLAP)

SLES SAP HANA on Azure (Large Instances) upon general availability

1Customers can try SAP HANA Developer Edition on Azure using the SAP Cloud Appliance Library.

2Contact your Microsoft or SAP account manager for more information.

Communications through VPN tunnel or ExpressRoute connection

On-Premise AD/DNS extended into Azure

On-Premise and Azure located SAP systems in same domain/AD

Communication between SAP Systems in Azure and on-Premise completely transparent

Every single customer usingSAP on Azure beyond demoor trainings scenario is usingthis setup with VPN/ExpressRoute

Supported for Hybrid andproductive SAP landscape in Azure

SAP DEPLOYMENT IN HYBRID IT SCENARIO

SUPPORTED VS. NOT SUPPORTED

Supported: Distinct Test/Production Systems in different premises

NOT Supported: Application layer and DBMS layer in different ‘locations’

SAP application layer has a Single Point Of Failure (SPOF) with CI/ASCS/SCS that is critical for the complete systemSAP uses Windows Server Failover Cluster (WSFC) to secure their SPOF

Issue: Azure does not support shared disks as necessary for setup of WSFC configurations suitable for SAP CI/ASCS/SCS

Solution: Use 3rd party SIOS Datakeeper to create Windows Server Failover Cluster with Shared Disk: http://azure.microsoft.com/blog/2014/11/11/high-availability-for-a-file-share-using-wsfc-ilb-and-3rd-party-software-sios-datakeeper/

HA FOR SAP DEPLOYMENT IN AZURE

AGENDA

Current SAP landscape And Infrastructure

Private Cloud On-Premise

Microsoft Azure And SAP

MSIT Deciding For The Right Infrastructure

MSIT Final State

STEP 1: ON-PREMISE WITH SOME VM’S

Early 2014: 520 Servers 61% Physical Hardware 39% On-Prem VMs

61%

39%

Physical On-Prem VM Azure

Azure as well as Hyper-V have some restrictions in regards to maximum CPU and memory per VMAzure additionally has some limitations around IOPS per VHD and per VMIn order to decide which systems can be virtualized or moved into Azure, systems need to be categorized in terms of:• CPU resource consumption• Memory consumption• IOPS requirement

The need to categorize all systems in the MSIT SAP Landscape results in a lot of work – but has to be done

CATEGORIZING SYSTEMS

Example CPU Utilization as one of the measures to decide

MOVING TO AZURE AND ON-PREMISE

Disk Score Avg. Disk Transfer/sec1 <=10

2 >10 and <50

3 >=5 and <200

4 >=200 and <1,000

5 >=1,000 and <10,000

6 >=10,000

Frozen Cold Warm Warm Hot Fire

Cold Cold Warm Warm Hot Fire

Warm Warm Warm Warm Hot Fire

Warm Warm Warm Warm Hot Fire

Warm Warm Warm Hot Fire Fire

Hot Hot Hot Hot Fire Fire

Disk Score

1 2 3 4 5 6

CPU Scor

e

1

2

3

4

5

6

CPU Score Total % Proc1 <=2%

2 >2% and <=5%

3 >5% and <=20%

4 >20% and <=70%

5 >70% and <90%

6 >=90%

Server Utilization Index Map Server Utilization to SLA Index

Server Classification by BPU App Lifecycle Disp

Before moving large systems into on-premise virtualization an intense series of tests were conducted together with the Corporate VM operations team – Findings:• VM hosts need to run in high performance power mode

• Severe difference between throughput of single SAP work process when host server was running balanced power mode compared to high performance power mode

• 4 x Intel E5 servers (HP DL560) are used as host hardware• Storage either EMC VMAX (Tiered Storage) or XtremeIO• Largest on-premise VMs up to 32 vCPUs• Maximum memory per on-premise VM of 352GB (11GB/vCPU)

May 2015 to August 2015: migrate to on-premise VMs in combination with datacenter move

MOVING TO VIRTUALIZATION

STEP 2: HYBRID CLOUD VERSION 1

February 2016 9% Physical Hardware 80% On-Prem VMs 11% Azure

9%

80%

11%

Physical On-Prem VM Azure

AGENDA

Current SAP landscape And Infrastructure

Private Cloud On-Premise

Microsoft Azure And SAP

MSIT Deciding For The Right Infrastructure

MSIT Final State

STEP 3: HYBRID CLOUD VERSION 2 (10/16)

XI/PIDUET

Prod.

Sandbox

ERP GTS MDG CFMGRC

SOLOER1DSC

ADSCC

OEROEM

SCMBI CI/RMCA

BOBJ DS E-REC

Prod. Support, OOC,& Monthly DEV

QA

QuarterlyReleaseSystems

DEV

SIT

UAT

VirtualizedPhysical

Azure VM

Quarterly Release & Prod. Support

STEP 3: HYBRID CLOUD VERSION 2

October 2016 1% Physical Hardware 64% On-Prem VMs

Production systems Pre-production/DR systems Very large Non-Prod

systems 35% Azure

Development systems Sandbox systems Unit test systems Some small production

systems

1%

64%

35%

Physical On-Prem VM Azure

On-premise (Physical and VM’s)• Production systems with very high load and very

high performance requirements• Systems required to co-locate with on-premise

systems• DR systems for production on-premise systems• Physical servers: 5 DB servers for ERP system

Azure• All other systems

STEP 4: FINAL HYBRID STATE

• We are leveraging our own MSIT supported Azure subscription and own ExpressRoute connectivity.

• VM provisioning and storage design done by Basis team SAP Basis team needed to ramp-up knowledge on Azure IaaS

• Moving to ARM template• All VMs are 2 the Azure regions: Non-prod in one, production in the other• Re-evaluate system location in hybrid cloud as part of capacity management • Plans for DR for production systems in Azure similar to on-premise solution

(Do not rely on Azure DR failover, due to requirements to do business initiated failovers independently)

• “Snoozing” of Azure VM’s if not required (e.g. weekends, holidays)• Build out new environments according to real needs, not future

expectation. Grow environment over time as requirements change.

AZURE – HOW?

CLOSING

FOLLOW US

Thank you for your time

Follow us on at @ASUG365