Sizing and migrating SAP to Azure
A good migration starts with two answers: how big must the target be, and what exists today. The exam tests which tool gives each answer.
Sizing
| Need | Tool |
|---|---|
| Size a new system from users and volumes | SAP Quick Sizer |
| Check usage of an existing host | OS07N in SAP GUI |
| Measure real performance of the SAP system | SAP EarlyWatch Alert from SAP Solution Manager |
| Check if a VM size is certified | SAP Note 1928533 and the certified VM list |
Capacity is expressed in SAPS (SAP Application Performance Standard). Azure VM sizes are published with their SAPS value. HANA VMs must be on the SAP HANA certified list (M-series, Mv2, Mv3, and some E-series for smaller systems).
Discovery
To list every application, interface and system in the SAP estate, use SAP Solution Manager (the landscape and system data). A network inventory or license file is not a complete list of applications. You can also use Azure Migrate to discover servers and dependencies.
Migration methods
| Scenario | Method |
|---|---|
| Same OS and database, lift and shift | Azure Migrate or Azure Site Recovery replicates the VMs |
| Change database or OS (heterogeneous) | SWPM export and import, or DMO |
| Move to SAP HANA with minimal downtime | DMO with System Move, using SUM |
| Very large data, slow network | Azure Data Box or Import/Export for bulk copy, not for the SAP migration itself |
DMO combines the software update, the Unicode conversion and the database migration in one run. With System Move it also moves the system to a new host in Azure.
Azure Site Recovery for VMware
To replicate VMware vSphere VMs, you first deploy a configuration server on-premises (an OVA template that includes the process server and master target). For Hyper-V managed by VMM you use the Site Recovery provider instead.
Load and performance testing
Test before cut-over with tools SAP supports: SAP LoadRunner by Micro Focus for SAP scenarios, and Apache JMeter for web dispatcher or Fiori load. Azure Monitor and Application Insights observe, but they do not generate load.
Exam traps
- Quick Sizer is for new systems. OS07N is for existing hosts.
- Azure Database Migration Service is not the supported way to migrate an SAP database. Use DMO or SWPM.
- Data Box and Import/Export move files, not SAP systems.
- Site Recovery for VMware needs a configuration server, not VMM.
- Azure Monitor does not replace a load-testing tool.
Practice questions
Choose an answer, then review the explanation to check your understanding.
1. You are planning a new SAP landscape on Azure and need a first estimate of the SAPS the system must deliver. The effort must be minimal. What do you use?
Show answer
Answer: A.SAP Quick Sizer turns user and throughput numbers into SAPS and memory for new or greenfield sizing.
2. Before moving an on-premises SAP system, you want to see CPU, memory and network usage of the source host from SAP GUI. Which transaction do you run?
Show answer
Answer: B.OS07N shows operating system and hardware metrics for a host. SM51 lists application servers, and DB12 is for backups.
3. An SAP ECC system on Oracle must move to Azure and be converted to SAP HANA in one step with the shortest downtime. What fits?
Show answer
Answer: C.Database Migration Option (DMO) with System Move in SUM migrates and converts the database to HANA in one run and is supported by SAP.
4. An SAP system on DB2 must move to SQL Server on Azure. Which tool handles the database conversion?
Show answer
Answer: D.Heterogeneous moves use SAP tools (SWPM export/import or DMO). For DB2 to SQL Server, SSMA is the Microsoft conversion tool the exam expects.