SAPonAzureCaseStudyMay2020.pptx

Case Study:
Planning and Sizing

2
Case Study Abstract and Learning Objectives
Abstract
In this workshop, you discover what is involved in deploying SAP HANA on Azure, Migrating
SAP to Azure, and Value of Embrace Microsoft and SAP program for S/4 HANA Customers with
the goal of designing for high availability, disaster recovery as well as supportability.
At the end of this workshop, you will be able to better design and deploy SAP HANA on Azure.
Learning Objectives
 Design core foundation for SAP HANA Workloads on Azure VMs
 Design core foundation for SAP on SQL Servers
 Design Scalable and reliable landscape
 Pricing SAP on Azure Landscape
 S/4 HANA foundation design concepts
 SAP and Microsoft Embrace program and customer centric digital journey
2

3
 Create Azure Pricing
 SAP BW on HANA
 SAP ECC on SQL
 Create detailed Architecture Diagrams
 Create S/4 HANA Migration Plan
 S/4 HANA, SAP Cloud Platform and Azure services integration
3
Summary Requirement

4
Customer Situation
Contoso
 Contoso is a wholesale automotive parts supply company headquartered in Boston, US.
 Contoso has been using SAP ERP for its Finance/Logistics/Analytics systems on the SAP
Business Suite on Windows Server 2008 R2 with a SQL Server 2008 R2 and BW has already
migrated to HANA. The ECC systems have experienced performance and stability issues and the
OS is nearing end of support.
 Contoso Leadership wants to drastically reduce server and storage hardware in their own
datacenters to minimize IT related costs. Contoso already has a number of their non-SAP
systems migrated to Azure. Leadership has asked the IT team to look into the possibility of
migrating its SAP environment to the Cloud as quickly as possible.
 While the Contoso leadership team interested to migrate to cloud they are aware of Microsoft’s
embrace program and would like to use industry best practices used by this program to
advantage of S/4 HANA migration , SAP Cloud Platform and Azure services to create new retail
opportunities
4

5
Customer Situation – continued
Contoso
 Contoso IT has decided to leverage its knowledge of the Microsoft Cloud platform and existing
ExpressRoute connectivity and host its SAP landscape in Azure. The intention is to migrate BW
system and ECC. Once the both systems are in Azure then the IT team will decide on S/4 HANA
adaption, the multi-stage approach is supposed to minimize potential migration risks.
 The SAP systems should be highly available and their performance must be predictable and
consistent. In addition, the management team wants to leverage disaster recovery capabilities
offered by Azure to ensure resiliency of the migrated environment in case the primary region
hosting the new deployment becomes unavailable.
 Before migrating the production environment to the Cloud, Contoso wants to test its new
deployment approach by provisioning training, development, test, and UAT environments in Azure.
5

6
Case Study – Migration/Greenfield
Contoso
 Contoso has a two-part approach to migrate it’s SAP from on premise to the Cloud. Step one is
to migrate BW up to the could first. This will allow Kocha IT to become more familiar with
supporting the environment in the Cloud.
 Kocha IT would like to use the SAP DMO (Database Migration Option) to migrate from ECC on
Oracle/HP-UX to ECC on HANA in the Azure Cloud.
6

7
Customer Needs
Scope : SAP BW on HANA deployment in Azure VMs
 Go-live date : 3 months from today for BW
 Customer requests flexible VM solution within Cloud to accommodate the BW workloads
Sizing:
 Production with latest OS/DB fully certified and supported by SAP
 HANA sizing memory requirement 1.2 TB of RAM, estimate 1.9 TB of RAM in 3 years
 Storage/volume configuration is based on Microsoft guidance
 SAP BW application servers: 15K SAPS
 Certification is NOT required for non-Prod
 QA : HANA database server: 800 GB of RAM
 Dev, Test : HANA database server(s): 256 GB of RAM
7

8
Customer Needs
Scope : SAP ECC deployment in Azure VMs
 Go-live date : 3 months from today
 Customer requests flexible VM solution within Cloud to accommodate the ECC workloads
Sizing:
 SAP: SAP ERP/ECC 6.0
 OS: Windows Server 2008 R2
 DB: SQL Server 2008 R2
 Production APP Server : 8 Cores, 32 GB RAM x 3 nodes
 Production Db Server : 8cores, 32 GB RAM x 1 node
 Application tier SAP : 30,000 SAPS
 Database tier SAPS : 15,000 SAPS
 IOPS (Production DB data files) ; 20,000 IOPS
 Production DB size : 750GB with max growth to 1TB
 SLA : Availability 99.9%, RPO = 15mins, RTO = 2hr
8

9
SAPS Calculations
From the SAP Benchmark Directory, find the closest match to the CPU architecture, database, and operating system:
https://www.sap.com/dmc/exp/2018-benchmark-directory/#/sd
9

10
SAPS Calculations
Benchmark Data:
 24 cores, 48 threads = 12,300 SAPS (assuming 100% CPU utilization)
De-rate the benchmark SAPS calculation to 65% utilization:
 24 cores, 48 threads = 12,300*65% = 7995
Cores to SAPS – Customer System:
 16 cores at 65% utilization = 7995*(2/3) = 5330 SAPS
10

11
Customer
Requirements
Select Azure Compute for
DBMS and Application
11
How to Size SAP Any DB (SQL Server, Oracle, DB2, ASE) on Azure VM

12
Customer Needs
Availability and Backup
 HA solutions need to be proposed for Production, No HA for all Non-Prod
 With HA option, data loss not allowed (zero RPO), no single point of failure, in
case of server/storage issues, auto failover to complete within 10 minutes
 DB log backup taken every 30 minutes
 DB log backup to be kept for 1 day (DB restore to be fast)
 DB full backup every day (night)
 Daily DB full backup to be retained for 1 month
 Monthly DB full backup for 1 year, annual for 3 years
 Use reasonable backup storage in Cloud
 Do BYOL of 3rd party backup solution (e.g. Commvault)
12

13
Azure HANA Backup and Restore
 HANA
 Database backups (full, incremental, or differential backups)
 Transaction log backups
 Options
 Native HANA database and logfile backups to a filesystem (Locally attached or NFS)
 HANA Snapshots (remember to confirm or abandon a data snapshot!)
 Azure storage snapshots (calls HANA Snapshot API) – HANA Storage Snapshot FAQ:
https://launchpad.support.sap.com/#/notes/2039883
 HANA backups through certified partner backup solutions using the backint interface
 Partner Solutions Directory:
https://www.sap.com/dmc/exp/2013_09_adpd/enEN/#/d/partners
 Combination of above options
 Backup size in filesystem
 Determined from table: M_BACKUP_SIZE_ESTIMATIONS
13

14
Azure HANA Backup and Restore – Example
14

15
Enterprise Backup Solutions for LOB applications/SAP on Azure

16
SAP on Azure Backup Solutions

17
Customer Needs
End User Access and System Integrations
 User locations – 300 from US, 50 LATAM, 50 Europe - all through corporate
network and MPLS
 Currently ExpressRoute is set up to Azure East US 2
 User response time needs to be minimized
Management
 Deploy Jumpbox, DNS, patching server, backup server, monitoring
18

18
Unsupported Scenarios
 Running different layers of SAP applications cross-premises. methods.
e.g. running the DBMS layer on-premises, but the SAP application layer
in VMs deployed as Azure VMs or vice versa (*)
(*) Does not apply to scenarios where the latency is within 2 ms
 Some components of an SAP system in Azure and some on-premises
(e.g. splitting instances of the SAP application layer between on-
premises and Azure VMs).
 Distribution of VMs running SAP instances of one system over multiple
Azure Regions.
19

19
Selection Criteria of Azure VMs for SAP
 Not all Azure VM types are certified for SAP
 Minimum requirements for VMs:
 At least 2 vCPUs
 Ratio between memory and vCPU at least 6GB:1vCPU
 Not all Azure VMs qualify
 Other rules for certification of VM SKUs:
 Some of the VM SKUs are exclusively certified with Premium Storage. (e.g. No SAP certification for
G-series, but certification of GS-Series)
 If the largest VM of a series does not provide sufficient results with Standard Storage, we do not
certify any of the VMs of the series. We wait for VM series coming available with Premium Storage.
(e.g. Dv2 series)
 From the SAPS-based sizing standpoint, we are not making any difference between VMs for the
SAP application layer (no significant dependencies on storage interaction) and DBMS VMs
(sensitive to storage latency and throughput)
20

20
Azure Application Planning – Storage
 Document current size
 Collect historical growth rate
 Document bandwidth and IOPS
 Plan storage type based on a combination of:
 Azure VM IO capabilities
 Storage IO capabilities
 Choose multiple disks to maximize throughput
21

21
Azure Application Planning – Network
Regionality
 Optimize user experience by using Azure regional Cloud presence closest
to user base.
 Remember to include any third parties that require connectivity
Review/Create Interface architecture Documentation
 Document how applications will communicate between Azure and on-
premise, including frequency, volumes, and latency sensitivity
(e.g. Sabrix taxware, Vertex, SAP VSI, etc).
 Capture on-premise IP addresses and ports that will connect to Azure
hosted applications (look at SAP gateway registration info).
 Secinfo and reginfo will provide insight if configured properly
22

22
Azure SAP Network Considerations
 The VNet(s) the SAP application is deployed into does not have Internet access.
 The database VMs are running in the same VNet as the application layer.
 The VMs within the VNet have a static allocation of the private IP address.
(Reference article IP address types and allocation methods in Azure)
 Routing restrictions to and from the DBMS VMs are NOT set with firewalls installed
on the local DBMS VMs. Instead traffic routing is defined with Azure Network
Security Groups (NSG)
 For the purpose of separating and isolating traffic to the DBMS VM, assign different
NICs to the VM. Where every NIC has a different IP address and every NIC is
assigned to a different VNet subnet, which again has different NSG rules.
23

24
Azure Monitoring – SAP Extension
For full SAP support (SAP note: 2015553):
 Each SAP application and database must have the Azure Monitoring Extension for SAP
deployed and configured correctly
 Data from Azure Monitoring Extension for SAP is visible in the NetWeaver system
Configuration, required versions, and minimum SP levels:
 Windows: SAP Note 1409604 (Virtualization on Windows: Enhanced monitoring)
 Linux: SAP Note 1102124 (SAPOSCOL on Linux: Enhanced function)
For installation, configuration and troubleshooting, see:
SAP NetWeaver on Microsoft Azure Virtual Machine Services – Deployment Guide and SAP
Note1999351 (Troubleshooting Enhanced Azure Monitoring for SAP)
25

25
SAP on Azure – Huge Variety of Instances
HIGHEST VALUE LARGEST SCALE-UP
Max vCPUs
Max RAM (GiB)
Max Local Storage (GiB)
26

26
(SAPS) Azure VM Options for SAP Applications
SAP Note 1928533 and https://docs.microsoft.com/en-us/azure/virtual-machines/windows/sizes-memory
Red: certification
in roadmap
27

27
Filesystem Requirements
Mountpoint Size (GB)
/sapmnt/SID 30
/usr/sap/SID/SYS 20
/usr/sap/SID/ASCS 5
/usr/sap/trans 100
HA NFS Servers
Mountpoint Size (GB)
/hana/data 3000
/hana/log 1000
/hana/shared 1000
/usr/sap 64
/hana/backup 4000
HANA
28

28
Premium Storage Allocation to Run SAP HANA on Azure
M-Series VM
Enable Write Accelerator https://docs.microsoft.com/en-us/azure/virtual-
machines/linux/how-to-enable-write-accelerator
https://docs.microsoft.com/en-us/azure/virtual-
machines/workloads/sap/hana-vm-operations
Recommended stripe sizes for the RAID 0:
64K or 128K for /hana/data
32K for /hana/log (Only smaller I/O sizes (<=32KiB)
are taking the accelerated path of Write Accelerator)
Set all caching of the disks building the
volumes to None
NOTES:
29

29
Premium Storage KPIs (Costs differ by Region)
**Stripe Premium
Storage Disks to
aggregate IOPS,
Throughput and
Storage Capacity
 Consistent low latency SSD with
predictable throughput
 For high-performance IO-intensive
DB workloads
 Disk performance is dependent on the
disk size, with up to 7,500 IOPS per disk
 Single digit ms latencies
 Supports up to 4 TB blob/disk size
 Stripe up to 64 disks for a total of 256 TB
 Pay for what you provision
 Check Azure VMs for maximum IOPS
Premium Storage
Disk Type
P4 P6 P10 P15 P20 P30 P40 P50
Disk size 32 GB 64 GB 128 GB 256 GB 512 GB
1024 GB
(1 TB)
2048 GB
(2 TB)
4096 GB
(4 TB)
IOPS per disk 120 240 500 1100 2,300 5,000 7,500 7,500
Throughput
per disk
25 MB/s 50 MB/s 100 MB/s 125 MB/s 150 MB/s 200 MB/s 250 MB/s 250 MB/s
30

30
Premium Storage KPIs (Costs differ by Region)
Azure Premium
Storage Account
Single Instance SLA (99.9%)
Availability Set (99.95%)
31

31
SAP HA Architecture
SAP NetWeaver ABAP / Java 7.00 (and higher) – Windows & Linux
(*) ASCS : ABAP SAP
Central Services – part of
SAP application servers
running message/enqueue
service, which is a single
point of failure (SPOF)
SAP Instances in 4 Layers:
 One or more Application Server Instances
(Redundant Components)
• One ASCS Instance (SPOF)
• One File Share Instance (SPOF)
 One Database Instance (SPOF)
AP AP AP
(A)SCS
File Share
…..
DBMS
32

SAP HA Architecture
AS
Virtual machine
Virtual machine
AS
Azure AS
SAP ASCS
SAP <SID>
(A)SCS IP
Azure ILB
(A)SCS
ERS
ERS
Virtual machine Virtual machine
Azure AS
Availability Set
DBMS
HANA
HANA IP
Azure ILB
VHD
HANA System Replication
VHD
Virtual machine
Azure AS
PRIMARY SECONDARY
Availability Set
DRBD
/sapmnt/<SID>
/usr/sap/trans/...
VHD
Highly Available
Linux DRBD
(Software Replication)
VHD
Virtual machine
Availability Set
Virtual machine
33

33
Pricing
 No need to include OS/DB license costs
(Customer will do BYOL separately)
 Do BYOL of 3rd party backup solution (e.g. Commvault)
 ExpressRoute: Start with 500Mbps
 ExpressRoute Additional outbound data transfer: 5TB/month
 Make sure to include MSFT support (= Professional Direct)
C U S T O M E R I S V E R Y C O S T S E N S I T I V E
34

34
Step 1: Create a Bill of Material
Outcome
Design a solution and prepare to present the solution to the target customer audience in a 30-
minute chalk-talk format.
Timeframe
60 minutes
35

35
Preferred solution cost
Service type Custom name Region Description Estimated Cost
Virtual Machines ASCS x 2, SOFS x 2 (Prod) East US 2 4 E2 v3 (2 vCPU(s), 16 GB RAM); Linux – CentOS; 3 year reserved; 4 managed OS disks – P10 $246.79
Virtual Machines Application x 2 (Prod) East US 2 2 E16 v3 (16 vCPU(s), 128 GB RAM); Linux – CentOS; 3 year reserved; 2 managed OS disks – P10 $736.73
Virtual Machines Database x 2 (Prod) East US 2 2 E16 v3 (16 vCPU(s), 128 GB RAM); Linux – CentOS; 3 year reserved; 2 managed OS disks – P10 $736.73
Storage Storage (Database Files) (Prod) East US 2 Managed Disks, Premium, P30 Disk Type 4 Disks $491.52
Storage Storage (t-log) (Prod) East US 2 Managed Disks, Premium, P20 Disk Type 2 Disks $133.12
Virtual Machines Domain Controller x 1 (Prod) East US 2 1 E2 v3 (2 vCPU(s), 16 GB RAM); Linux – CentOS; 3 year reserved; 1 managed OS disks – P10 $61.70
Virtual Machines Backup / SCDPM x 1 (Prod) East US 2 1 E8 v3 (8 vCPU(s), 64 GB RAM); Linux – CentOS; 3 year reserved; 5 managed OS disks – P30 $789.62
Virtual Machines ASCS x 2, SOFS x 2 (DR) West US 2 4 E2 v3 (2 vCPU(s), 16 GB RAM) x 100 Hours; Linux – CentOS; Pay as you go; 4 managed OS disks – P10 $124.88
Virtual Machines Application x 2 (DR) West US 2 2 E4 v3 (4 vCPU(s), 32 GB RAM) x 100 Hours; Linux – CentOS; Pay as you go; 2 managed OS disks – P10 $89.04
Virtual Machines Database x 1 (DR) West US 2 1 E4 v3 (4 vCPU(s), 32 GB RAM); Linux – CentOS; 3 year reserved; 1 managed OS disks – P10 $90.92
Storage Storage (Database files) (DR) West US 2 Managed Disks, Premium, P30 Disk Type 2 Disks $245.76
Storage Storage (t-log) (DR) West US 2 Managed Disks, Premium, P20 Disk Type 1 Disks $66.56
Virtual Machines Domain Controller x 1 (DR) West US 2 1 E2 v3 (2 vCPU(s), 16 GB RAM); Linux – CentOS; 3 year reserved; 1 managed OS disks – P10 $54.42
Virtual Machines Backup / SCDPM x 1 (DR) West US 2 1 E4 v3 (4 vCPU(s), 32 GB RAM) x 100 Hours; Linux – CentOS; Pay as you go; 1 managed OS disks – P10 $44.52
ExpressRoute East US 2 Metered data plan, 500mbps port speed, Zone 1: North America, Europe, 3 TB additional data transfer $366.80
VPN Gateway East US 2 ExpressRoute Gateways type, Standard tier, 732 gateway hour(s), 3 TB, Inter-VNET outbound VPN
gateway type
$246.60
VPN Gateway West US 2 ExpressRoute Gateways type, Standard tier, 732 gateway hour(s), 3 TB, Inter-VNET outbound VPN
gateway type
$246.60
Backup East US 2 1 instance(s) x 30 TB, LRS $1,345.40
Log Analytics East US Standalone tier , 100 GB(s) $230.00
Support Support $0.00
Monthly Total $6,347.71
Annual Total $76,172.51
Microsoft Azure Estimate
Your Estimate
36

36
# Application Prod or Non-Prod
Azure
VM/HW
Type
Data
Center OS
# of CPU
in Azure
RAM in
Azure (GB) SAPS
hourly
rate ($
/hour)
up time
(hours)
per month
1. Azure
Compute
Cost ($ per
month)
Premium
Storage # of
P20 disks
(512GB&2500I
OPS/disk)
Premium
Stoarge
P20 cost
($/disk,
month)
Premium Storage # of
P30 disks
(1024GB&5000IOPS/
disk)
Premium
Stoarge
P30 cost
($/disk,
month)
2. Azure
Storage
Cost ($ per
month)
1 HANA DB Prod GS5 East US 2 SUSE Linux 32 448 41670 7.82 744 5,818 1 73.22 2 135.17 344
2 SAP Application Server Prod DS12 v2 East US 2 Windows 4 28 6680 0.583 744 434 73.22 135.17 -
3 HANA DB QA GS5 East US 2 SUSE Linux 32 448 41670 7.82 744 5,818 1 73.22 2 135.17 344
4 SAP Application Server QA DS12 v2 East US 2 Windows 4 28 6680 0.583 744 434 73.22 135.17 -
1. Azure Compute 12,504 2. Azure Storage 687
3. ExpressRoute (MS) 418
Bandwidth 500Mbps
Premium No
Unlimited No
Additional egress (GB) 5120
Number 1
4. VPN Gateway 141
Type Standard
Hours 744
Number 1
Total Monthly 13,750
S/4HANA, BW on HANA, HANA Enterprise, Side Car –
Single VM 3-tier – Azure cost
37

37
Step 2: Landscape Design
Outcome
Design a solution and prepare to present the solution to the target customer audience in a 30-
minute chalk-talk format.
Timeframe
60 minutes
38

38
Azure Datacenter East US 2
Customer Corporate
Network
Azure Virtual Network #1
GW
Subnet
Subnet #2
Mgmt
HANA Database Server(s) Prod
Subnet #1 – Prod
MPLS
WAN
or
Internet
Backup
Security
Center
OMS Log
Analytics
Auto
mation
Site
Recovery
Storage
Domain
Controller,
Monitoring,
Backup Server,
SAP Router
in VM
4
SAP Application
Server(s) to scale
out when needed
2 3
1
Site to Site VPN or
ExpressRoute
1 nodes x 448GB (RAM)
uptime SLA : 99.9%
2TB SSD Storage
Single VM 3-tier - Components
39

39
Running SAP HANA on Azure VM HA
Azure East US 2 Region
Azure VNET (Hub)
GW
Subnet
Subnet
DMZ
Azure VNET (Spoke – SAP Prod/Non-Prod)
Customer Corporate
Network
Subnet
Shared
Management
Subnet Prod BW AP+DB
Subnet Non- Prod BW AP+DB
Partner
Admin Network
Web
Internet
VPN?
3
2
Internet VPN
or private
connect ?
4
Where to deploy Jumpbox,
Patching, DNS, Backup ?
Subscription
1
Make sure to use
VNET Hub-spoke topology
6 How to deploy VMs for highly available
SAP ASCS and NFS on Linux Clusters ?
How to deploy VMs and allocate storage for
SAP AP Servers and HANA DB (800GB) for QA,
Dev and Test (256GB each) ?
9
How to size
storage to
store backup ?
8
7 How to deploy VMs for SAP AP servers ?
(15k SAPS)
How to deploy highly available HANA DB and
allocate storage for Production (1.2 -> 1.9TB) ?
How to allocate storage for data, log, shared, root
and backup ?
5
40

40
Running SAP HANA on Azure VM HA
Azure East US 2 Region
Azure VNET (Hub)
GW
Subnet
Subnet
DMZ
Azure VNET (Spoke – SAP Prod/Non-Prod)
Customer
Corporate Network
Subnet
Shared
Management
Subnet Prod BW AP+DB
Subnet Non- Prod BW AP+DB
Partner
Admin Network
Web
41

41
Azure Datacenter East US 2
Customer Corporate
Network
Azure Virtual Network #1
GW
Subnet
Subnet #3
Mgmt
HANA Database Server(s) Prod
1
Subnet #2 – DB Prod
2-node x 448GB (RAM)
HANA System Replication
Cluster uptime SLA : 99.95%
2TB SSD Storage
ExpressRoute is
recommended
3
2
Availability Set
MS
EE
MPLS
WAN
Express
Route
Backup
Security
Center
OMS Log
Analytics
Auto
mation
Site
Recovery
Storage
Subnet #1 – AP
Prod
Availability Set
SAP ASCS
Availability Set
SAP AP
Availability Set
NFS Share
Express
Route
Gateway
Highly available
SAP ASCS and NFS
Clusters
uptime SLA 99.95%
VM with HA - Components
42

42
SAP Business Suite, NetWeaver – Azure VM with HA and DR
43

43
SAP Business Suite, NetWeaver – Azure VM with HA and DR
(continued)
44

44
SAP Support Pre-Requisites
Support KB Reference:
https://launchpad.support.sap.com/#/notes/2015553
 The first level is the bare minimum support level which is appropriate if you only require
support from Microsoft for Azure itself. This support offering is called "Professional Direct" and
is described here:
https://azure.microsoft.com/en-us/support/plans/
 If the SAP solution you are running in Azure is based on Windows and/or SQL Server, the
preferred support option is for you to have a "Microsoft Premier Support" contract with
Microsoft so that you have the best enterprise-level support for Azure, Windows and/or SQL
Server. This support offering is described here:
http://www.microsoft.com/en-us/microsoftservices/support.aspx
http://www.microsoft.com/en-us/microsoftservices/premier_support_windows_azure.aspx
45

45
Day 3 : S/4 HANA Consideration
 Create landscape architecture for S/4 HANA on Azure
 Explain design considerations that will be different for S/4 HANA on Azure
 Management team would like you to present available analytical solutions that
can be considered as part of the S/4 HANA on Azure transformation project
46

SAP on Cloud
Cloud Migration and Support Experts
S/4HANA Solution Architecture with HA/DR
46

SAP on Cloud
Cloud Migration and Support Experts
S/4 HANA Bill of Material
Private and confidential material. © KochaSoft 2018 47

48
Day 4: Embrace program
 Create a high-level architecture which incorporates S/4 HANA, SAP Cloud
Platform and Azure IOT services
 Present the value of incorporating Azure services, SAP Cloud Platform and S/4
HANA
47

SAPonAzureCaseStudyMay2020.pptx

More Related Content

Similar to SAPonAzureCaseStudyMay2020.pptx (12)

Recently uploaded (20)

SAPonAzureCaseStudyMay2020.pptx

Editor's Notes