View a markdown version of this page

Best Practice 15.4 – Consider performance tuning for recovery and availability options - SAP Lens

Best Practice 15.4 – Consider performance tuning for recovery and availability options

In alignment with both the Well-Architected Reliability and Operational Excellence pillars, tuning of the SAP system given your chosen recovery and resiliency requirements should be evaluated to minimize any performance impact. Take into consideration items such as system performance during a backup, clustering options for the chosen database (for example, synchronous vs. asynchronous SAP HANA System Replication), and the distribution of load across multiple SAP application server instances.

Suggestion 15.4.1 – Review performance recommendations for backup and recovery solutions

Each supported database has different recommendations to optimize the performance of backups and recovery operations, and these often work in conjunction with your chosen software solution for managing backups and restores, including third-party offerings.

In general, following the guidelines for improving throughput between an EC2 instance and the storage target of your backup (such as, EBS volumes, S3 buckets, and EFS file systems) can improve the performance of your backup and recovery.

For example, when using Amazon S3 as a repository for backups and AWS Backint Agent for SAP HANA, you can enable performance improvements via changing configuration parameters, such as the maximum concurrency settings. Another common way to improve backup performance is to increase EBS volume performance characteristics, such as maximizing GP3 throughput configuration to 1,000 MB/s.

For more information, refer to the following:

Database Guidance
SAP HANA
SAP ASE (Consult SAP or Vendor documentation for guidance)
IBM Db2 (Consult SAP or Vendor documentation for guidance)
Oracle SAP Note: 2084077 - How to plan backup cycle for Oracle database [Requires SAP Portal Access]
Microsoft SQL Server SAP Note: 1420452 - FAQ: Restore and recovery with MS SQL Server [Requires SAP Portal Access]
SAP MaxDB SAP Note: 1377148 - FAQ: SAP MaxDB backup / recovery [Requires SAP Portal Access]

Suggestion 15.4.2 – Review configuration of clustering parameters

Clustering options for SAP HANA and other databases often rely on a confirmed connection in a cluster (that is, a heartbeat) between the primary instance and the failover instance. SAP administrators must balance the speed with which an action can occur in the system with the potential for any failover side effects that may occur if there is a false negative interruption in communication. Follow recommendations for timeout parameters and related settings.