A company is designing a disaster recovery (DR) strategy for an SAP HANA database that runs on an Amazon EC2 instance in a single Availability Zone. The company can tolerate a long RTO and an RPO grea

Question

Options

• ASet up AWS CloudFormation to automatically launch a new EC2 instance for the SAP HANA
• BLaunch a secondary EC2 instance for the SAP HANA database on a less powerful EC2 instance
• CLaunch a secondary EC2 instance for the SAP HANA database on an equivalent EC2 instance
• DSet up AWS CloudFormation to automatically launch a new EC2 instance for the SAP HANA

• A
  79% (41)
• B
  4% (2)
• C
  12% (6)
• D
  6% (3)

Explanation

The company explicitly accepts a long RTO and RPO greater than zero in exchange for cost savings. This means there is no need to maintain a running standby EC2 instance. The most cost-effective DR option is to use AWS CloudFormation to define the EC2 instance configuration as infrastructure-as-code, then launch a new instance only when a disaster occurs and restore the SAP HANA database from the S3 backups (already in place via AWS Backint Agent). This incurs no ongoing compute cost for a standby instance. Options B and C require a continuously running secondary EC2 instance (whether smaller or equivalent), generating ongoing costs. Option D likely differs from A in some configuration detail but the core principle - using CloudFormation to launch on demand and restoring from S3 - is the most cost-efficient approach when long RTO is acceptable.

No community discussion yet for this question.