Architecture patterns for SAP HANA on Amazon - SAP HANA on Amazon
SAP HANA System ReplicationSecondary SAP HANA instanceOverview of patterns
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Architecture patterns for SAP HANA on Amazon

This section provides information on architecture patterns that can be used as guidelines for deploying SAP HANA systems on Amazon. For more information on the architecture patterns for SAP NetWeaver-based applications on Amazon, see Architecture guidance for availability and reliability of SAP on Amazon.

You can change the patterns to fit your changing business requirements with minimum to no downtime, depending on the complexity of your chosen architecture pattern.

Topics

SAP HANA System Replication

SAP HANA System Replication is a high availability solution provided by SAP for SAP HANA that can be used to reduce outage due to maintenance activities, faults, and disasters. It continuously replicates data on a secondary instance. The changes persist on the alternate instance in the event of a failure on the primary instance. For more information, see Configuring SAP HANA System Replication.

Secondary SAP HANA instance

In Amazon Cloud, a secondary SAP HANA instance can exist in the same Region on a different Availability Zone or in a separate Region. For more information, see Architecture guidelines and decisions. The secondary instance can be deployed as a passive instance or an active (read-only) instance. When the secondary instance is deployed as a passive instance, you can reuse the Amazon EC2 instance capacity to accommodate a non-production SAP HANA workload.

Overview of patterns

The architecture patterns for SAP HANA are divided into the following two categories:

You must consider the risk and impact of each failure type, and the cost of mitigation when choosing a pattern. The following table provides a quick overview of the architecture patterns for SAP HANA systems on Amazon.

Patterns

Business requirements

Solution characteristics

Implementation details

Resilience type

Recovery point objective1

Recovery time objective2

Cost

Complexity

Capacity re-use3

SAP HANA System Replication4

Amazon S3 replication5

Pattern 1

Single Region disaster recovery

Near zero

Low

Medium

Medium

Optional

2-tier

Same Region

Pattern 2

Near zero

Low

Medium

High

Yes

3-tier

Pattern 3

Low

Medium

Low

Medium

Yes

2-tier

Pattern 4

Medium

High

Very low

Very low

N/A

N/A

Pattern 5

Multi-Region disaster recovery

Near zero

Low

Medium

Medium

Optional

2-tier

Cross Region

Pattern 6

Near zero

Low

High

High

Optional

3-tier

Pattern 7

Near zero

Low

Very high

Very high

Optional

Multi-target

Pattern 8

Medium

High

Low

Low

N/A

N/A

1To achieve near zero recovery point objective, SAP HANA System Replication must be setup in sync mode for the SAP HANA instances within the same Region.

2To achieve the lowest recovery time objective, we recommend using a high availability setup with third-party cluster solutions in combination with SAP HANA System Replication.

3A production sized Amazon EC2 instance can be deployed as an MCOS installation to accommodate a non-production SAP HANA instance.

4SAP HANA System Replication and the number of SAP HANA instance copies as targets.

5Same-Region replication copies objects across Amazon S3 buckets in the same Region.