PAS-C01 · Question #137
A company wants to improve the RPO and RTO for its SAP disaster recovery (DR) solution by running the DR solution on AWS. The company is running SAP ERP Central Component (SAP ECC) on SAP HANA. The co
The correct answer is D. For the SAP HANA database, use a smaller SAP certified Amazon EC2 instance. Use SAP HANA. Because the SAP HANA global allocation limit is only 768 GB rather than the full 1 TB of physical memory, a smaller SAP-certified EC2 instance running HANA System Replication meets the RPO/RTO targets most cost-effectively without changing backup parameters.
Question
A company wants to improve the RPO and RTO for its SAP disaster recovery (DR) solution by running the DR solution on AWS. The company is running SAP ERP Central Component (SAP ECC) on SAP HANA. The company has set an RPO of 15 minutes and an RTO of 4 hours. The production SAP HANA database is running on a physical appliance that has x86 architecture. The appliance has 1 TB of memory, and the SAP HANA global allocation limit is set to 768 GB. The SAP application servers are running as VMs on VMware, and they store data on an NFS file system. The company does not want to change any existing SAP HANA parameters that are related to data and log backup for its on-premises systems. What should an SAP solutions architect do to meet the DR objectives MOST cost-effectively?
Options
- AFor the SAP HANA database, change the log backup frequency to 5 minutes. Move the data and
- BFor the SAP HANA database, change the log backup frequency to 5 minutes. Move the data and
- CFor the SAP HANA database, SAP application servers, and NFS file shares, use CloudEndure
- DFor the SAP HANA database, use a smaller SAP certified Amazon EC2 instance. Use SAP HANA
How the community answered
(65 responses)- A20% (13)
- B6% (4)
- C11% (7)
- D63% (41)
Why each option
Because the SAP HANA global allocation limit is only 768 GB rather than the full 1 TB of physical memory, a smaller SAP-certified EC2 instance running HANA System Replication meets the RPO/RTO targets most cost-effectively without changing backup parameters.
Changing the log backup frequency directly modifies an existing SAP HANA backup parameter, which violates the company's explicit requirement to leave on-premises SAP HANA backup parameters unchanged.
Like option A, this choice also requires modifying the log backup frequency, which directly contradicts the stated constraint of not changing any existing SAP HANA data and log backup parameters.
AWS Application Migration Service (CloudEndure Migration) is designed for one-time server lift-and-shift migrations, not for continuous DR replication, and it cannot reliably provide a 15-minute RPO or support a structured 4-hour RTO failover for SAP HANA.
SAP HANA System Replication continuously replicates redo log data from the primary to a secondary instance, making it feasible to achieve an RPO of 15 minutes and an RTO of 4 hours. Because the global allocation limit is set to 768 GB rather than the full 1 TB of physical memory, a smaller SAP-certified EC2 instance that covers 768 GB of memory can serve as the DR target, meaningfully reducing cost compared to provisioning a full 1 TB instance.
Concept tested: SAP HANA System Replication for DR with right-sized EC2 instances
Source: https://docs.aws.amazon.com/sap/latest/sap-hana/sap-hana-on-aws-system-replication.html
Topics
Community Discussion
No community discussion yet for this question.