You have an SAP production landscape that uses SAP HANA databases on Azure. You need to deploy a disaster recovery solution to the SAP HANA databases. The solution must meet the following…

Question

Options

• AAzure Site Recovery
• BAlways On availability group
• CHANA system replication that uses asynchronous replication
• DHANA system replication that uses synchronous replication

• A
  21% (11)
• B
  8% (4)
• C
  58% (31)
• D
  13% (7)

Explanation

HANA System Replication (HSR) with asynchronous replication is the correct choice because it is designed to handle the high network latency inherent in cross-region Azure deployments. Unlike synchronous replication, it does not force the primary system to wait for acknowledgment from the secondary before committing each transaction, making it practical across geographically distant Azure regions while still streaming changes continuously - which minimizes data loss compared to alternatives like periodic backups.

Why the distractors are wrong:

• A (Azure Site Recovery): ASR is a VM-level failover orchestration service; it doesn't provide database-aware replication and isn't optimized to minimize data loss for SAP HANA specifically.
• B (Always On availability groups): This is a SQL Server feature and has no applicability to SAP HANA databases whatsoever.
• D (Synchronous replication): Synchronous HSR requires very low latency (typically sub-millisecond) to avoid crippling primary system performance, because every commit must wait for the replica to confirm receipt. Cross-region Azure latency (often 10–100ms+) makes this operationally infeasible.

Memory tip: Think "Async = Across regions, Sync = Same site." Synchronous gives you zero data loss but chains you to low latency; asynchronous trades a small RPO window for the freedom to span long distances.

No community discussion yet for this question.