10 – Design to withstand failure
How do you design your SAP workload to withstand failure? Work backwards from your business requirements to define an approach for meeting the availability goals of your SAP infrastructure and data. For each failure scenario, the resiliency requirements, acceptable data loss, and mean time to recover (MTTR) need to be proportionate to the criticality of the component and the business applications it supports. Select from one of the AWS architecture patterns provided for SAP availability, and evaluate it based on the criteria you define. These criteria should include the risk and impact for each failure as well as taking into consideration cost and performance. In all cases, use initial and periodic testing to validate your decisions.
| ID | Priority | Best Practice |
|---|---|---|
| ☐ BP 10.1 | Required | Agree on SAP workload availability goals that align with your business requirements |
| ☐ BP 10.2 | Highly Recommended | Select an SAP deployment pattern suitable for your availability and capacity requirements |
| ☐ BP 10.3 | Highly Recommended | Define an approach to help ensure availability of critical SAP data |
| ☐ BP 10.4 | Recommended | Validate the design against a set of criteria based on the business requirements |
For more details, see the following information:
-
AWS Documentation: Architecture Guidance for Availability and Reliability of SAP on AWS including Failure Scenarios and Architecture Patterns
-
AWS Documentation: The Amazon Builders' Library: Static stability using Availability Zones
-
AWS Documentation: AWS Direct Connect Resiliency Recommendations
-
AWS Documentation: Disaster Recovery of Workloads on AWS: Recovery in the Cloud
-
SAP Documentation: SAP HANA System Architecture Overview
