| copyright | lastupdated | subcollection | keywords | ||
|---|---|---|---|---|---|
|
2024-11-17 |
pattern-sap-on-powervs |
{{site.data.keyword.attribute-definition-list}}
{: #resiliency-design}
Resiliency solution components:
Resiliency is the ability of a workload to meet a specific target Service Level Objective (SLO), Service Level Availability (SLA) or recover from a service disruption and still meet the required SLA. Resiliency needs to be considered at both the infrastructure and application layers across the entire solution. PVS regions
A resilient design will include Backup&Recovery and, may include Disaster Recovery (DR) and High Availability (HA) depending on Service Level Availability (SLA) requirements.
Backup and Recovery:
For HANA data protection, SAP provides tools:
- HANA Studio - An integrated development environment for managing, modeling, and monitoring SAP HANA databases.
- HANACOCKPIT - A web-based tool for administering, monitoring, and managing SAP HANA systems.
- Backint - A certified SAP interface for integrating third-party backup tools with SAP HANA for backup and restore operations.
For SAP certified HANA backup tools, please refer to SAP note 2031547. On IBM Power System Virtual Servers, Veeam, Spectrum Protect and Cobalt Iron from Compass are recommended tools and services.
Disaster Recovery:
Disaster Recovery is to recover and restore system operations after a disruptive event. These events can range from natural disasters like earthquakes or floods to man-made events like cyber-attacks, power outages, or hardware failures.
A performance-optimized disaster recovery (DR) solution is designed to not only recover from disruptions but also to do so in a manner that minimizes downtime and maintains performance levels close to or as good as the production environment. The goal is to ensure that recovery operations are efficient and that the DR site performs well during and after failover.
- Low Recovery Time Objective (RTO): Aim to minimize the time it takes to restore services to their normal state. This involves using technologies and strategies that allow for quick failover, such as pre-staged and fully synchronized replicas of data and systems.
- Low Recovery Point Objective (RPO): Ensure that data loss is kept to a minimum by implementing frequent, near-real-time data replication and backup solutions. A cost-optimized disaster recovery (DR) solution aims to balance the need for effective disaster recovery with budget constraints. The focus is on achieving reliable recovery while managing and minimizing expenses.
Instead of dedicated infrastructure for DR systems, which may be idle most of the time, shared infrastructure may be configured so that DR systems share the same compute with Non-Production systems, if segmentation/compliance/licensing/Non-Production system availability and other client requirements allow.
Also, using reduced-size compute for dedicated DR systems may be an option as well. To reserve the capacity for DR systems, Shared Processor Pool can be setup with a small fee.
High Availability :
High Availability Purpose and Metrics-
High Availability is to ensure systems remain operational and accessible with minimal downtime, even in the event of failures. The goal of HA is to provide continuous service by eliminating single points of failure and ensuring that critical components have redundant systems or processes in place.
Service Level Availability (SLA) is the major metrics for high availability. When SLA requirement for the SAP application is higher than 99.5%, it is recommended to implement HA.
Single Point Failures of SAP S/4HANA on IBM Power Systems Virtual Servers:
| Components | Recommendation |
|---|---|
| SAP Web Dispatcher | SAP Web Dispatcher {: external } |
| SAP Central Services (ASCS for ABAP system, SCS for Java system) | |
| SAP Application server | Multiple application servers |
| SAP HANA | |
| Shared Storage | SAP Web Dispatcher |
| Networking | Highly available IBM Cloud services. For example, Direct Link, Transit Gateway, Application Load Balancer |
{: caption="Resiliency options" caption-side="bottom"}
The SAP HANA database supports high availability in a distributed system by providing for host auto-failover. If an active host fails, for example, because of a hardware failure, standby hosts can take over and ensure the continued availability of the database.
IBM Power Systems Virtual Servers are designed by hardened configuration within single data center to provide 99.95% SLA. For more details, please refer to IBM Terms
To increase availability for SAP systems on IBM Power Systems Virtual servers, High Availability instances can be deployed with “Different Server” placement group, and Disaster Recovery systems can be deployed in a different region.
To setup HA cluster for SAP applications and databases, both data replication and cluster management should be considered. Data replication can be done with database native methods, OS native tools, as well as third party continuous data protection tools. Cluster management on Linux can be done with Red Hat High Availability Add-On or SUSE High Availability Extension.
For more information on SAP HA Implementation on IBM Cloud: SAP HA
Availability for SAP Central services :
The following should not be different for classic/VPC/PVS, since it is more on Operating System/Application layer.
- SAP documents on ASCS/ERS1: SAP Doc{: external}
- SAP documents on ERS1 and ENSA2: SAP Doc{: external}
- SUSE documents on setting up HA: • ERS1{: external} • ENSA2{: external}
- RHEL documents on setting up HA: • ERS1{: external} • ENSA2{: external}
High Availability for SAP HANA :
- SAP Documentation on SAP HANA replications, including synchronization mode and operation mode: SAP Doc{: external}
- IBM Cloud documentation on SAP HANA high Availability: SAP HA
- SUSE documentation on SAP HANA high availability: SUSE DOC{: external}
- RHEL documentation on SAP HANA high availability: RHEL DOC{: external}