A company wants to implement a highly available SAP S/4HANA workload on AWS with automatic failover. The company also needs a cross-Region disaster recovery (DR) solution for the SAP S/4HANA productio

Question

Options

• ADeploy two identically sized SAP S/4HANA systems, each in a different Availability Zone in the
• BDeploy two identically sized SAP S/4HANA systems, each in a different Availability Zone in the
• CDeploy two SAP S/4HANA systems, each in a different Availability Zone in the primary AWS
• DDeploy two identically sized SAP S/4HANA systems, each in a different Availability Zone in the

• A
  66% (27)
• B
  20% (8)
• C
  10% (4)
• D
  5% (2)

Explanation

For the primary region HA requirement, two identically sized SAP S/4HANA instances across different Availability Zones with a Pacemaker cluster provides automatic failover. For the cross-Region DR with RPO ≤15 minutes and RTO ≤120 minutes, SAP HANA system replication in asynchronous mode (logreplay) to a secondary AWS Region satisfies the RPO. Because RTO is a relaxed 120 minutes (not near-zero), the DR instance does not need to be running full-time or sized identically - it can be a scaled-down or stopped instance that is resized and started only during a DR event. This makes option A the most cost-effective: it avoids paying for a continuously running, full-sized DR instance while still meeting the stated RPO/RTO targets. Options that require an always-on, identically sized DR system in a second region would meet the SLAs but at significantly higher cost.

No community discussion yet for this question.