SAP workload operational procedures
Standard operating procedures (SOPs) are documented processes for managing a workload. Each SAP workload should have SOPs to govern operations. Without SOPs, teams drift from management best practices, so we recommend a continuous cycle of assessment and health checks for your SAP workload.
Use health checks and assessments
Impact: Operational excellence
Run health checks. We have four Azure SAP (AzSAP) health checks: (1) deployment checklist, (2) inventory checklist, (3) quality checks, and (4) Linux VM OS analyzer. The image below shows how they share a cycle with our Azure SAP assessments. For more information on the health checks, see SAP quality checks.
Figure 1: The cycle of SAP health checks and assessments throughout th journey.
Conduct assessments. We have three SAP assessments: (1) landing zone accelerator (LZA), (2) Azure SAP (AzSAP) deployment management assessment, and (3) the AzSAP Well-architected framework assessment. These assessments are designed for different stages in the SAP workload lifecycle.
The AzSAP Well-architected framework assessment is for operations. It compares your SAP operations against SAP workload best practices. The assessment encourages continuous improvement by building on each previous assessment.
Figure 2: How the Well-architected assessment creates milestones and builds on these milestones over time.
The initial assessment creates a baseline, and the next iteration of assessment uses the previous assessment as the starting point. It will maintain the selections from the last assessment to track and review the design principle. Because the assessment builds on itself, you can track improvements overtime. The assessment is designed for an existing SAP workload in Azure and can assess one or more of the WAF pillars.
We recommend using this SAP assessment to develop and realign the SOPs for your SAP workload. The assessment identifies areas of strength and weakness that allow you to build better SOPs. For more information, see Azure Well-Architected Review.
Monitor the workload
Impact: Operational excellence
Monitoring is the process of collecting, analyzing, and acting on data gathered from an SAP workload. Monitoring provides insights of the health of the workload to compare with an expected baseline. It allows you to know when, where, and why failures occur. A monitoring best practice is to use a common and consistent logging schema that lets you correlate events across systems. The monitoring and diagnostics process has several distinct phases.
Table 1 - Phases of monitoring and diagnostic process
| Phases | Process description |
|---|---|
| Instrumentation | Generating the raw data from application logs, web server logs, the diagnostics built into the Azure platform, and other sources. |
| Collection and storage | Consolidating the data into one place. |
| Analysis and diagnosis | Troubleshooting issues and seeing the overall health. |
| Visualization and alerts | Using data to spot trends or alert your operations team. |
We recommend using Azure Monitor for SAP solutions to drive these processes. Azure Monitor for SAP is an Azure-native monitoring product for SAP landscapes that run on Azure. Azure Monitor for SAP solutions uses specific parts of the Azure Monitor infrastructure to provide insights into the monitoring of SAP Netweaver, SAP HANA, SQL Server & Pacemaker High-Availability deployments on Azure. For more information, see Azure Monitor for SAP Solutions.
Azure Inventory Checks for SAP Workbooks provide a flexible canvas for SAP specific Azure resource deployment and configuration checks with the help of rich visual reports within the Azure portal. It allows you to tap into multiple data sources from across Azure and combine them into unified interactive experiences. It aims at providing customers/partners with an immediately view of Azure Inventory with intelligence to highlight configuration drift to improve the quality of SAP On Azure deployment for operations. For more information, see Azure Inventory Checks for SAP.
Automate workload infrastructure
Impact: Operational excellence
You should use infrastructure as code (IaC) to automate SAP workload deployments with minimal human intervention and build a scalable and consistent SAP workload on Azure. The manual process of creating the required SAP workload resources is slow and allows for errors. Microsoft has a repository of SAP deployment templates that you should use. It’s called the SAP on Azure Deployment Automate Framework. The templates support SAP HANA and NetWeaver with any database on any SAP-supported operating systems.
For more information, see:
Table 2 - Benefits of automated deployments with IaC
| Benefit domain | Automate deployment benefits | Manual deployment disadvantages |
|---|---|---|
| Knowledge | Works immediately after some initial preparation time. Requires little domain knowledge. | Requires specialized knowledge in many domains outside of SAP. |
| Time | Consumes predictable time from 30 minutes to a couple of hours. | Can take much more time depending on the size of the SAP landscape, depending on the size of the SAP landscape. |
| Cost | Makes automated deployments cheap due to less time spent. | Expensive due to more time spent. |
| Testing | Provides templates that include test instrumentation during deployment and migration. | Allows for limited testing. Requires more work to inject tests in the process. |
| Scaling | Allows you to easily scale up, down, and out. Provides new deployment templates. | Takes more time to scale and customize the environment. |
| Standardization | Applies your defined standards with each deployment. | Sometimes leads to unwanted variations in design. |
Next steps
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for