SAP Operations and Lifecycle Management
Manage SAP lifecycle on Azure with ACSS for ongoing management, system copy and refresh, Azure Automation, Update Manager for OS patching, SAP kernel upgrades, troubleshooting common issues, and exam preparation tips.
Day-2 operations: keeping SAP alive
🔧 Aisha pours her fourth coffee of the day. “We have built it, secured it, monitored it, backed it up, and optimized the costs. Now comes the part that never ends — keeping SAP running, patched, refreshed, and troubleshot. This is where SAP Basis admins earn their reputation.”
Carlos checks the calendar. “We have a system refresh due next week, three OS patches pending, and the SAP kernel upgrade is overdue. Can we automate any of this?”
🔧 Aisha smiles. “Most of it. Let me show you how.”
Think of it like maintaining a fleet of delivery trucks.
You do not just buy the trucks and hope for the best. Every week you check tire pressure and oil (monitoring). Monthly you rotate tires and change filters (patching). Quarterly you refresh the GPS maps (system refresh). Annually you get the full inspection (SAP kernel upgrade). And when a truck breaks down on the highway, you need a troubleshooting checklist — is it fuel, engine, or a flat tire? Operations is the difference between a fleet that runs for years and one that falls apart in months.
ACSS for ongoing management
Azure Center for SAP solutions (from Domain 2) provides ongoing value beyond initial deployment:
- Start/stop SAP systems — one-click start or stop in the correct SAP order (DB, ASCS, app servers)
- Health monitoring — VIS resource shows aggregate health across all SAP components
- Quality checks — continuous validation against best practices catches configuration drift
- Cost insights — see total cost per SAP system, not scattered across individual VMs
🔧 Aisha demonstrates. “When I need to stop the QA system for maintenance, ACSS handles the shutdown order. HANA stops last. When I start it, HANA starts first. No more writing scripts to manage startup sequences.”
System copy and refresh
System copy creates a new SAP system from an existing one. System refresh overwrites a non-production system with production data. Both are critical for keeping test environments current.
Azure approaches:
- Azure Backup restore — restore production HANA to a non-production VM, then post-process (change SID, reset passwords, anonymize data)
- ANF volume clones — create instant writable clones of ANF volumes for fast data copy
- SAP LaMa — automate the entire copy/refresh workflow from the SAP console
- SDAF — deploy fresh infrastructure and restore data using Terraform automation
Key steps after refresh:
- Restore or clone the production database to the target system
- Post-copy processing — change system SID, reset user passwords
- Anonymize or mask sensitive data (GDPR compliance)
- Update connection parameters (hostnames, IPs)
- Verify system health and run smoke tests
Exam tip: Know the refresh workflow
The exam may describe a scenario where the QA team needs current production data. The answer involves HANA backup restore (or ANF clone) to the QA system followed by post-copy processing. Do not forget data anonymization — copying production data with real customer information to a less-secure non-production system is a compliance violation.
Azure Automation for SAP
Azure Automation extends beyond VM snoozing to broader SAP operations:
- Scheduled start/stop — daily schedules for non-production systems
- Pre/post patch scripts — stop SAP services before OS patching, restart after
- Monitoring alerts response — automated remediation runbooks triggered by AMS alerts
- Housekeeping — clean up old snapshots, delete orphaned disks, rotate backup archives
- Integration with SAP — PowerShell or Python runbooks that interact with SAP via RFC or API
Update Manager for OS patching
Azure Update Manager schedules and applies OS patches to SAP VMs:
- Assessment — scan all SAP VMs for missing patches
- Scheduling — define maintenance windows aligned with SAP change calendar
- Staging — patch non-production first (dev, then QA, then pre-prod)
- Production — patch production during the approved maintenance window
- Validation — verify SAP starts successfully after patching
Integration with Azure Automation allows pre-patch scripts (stop SAP) and post-patch scripts (start SAP, run health check).
SAP kernel upgrades
SAP kernel upgrades update the SAP executable layer without changing the database or application configuration:
- Download the new kernel from SAP Software Download Center
- Test in non-production first
- Stop SAP instance, replace kernel files, restart
- Verify system health and run regression tests
- Azure Automation can orchestrate this across multiple systems
Troubleshooting common issues
🔧 Aisha’s phone buzzes — a performance alert. “Here is my troubleshooting checklist for the three most common SAP-on-Azure issues.”
Storage bottlenecks:
- Symptom: slow HANA savepoints, high disk queue lengths
- Check: AMS OS provider for disk I/O metrics, HANA provider for savepoint duration
- Fix: increase disk IOPS/throughput (Premium SSD v2 allows online adjustment), add disks to stripe set
Network latency:
- Symptom: slow RFC calls between app and DB tier, transaction timeouts
- Check: niping between VMs, Network Watcher connection monitor
- Fix: verify accelerated networking is enabled, check PPG placement, review NSG rules for drops
Memory pressure:
- Symptom: HANA OOM (Out of Memory) kills, slow queries
- Check: AMS HANA provider for memory utilization, HANA memory advisor
- Fix: enable Native Storage Extension (dynamic tiering), increase VM size, clean up HANA memory consumers
Troubleshooting order matters
Always troubleshoot from the SAP layer down: (1) SAP application metrics (AMS NetWeaver), (2) HANA database metrics (AMS HANA), (3) OS infrastructure (AMS OS), (4) Network (Network Watcher). Starting at the infrastructure layer wastes time when the issue is an SAP configuration problem.
Azure support plans
For production SAP, the right Azure support plan matters:
- Developer — for non-production, experimentation only
- Standard — business-hours support for production workloads
- Professional Direct — faster response times with proactive guidance
- Premier/Unified — Microsoft’s premium plan with a designated Technical Account Manager, proactive health checks, advisory services, and 24/7 support
- SAP joint support — Microsoft and SAP collaborate on tickets (part of the partnership)
- Know the escalation path: open Azure ticket for infrastructure issues, SAP ticket for application issues, and the joint support process bridges both
Course wrap-up: all four characters
🏗️ Raj raises his coffee cup. “We did it. PrecisionSteel is running SAP on Azure — migrated, optimized, and monitored.”
☁️ Mei smiles at Yuki. “And you helped them design the infrastructure, HA, and DR architecture. Good job, team.”
🛡️ Lars gives a thumbs up. “GlobalPharma’s SAP is compliant, highly available, and protected by Sentinel. Dr. Schmidt is satisfied — for now.”
🔧 Aisha grins. “TradeCorp’s 15 SAP systems are backed up, cost-optimized, and monitored 24/7. Carlos finally stopped asking about the Azure bill.”
Exam prep tips
As you prepare for the AZ-120 exam:
- Know SAP Notes — 1928533 (certified VMs), 2015553 (support prerequisites), 2205917 (SLES tuning), 2009879 (HANA guidelines)
- Understand the “why” — the exam tests decision-making, not just memorization. Know why you would choose one option over another.
- Practice scenarios — every question is scenario-based. Practice reading the scenario for RPO/RTO requirements, VM sizing constraints, and cost considerations.
- Focus on Linux HA — Pacemaker, STONITH, and HANA HSR get more exam weight than WSFC.
- Know the Azure services — Load Balancer, ANF, ASR, Backup, Sentinel, ACSS, and SDAF are all testable.
- Review Microsoft Learn modules — the official AZ-120 learning path covers each domain in detail.
Knowledge check
TradeCorp's QA team needs production data refreshed to the QA HANA system. What is the recommended approach?
Aisha notices HANA savepoints taking longer than usual. What should she check first?
Aisha is defining the OS patching policy for TradeCorp's SAP landscape across dev, QA, and production. What is the recommended OS patching strategy for SAP environments with multiple stages?
Congratulations!
You have completed the entire AZ-120 study guide. Across four domains, you have learned to:
- Domain 1 — Migrate SAP workloads to Azure (assessment, strategy, execution, validation)
- Domain 2 — Design and implement infrastructure (VMs, storage, networking, HANA, app tier, ACSS, SDAF)
- Domain 3 — Design and implement HA and DR (ASCS clustering, HANA HSR, shared storage, Load Balancer, DR strategy and implementation)
- Domain 4 — Maintain SAP workloads (monitoring, backup, security, Sentinel, cost optimization, operations)
You followed Raj through his migration, Mei through her architecture designs, Lars through his HA/DR implementations, and Aisha through her Day-2 operations. Each module built on the previous one, just like a real SAP-on-Azure project.
Good luck on the exam. You are ready. 🎓
🎬 Video coming soon