Planning for Migrating SAP Workloads to Azure

By Ashwin Venugopal -

 



Strategies for Migrating SAP systems to Microsoft Azure

Generally, all the enterprises have their own SAP systems for business function such as Enterprise Resource Planning (ERP), global trade, Business Intelligence (BI), and others; with their environments like sandbox, development, test as well as production.

Horizontal strategy

It can help you to start from the bottom of the stack as it's a safe way to experiment as well as gain experience with Azure and it can also be used while redefining your operational, deployment, and approval processes. This strategy works as follows:

  • To limit risk, you should start with low-impact sandbox or training systems. If something goes wrong, there's very little danger of affecting many users or mission-critical business functions. 

  • After that, as you gain experience with running, hosting, and administering SAP systems in Azure, you can apply this knowledge to the next layer of systems up the stack.

  • For each layer, you have to estimate costs, potential money saved, performance, and optimization potential and adjust if needed.

Vertical strategy

Vertical strategy with low-risk systems in parallel to the horizontal strategy can be used to gain experience from production systems on Azure which also provides a chance to adjust internal processes for Azure and train team members. This strategy works as follows:

  • Look at the impact on cost, customers, Service Level Agreements (SLA), & legal requirements- Firstly, move systems that have lower risk- the governance, risk, and compliance systems and then the Object Event Repository (OER) system. After that you can move the higher risk ones, like BI, and ERP.

  • When you have a new SAP system, start in Azure by default rather than putting in on-premises & moving it later- OER is a new low-risk system and you can deploy it entirely to Azure end-to-end ( from sandbox all the way up to production) after successfully moving some of the other systems into Azure with the horizontal strategy.

  • Don't move your most critical system first- The last system you must move should be the highest risk and you require the most performance intensive virtual machine SKUs as well as the largest storage.

  • Move standalone systems first- Some systems are often closely joined with one another like ERP and GRP system with lot of synchronous, real-time traffic between the two. But if you want to move ERP to Azure, while keeping GTS on-premises, it will surely affect the performance due to network latency, hence you should move them together.

  • If you have several SAP systems, look for upstream & downstream dependencies fro one SAP system to another, or from SAP to the apps outside the SAP ecosystem. You should also examine the traffic patterns and areas with high sensitivity to latency.

  • If you have tightly connected systems, do a performance analysis to know what effect moving them will have but if there isn't much impact, then you can easily move them separately to Azure (like Business Warehouse independent of ERP); otherwise you have to create migration groups and move them together.

  • In some cases consider waiting- Sometimes you don't want to move certain systems to Azure right away which could be related to sizing requirements, when the processing requirements were so high that the VMs weren't big enough yet. You have to run some tests to ensure that moving these systems isn't going to affect SLAs with customers.  

Migrating to SAP S4HANA from SAP Business Suite

For most of the SAP customers, their migration of SAP HANA to cloud is mainly due to the following factors:
  • End of life first-generation SAP HANA appliances causing customers to re-evaluate their platform.
  • The desire to take advantage of the early value proposition of SAP Business Warehouse (BW) on HANA in a flexible TDI model over traditional databases and later BW/4HANA.

This result in the numerous initial migrations of SAP HANA to Microsoft Azure have focused on SAP BW to take advantage of SAP HANA's in-memory capability for the BW workload. This means that the migration of the BW application to utilize SAP HANA at the database layer, and eventually the more involved migration of BW on HANA to BW/4HANA. 




Comments

Post a Comment

Popular posts from this blog

Query, Visualize, & Monitor Data in Azure Sentinel

By Ashwin Venugopal -
Image
  Azure Sentinel Workbooks Several ready for use templates are provided by the Azure Sentinel that can be used to create your own workbook and then modify them as needed for Contoso. Most of the data connectors it uses to ingest data come with their own workbooks, but better insight can be obtained by simply looking into the data that is being ingested by using tables and visualizations, including bar and pie charts. You can also make your own workbook easily by using this data from the beginning instead of using the predefined templates. Workbook Page You can easily access the workbook page from the Azure Sentinel from the navigation pane which consists of the: Workbook header- You can add a new workbook and review the saved workbooks as well as templates that are available on the workbook page. Templates section- You can access existing workbook templates on the Templates tab. You can save some of the workbooks for quick access and they will appear on the My Workbooks tab.  From the
Read more

Planning for Implementing SAP Solutions on Azure (Part 2 of 5)

By Ashwin Venugopal -
Image
  To read part 1 please click  here To read part 3 please click  here To read part 4 please click  here To read part 5 please click  here Load Balancing The load balancer uses probe ports to determine as well as route the traffic to an active DBMS node, but of there's any failover then the most common SAP application architecture can automatically reconnect against the private virtual IP address without the need for the SAP application to reconfigure it, while the load balancer redirect the traffic against the private virtual IP address without any need for the SAP application to reconfigure. The loaf balancer also offers an option of DirectServerReturn which if configured, can help in directing the traffic from the DBMS VM to the SAP application layer directly to the application layer without routing through the load balancer. But, if it isn't configured, then the return traffic to the SAP application layer is routed through the load balancer. You can also use Azure Load Balan
Read more

Work with String Data Using KQL Statements

By Ashwin Venugopal -
Image
  Extract Data from Unstructured String Fields Unstructured string fields often contains the Security log data and requires parsing to extract data. There are multiple ways of pulling information from string fields in KQL and the two primary operators used are extract and parse.  Extract It gets a match for a regular expression from a text string. You can convert the extracted substring to the indicated type.  Arguments regex- A regular expression. captureGroup- A positive int constant indicating the capture group to extract. 0 stands for the entire match, 1 for the value matched by the first '('parenthesis')' in the regular expression, 2 or more for subsequent parenthesis.  text- A string to search. typeLiteral- An optional type literal. If provided, the extracted substring is converted to this type.  Returns If regex finds a match in text- the substring matched against the indicated capture group captureGroup, optionally converted to typeLiteral. If there's no mat
Read more