1. How Microsoft Moves Their SAP Landscape into Azure Matt Ordish, Hans Reutter Microsoft Corporation
Session ID 5713

2. SESSION TITLE 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.

3. 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

4. RETURN ON INVESTMENT
Reduce infrastructure costs for your SAP landscape by aggressively leveraging public cloud infrastructure

5. BEST PRACTICES
Method to evaluate suitability of SAP system for public cloud
Special thoughts about usage in Azure

6. AgeNDA Current SAP Landscape And Infrastructure
Private Cloud On-Premise
Microsoft Azure And SAP
MSIT Deciding For The Right Infrastructure
MSIT Final State

7. SAP APPLICATIONS AT MICROSOFT
ERP ECC 6.0 EhP6
GTS
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
BI/BPC
Finance/Corporate Services: Finance, Controlling, Accounting, Enterprise Controlling, Treasury, Project Systems, Financial Services, Real Estate, Corporate Finance Management, InHouse Cash Center
Global Trade Services: Compliance Management, Customs Management
Business Planning&Consolidation, BI
BPC BI FI CO AC EC TR
CON
CUS CC PS
FIN RE
CFM
IHC
TREX: for Sanction Party List Screening
Conv.Charging: Direct Billing,Rating
TREX BL RT
Human Capital Management: Personnel Administration, Benefits, Organizational Management, Talent Management, Personnel Time Management, Payroll
SCM EhP2
MDG ECC 6.0 EhP7
OER NW 7.0 EhP2
STT
Object Event Repository: Secure Track and Trace Scenario
Add-On: Auto-Infrastructure ID
AIN
SMG EhP1
CDM
MAI
Solution Manager: Custom Development Management Cockpit, Maintenance Optimizer, SAP Support Services
SER PA BN OM TM PT
Supply Chain Management: Demand Planning, Event Management, Supply Network Planning
Master Data Gov: Business Partners
Supply Chain Management: Sales and Distribution, Materials Management, Logistics, Logistics Execution PY BP SD MM LO LE
OERDSC NW
STT
Object Event Repository: Secure Track and Trace Scenario
Add-On: Auto-Infrastructure ID
AIN DP EM
Add-On: Core Country Version for Central and Eastern Europe
CEE
SNP
Others
BOBJ Data Services 4.2
Vertex Sales Tax
PI/XI NW 7.3 Process Integration
Esker Faxing
DUET Enterprise 2.0
RealTech
Tidal Enterprise Scheduler
Others
BSI Tax Factory
GRC
SAP Services
Governance,
Risk & Compliance
Ariba Network
IBP (HCI)
GRC

8. SAP SysteMs Per LANDSCAPE
Sandbox
POC, special use as required
refreshed on demand
Quarterly
Development
never refreshed from production
Quarterly
Unit Test
Unit testing
refreshed quarterly
Quarterly
Integration Test
BPRT
Stress testing DR
refreshed quarterly
Transports
Transports
Transports
Production
Monthly & Prod. support
Development
refreshed quarterly from development
Monthly & Prod. support
Unit Test
Unit testing
refreshed quarterly
Transports
Transports

9. SAP System Landscape – 02/2016
Physical
Virtualized
Azure VM
BOBJ DS
CI/ RMCA
MDG
CFM
ADS
ERP
GTS BI
OER 1DSC
OER OEM
SCM
DUET
SOL
E-REC CC
XI/PI
GRC
Prod.
UAT
Quarterly
Release
Systems
SIT
DEV
Quarterly Release
& Prod. Support
Prod.
Support, OOC,
& Monthly QA
DEV
Sandbox

10. AgeNDA Current SAP landscape And Infrastructure
Private Cloud On-Premise
Microsoft Azure And SAP
MSIT Deciding For The Right Infrastructure
MSIT Final State

11. WINDOWS SERVER 2012 (R2) Hyper-V
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:

12. EXPERIENCES WITH CUSTOMER DEPLOYMENTS
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

13. AgeNDA Current SAP landscape And Infrastructure
Private Cloud On-Premise
Microsoft Azure And SAP
Deciding For The Right Infrastructure
MSIT Final State

14. HYPER SCALE INFRASTRUCTURE IS THE ENABLER
30 Regions Worldwide, 22 Generally Available…
North Central US
Illinois
United Kingdom
Regions
United Kingdom
Regions
West Europe
Netherlands
Canada Central
Toronto
Central US
Iowa
Canada East
Quebec City
Germany North East **
Magdeburg
China North *
Beijing
US Gov
Iowa
US DoD West
TBD
North Europe
Ireland
Germany Central **
Frankfurt
Japan East
Tokyo, Saitama
China South *
Shanghai
East US
Virginia
West US
California
India Central
Pune
Japan West
Osaka
East US 2
Virginia
US Gov
Virginia
India West
Mumbai
India South
Chennai
South Central US
Texas
US DoD East
TBD
East Asia
Hong Kong
SE Asia
Singapore
Australia East
New South Wales
Brazil South
Sao Paulo State
Australia South East
Victoria
100+ datacenters
Top 3 networks in the world
2.5x AWS, 7x Google DC Regions
Operational
Announced/Not Operational
* Operated by 21Vianet ** Data Stewardship by Deutsche Telekom

15. AZURE Services Platform Services Security & Management
Infrastructure Services
OS/Server Compute
Storage
Datacenter Infrastructure (30 Regions, 22 Online)
Web and Mobile
Web Apps
Mobile
Apps
API
Management
API Apps
Logic Apps
Notification
Hubs
Media & CDN
Content Delivery
Network (CDN)
Media Services
Integration
BizTalk
Services
Hybrid
Connections
Service Bus
Queues
Operations
Backup
StorSimple
Azure Site
Recovery
Import/Export
Networking
Data
SQL
Database
DocumentDB
Redis
Cache
Azure
Search
Tables
Warehouse
Azure AD
Health Monitoring
Virtual Network
Express
Route
BLOB Storage
Files
Premium
Virtual Machines
AD Privileged
Identity
Traffic Manager
App
Gateway
Operational
Analytics
Services Compute
Cloud
Batch
RemoteApp
Service
Fabric
Developer Services
Visual Studio
Insights
SDK
VS Online
Container
DNS
VPN Gateway
Load Balancer
Domain Services
Analytics & IoT
HDInsight
Machine
Learning
Stream
Factory
Event
Engagement
Lake
IoT Hub
Catalog
Security & Management
Azure Active
Directory
Multi-Factor
Authentication
Automation
Portal
Key Vault
Store/
Marketplace
VM Image Gallery
& VM Depot
B2C
Scheduler

16. AZURE Infrastructure as a Service (IAAS)
Azure datacenters,
your datacenters.
app services
cloud services
caching
identity
service bus
media
virtual machines
virtual network
mobile services
web sites
integration
hpc
analytics
vpn
data services
SQL database
HDInsight
table
blob storage
virtual network
infrastructure services
virtual machines
virtual network
vpn
traffic manager
cdn
vpn

17. Azure Scenarios USED BY CuStomers
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

18. Certification process with SAP
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:
Get SAPS throughput numbers or every certified VM noted in SAP Note: – SAP Applications on Azure: Supported Products and Azure VM types
Document Reference architecture and deployment processes:
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

19. AZURE VM SKUS SUPPORTED FOR SAP
SAP Note – 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.

20. Azure Storage – Standard Storage
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

21. Azure Storage – Premium 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 independent of data stored in disk – even pay for empty disks
Preferred for DBMS layer of SAP deployments

22. Current MS/SAP Azure Roadmap – OS/DBMS
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

23. Current MS/SAP Azure Roadmap – SAP Applications
SAP applications based on SAP NetWeaver
SAP HANA Dev Edition through SAP Cloud Appliance Library and/or Azure Marketplace ( )
SAP BusinessObjects – certified. See 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

24. SAP NetWeaver certifications
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.
SAP Solution
Guest OS
Database
VM Type
SAP 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
SAP Business Objects (BI)
Windows Server NA
SAP NetWeaver1
SQL Server, Oracle; DB22; SAP ASE3
1Only NetWeaver 7.00 and later SAP releases of NetWeaver are supported for deployment in Azure 2Oracle Database 11g R2 Patchset 3 ( ), Single Instance 3SAP Adaptive Server Enterprise 16

25. SAP HANA certifications
SAP Solution
Supported OS
Azure Offerings
SAP HANA Developer Edition (including the HANA client software comprised of SQLODBC, ODBO-Windows only, ODBC, JDBC drivers), HANA studio, and HANA database)1
SUSE Linux Enterprise Server (SLES)
A5-A11, D11-D14, DS11-DS14, GS1-GS5
SAP HANA One
SLES
DS14_v2 (upon general availability)
SAP S/4HANA
Controlled Availability for GS52
SAP HANA on Azure (Large Instances) upon general availability
SAP Business Suite on HANA (OLTP)
SAP HANA Platform or Enterprise Edition for SAP BW (OLAP)
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.

26. SAP Deployment in Hybrid IT scenario
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 using SAP on Azure beyond demo or trainings scenario is using this setup with VPN/ ExpressRoute
Supported for Hybrid and productive SAP landscape in Azure

27. SUPPORTED VS. NOT SUPPORTED
Supported: Distinct Test/Production Systems in different premises
NOT Supported: Application layer and DBMS layer in different ‘locations’

28. HA FOR SAP DEPLOYMENT IN AZURE
SAP application layer has a Single Point Of Failure (SPOF) with CI/ASCS/SCS that is critical for the complete system
SAP 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:

29. AgeNDA Current SAP landscape And Infrastructure
Private Cloud On-Premise
Microsoft Azure And SAP
MSIT Deciding For The Right Infrastructure
MSIT Final State

30. STEP 1: On-Premise with some VM’s
Early 2014: 520 Servers
61% Physical Hardware
39% On-Prem VMs

31. CATEGORIZING SYSTEMS
Azure as well as Hyper-V have some restrictions in regards to maximum CPU and memory per VM
Azure additionally has some limitations around IOPS per VHD and per VM
In 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

32. Moving to Azure and on-Premise
Example CPU Utilization as one of the measures to decide
Server Utilization Index
Map Server Utilization to SLA Index
Server Classification by BPU
App Lifecycle Disp
Disk Score 1 2 3 4 5 6
CPU Score 1 2 3 4 5 6
Frozen
Cold
Warm
Hot
Fire
CPU Score
Total % Proc 1
<=2% 2
>2% and <=5% 3
>5% and <=20% 4
>20% and <=70% 5
>70% and <90% 6
>=90%
Disk Score
Avg. Disk Transfer/sec 1
<=10 2
>10 and <50 3
>=5 and <200 4
>=200 and <1,000 5
>=1,000 and <10,000 6
>=10,000

33. Moving to Virtualization
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

34. Step 2: HYBRID CLOUD Version 1
February 2016
9% Physical Hardware
80% On-Prem VMs
11% Azure

35. AgeNDA Current SAP landscape And Infrastructure
Private Cloud On-Premise
Microsoft Azure And SAP
MSIT Deciding For The Right Infrastructure
MSIT Final State

36. Step 3: Hybrid Cloud Version 2 (10/16)
Physical
Virtualized
Azure VM
BOBJ DS
CI/ RMCA
MDG
CFM
ADS
ERP
GTS BI
OER 1DSC
OER OEM
SCM
DUET
SOL
E-REC CC
XI/PI
GRC
Prod.
UAT
Quarterly
Release
Systems
SIT
DEV
Quarterly Release
& Prod. Support
Prod.
Support, OOC,
& Monthly QA
DEV
Sandbox

37. 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

38. Step 4: Final Hybrid state
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

39. Azure – How?
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.

40. CLOSING

41. FOLLOW US
Thank you for your time
Follow us on