Instiq
Chapter 5 · Monitoring and maintenance·v1.0.0·Updated 8/6/2026·~12 min

What's changed: Created AZ-120 Chapter 5, completing the textbook (Domain 4 second-half: monitoring (Azure Monitor VM Insights, Azure Network Watcher, Azure Monitor for SAP solutions AMS integrating SAP HANA/NetWeaver internals); backup management (Azure Backup, Recovery Services vault, Azure Backup for SAP HANA DB-consistent, instant restore, restore validation); SAP operations (Azure Center for SAP solutions virtual instance VIS, start/stop, SAP LaMa connector for Azure)).

5.2Backup management

Key points

Understand managing backup policies, snapshots, and restore (including SAP/HANA) with Azure Backup and a Recovery Services vault.

In SAP operations, you continuously manage and validate the designed backup strategy, centered on Azure Backup and a Recovery Services vault.

5.2.1Backup policies and the vault

Azure Backup stores backup data in a Recovery Services vault and protects VMs/files/databases with backup policies (frequency, retention, schedule). SAP HANA can be protected with Azure Backup for SAP HANA (DB-consistent streaming backup), with policies tuned to RPO/RTO. Use app-consistent snapshots too for restore options. Continuously monitor that backups succeed (jobs/alerts).

5.2.2Restore management and validation

Restore is available at file/folder, VM, and database granularity, quickly via instant restore (snapshots) or by restoring to a new VM (encrypted VMs included). Crucially, validate restores—periodically confirm that backups actually restore (rehearse). Distinguish "backup = point-in-time protection" from "Azure Site Recovery = continuity during a regional outage," and in operations watch both job success and restorability.

Exam point

Cues: "store backups in a vault, protect by policy" = Azure Backup + Recovery Services vault. "DB-consistent HANA protection" = Azure Backup for SAP HANA. "fast restore" = instant restore (snapshots); restore to a new VM is possible. Backup (point-in-time) vs ASR (regional continuity). Validate restores regularly.

Warning

Watch the mix-ups: (1) Azure Backup (point-in-time) vs Azure Site Recovery (regional continuity). (2) HANA needs DB-consistent backup, not just VM backup. (3) Validate restorability, not just backup success. (4) Set retention/frequency by RPO/RTO vs cost.

Diagram: Azure Backup stores backups in a Recovery Services vault and protects VMs/files by policy (frequency/retention), HANA uses Azure Backup for SAP HANA DB-consistent backup, restore at file/VM/DB granularity via instant restore/new-VM restore, validate restorability regularly, and distinguish backup (point-in-time) from Azure Site Recovery (regional continuity).
Store, restore, validate

5.2.3Section summary

  • Azure Backup + Recovery Services vault for policy-based protection; HANA via DB-consistent backup
  • Restore at file/VM/DB granularity, instant restore/new-VM restore; validate restores regularly
  • Operate distinguishing backup (point-in-time) from Azure Site Recovery (regional continuity)

Sign in to track progress — Log in.

Quick check

(just a quick review)

Q1. You want to protect SAP VMs and files in a Recovery Services vault with policy-managed frequency/retention. Best?

Q2. You want DB-consistent protection of an SAP HANA database. Best?

Q3. Beyond backup success, what must you also verify in backup operations?

Q4. Which correctly distinguishes Azure Backup from Azure Site Recovery?

Q5. You want to restore an SAP VM quickly from a failure. Best?

Check your understandingPractice questions for Chapter 5: Monitoring and maintenance

Keep track of your progress

The full study guide is free to read. Sign up free to practice with the question bank, track what you have read, review your mistakes, and highlight passages.