Professional Documents
Culture Documents
Av. Set 1
Azure ILB
SAP Web Dispatchers SAP ASCS
Cluster
Azure ILB
AG Listener
Sync Commit
SAP SQL DB SAP SQL DB
WSFC node 1 WSFC node 2
Azure VNET
DMZ Subnet
Network Security
Group
NG FW NG FW
Web Subnet
Network Security
Group
ExpressRoute
App Subnet
Network Security
Group
Data Subnet
Controller
Group
Architecture of Phased Migration – ASR On-Prem to Azure
Customer Current Datacenter (On-premise) Customer Azure Subscription
OpenText,
PI, NW,
Test/Dev/Prod Data Tier (VMWare, SQL server, single Lumira ***
instance) GRC,
SQL
PaymetrixServer
Log
Shut
` ERP DBShipping
down BO DB, etc
ASR
(Always On
Process
Server
SAN Storage Azure Virtual
Network Marketplace Net
Web Check
Dispatchers Or balancer NAVs
Azure load
Internet Scaler Point
ExpressRout
(Scale) LB FW
(HTTPS)
e
(10Mbps
-1Gbps)
Azure
End users Storage
Azure Site
Recovery
`
SAP NetWeaver on SQL Server + BW on HANA – All in Azure
SIOS Cluster Scale out Azure ILB w/
5 running SAP when 4 3
AV for HA SLA
ASCS HA needed DS13v2
Azure IaaS/VNET (W EU) HANA on Azure Large Instances 7
1
ERP ASCS ERP APP BW, BO,
Azure load
(HA & APP 10Gbps NW 768GB HANA S72
ExpressRoute Prod balancer Azure load Azure load
Scale) balancer
(HA & balancer provided Large Instances
(Cluster)
Scale) by MS
Solution
Large Instances: for production and non-production workloads
Microsoft offers certified SAP HANA capabilities via purpose-built hardware
specifically tuned for SAP HANA.
• SAP HANA instance runs in a non-virtualized environment on
SAP HANA TDI certified hardware in an Azure-certified data center
• SAP HANA is connected to the SAP application tier running on
Azure VMs
• The two environments are connected via Azure ExpressRoute
1 in controlled availability
SCSVM1 SCSVM2
Source Environment (West Europe) Target Environment (North Europe)
VM3
VM2 VM3
Failover
subnet2 subnet3
subnet2 subnet3
vnet1-asr
vnet1
Azure West Europe Azure North Europe
In order to create traditional Recommended HA approach for 99.9% uptime guarantee from 99.95% uptime guarantee from
Windows/SQL Cluster SQL Server in Azure VMs MSFT with Premium disks (no SLA MSFT
(Active/Passive) requires SIOS for standard disks)
DataKeeper to mimic shared drives
in the cloud or Win 2016 Guest
Clustering
Only use this option if required by Additional requirement of load Better storage stamp separation if Requires you to maintain 2 or more
application (i.e. SAP NetWeaver) balancer for virtual host routing you use Managed Disks copies of the same VM
Additional costs incurred in data Easy and quick to configure with Premium Managed Disks protects Protects against Azure system
replication and SIOS licensing pre-built templates in Azure Gallery against IOPS capping upgrades & patches via
update/fault domains
Block-level replication Individual SQL Server Individual file/folder Manual process SQL Server Backup /
and recovery of VMs, instance-level backup capability requires scripting or Recovery for data
currently not jobs on each VM Storage Explorer, can consistent backups
supported w/SIOS DK be automated
Requires recovery vault Backups sent to Requires recovery vault Very quick snapshots Individual file and
Storage Account via that allow “promoting” folder backup /
public URL with GRS snapshots to other recovery
protection, can use environments or
Standard Storage for production
backups
Use for VM DR Use for DB DR Use for VM and app No individual file/folder Available in Azure
DR recovery, full VHD only Marketplace
Azure-to-Azure Can be used to refresh Use for VMs not Requires Storage
replication currently in other environments supported by current Accounts with per-
private preview, from DB backups using ASR A2A snapshot charges
missing full DB restore
functionality
Private cloud to Azure Public cloud to Azure
https://aka.ms/ignite.mobileapp