Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
cancel
Showing results for 
Search instead for 
Did you mean: 
mark_ma
Product and Topic Expert
Product and Topic Expert
2,243
Spoiler
updated date: 31.Oct.2023
This blog is part of the Business Continuity with RISE and BTP blog series:
part 1 – Concept Explained
part 2 – Technical Building Blocks in RISE 👈
part 3 – Technical Building Blocks in BTP

4. Technical Building Blocks in RISE

RISE with SAP Private Cloud Edition is a 'SaaS-like' one-stop offering with managed IaaS services (considering hyperscaler reference architecture of SAP on Azure, SAP on AWS, and SAP on GCP), managed SAP Basis services, and application support. In this section, we won't be discussing the commercial combinations or the exact same offerings in SAP RISE, but rather will just explain the technical building blocks of what makes running SAP on hyperscalers (Azure, AWS, and GCP) possible.

4.1. IaaS Level

4.1.1. Network

Load Balancers are functioned for monitoring and failover. With load balancers, the active server failure and be detected, then the traffic can be redirected to the redundant server. Below table is a summary of load balancers been used in RISE with SAP. Here's an example of how SSO request with High Availability works under load balancing in RISE.

AzureAzure Load Balancers
Azure Traffic Manager
  • cross-region failover
  • DNS-based traffic load balancer
AWSAWS Elastic Load Balancer (ELB)
    • cross-AZ, or cross-region failover
Amazon Route53
    • cross-AZ, or cross-region failover
GoogleGoogle Cloud Load Balancer
    • Network Load Balancer (NLB) for OSI Layer 4 (TCP/UDP/other IP protocol) load balancing
    • Application Load Balancer (ALB) for OSI Layer 7 (HTTP/HTTPS) load balancing
SAPSAP Web Dispatcher
    • A reverse proxy server for SAP systems, used to distribute incoming requests from clients to the appropriate application servers in a SAP landscape.

4.1.2. Storage

RISE with SAP Private Cloud Edition running on Azure, AWS, and GCP, consume hyperscaler native storage component. There native storage components are with built-in features/services of backup, replication (either synchronous or asynchronous), snapshot, and recovery.

AzureAzure Managed Disks
    • Azure Managed Disks are available within one Availability Zone with Locally Redundant Storage (LRS) feature by having 3 replicas within one single data center
    • with zone-redundant storage (ZRS) feature, Azure Managed Disks can be synchronously replicated across availability zone within a region, hence make cross-availability-zone failover possible
    • with Azure Site Recovery, which facilitates replication and failover across regions, as well as Azure Backup for regular backups and point-in-time recovery, can make cross-region failover possible
Azure Files
Azure NetApp Files
    • provides SMB or NFS shares for SAP's global transport directory
Azure Blob Storage
AWSElastic Block Storage (EBS)
    • EBS provides block-level storage volumes for use with EC2 instances. EBS for SAP Workload is used to store all the kernel, executable and data.
    • EBS Volume is only available within one Availability Zone.
    • with Amazon EBS snapshots, cross-availability-zone failover is possible by using the snapshots to recover EBS Volume into a separate Availability Zone
Elastic File System (EFS)
    • EFS is used to support shared file systems such as SAP Kernel, Interface Files, Batch Job files, Logs, and Transport files
    • EFS is cross-availability-zone resilient, meaning that failover of EFS over Availability Zones within one region is possible
Amazon FSx
    • Amazon FSx for NetApp ONTAP is a fully managed service that provides highly reliable, scalable, high-performing, and feature-rich file storage built on NetApp's popular ONTAP file system (use case: for SAP HANA)
Simple Storage Services (S3)
    • S3 is used to support backup of SAP systems, and also archival (historical data)
    • S3 is cross-availability-zone resilient, meaning that failover of S3 over Availability Zones within one region is possible
GCPPersistent Disk
    • By default, each Compute Engine virtual machine (VM) instance has a single boot Persistent Disk volume that contains the operating system.
    • Regional persistent disks provide durable storage and synchronous replication of data between two zones in the same region, with that, cross-availability-zone replication (RPO=0) is possible for HA or in-region DR purpose
Filestore
    • Filestore has built-in backup feature for cross-availability-zone and cross-region for DR purpose
Cloud Storage
    • Cloud Storage stores data redundantly in one region, dual-regions, or multi-regions. This allows customer to obtain the desired level of availability at the lowest cost for designated purposes (eg. SAP backup for DR purpose).

4.1.3. Compute

RISE with SAP Private Cloud Edition running on Azure, AWS, and GCP, consume hyperscaler native compute resources, and have been fully virtualised.
For Virtual Machines on Azure, AWS, and GCP, there are built-in Hypervisors doing monitoring, auto-restart, and self-healing.

Azure Virtual Machine
AWS EC2
    • Active-Active deployment cross availability zones within same region with distributed ASCS / ERS instance deployed
    • EC2 is available within an Availability Zone only, nevertheless the data are stored within EBS Volume, which can support cross-availability-zone and cross-region failover. And EC2 resources can be reserved in other availability zone and region.
Google Compute Engine
    • Google Cloud Backup and DR provides central backup management and can facilitate backup, replication and failover across regions for Google Compute Engine, SAP databases (HANA, ASE, IQ, MaxDB), and file shares. For HANA, both backint backups and block-based, incremental-forever backups are supported
    • Active-Active deployment cross availability zones within same region with distributed ASCS / ERS instance deployed
    • Workload Manager is a Compute Engine service that provides continuous analysis of your SAP configurations to identify issues, detect misconfigurations, and improve system reliability

 

4.2. Operating System Level


Clustering solution on OS level for high availability and disaster recovery purpose failover.

SUSE Linux (SLES) Pacemaker
Redhat Linux (RHEL) PowerHA
    • Red Hat Enterprise Linux High Availability Add-on provides all the necessary packages for configuring a pacemaker-based cluster that provides reliability, scalability, and availability to critical production services. In addition, the components for the Red Hat High Availability solutions for SAP NetWeaver, S/4HANA and SAP HANA
Microsoft Windows Server Failover Cluster

4.3. Application and Database Level

Application Server
    • SAP NetWeaver (ABAP and JAVA) provides the run-time environment for SAP installation-based applications
    • ABAP Central Services (ASCS) contains the ABAP message server and the Standalone Enqueue Server
    • Enqueue Replication Server (ERS) contains the replication table, which is a copy of the lock table of the Standalone Enqueue Server in the ASCS instance.
Database Server
    • supports a recovery point objective (RPO) of 0 seconds and a recovery time objective (RTO) measured in minutes.
    • depending on physical datacenter distance of the 2 HANA Database Servers, both synchronous replication (less than 100km) and asynchronous replication (more than 100km) are possible
    • scalability: Scale Up (increase RAM) and Scale Out (increase host)
    • scale out pattern: Worker Node (active/hot standby) and Standby Node (cold/passive standby) are the mechanism to create redundancy for high availability purpose

4.4. IaC and CI/CD pipeline

When deploying hyperscaler infrastructure resources, with IaC enabled, the provisioning of infrastructure can be through code instead of through manual processes.

AWS
    • AWS Cloud Formation, AWS Cloud Development Kit (AWS CDK) / for Kubernetes / for Terraform, AWS Cloud Control API
Azure
GCP


For application code change, CI/CD pipeline is recommended to automate and govern change management. This is especially necessary when doing side-by-side extensibility to keep the core clean. Below is a summary of available CI/CD pipeline services:

SAP Continuous Integration and Delivery
(on SAP BTP)



Azure DevOps



AWS CodePipeline



Google Cloud Build



 

Disclaimer

Spoiler
  • The blog content does not necessarily represent the official opinion of SAP, Microsoft, Amazon Web Services, or Google Cloud. The opinions appearing in this blog are backed by SAP, Azure, AWS, GCP documentation which can be revealed in the corresponding reference links.
  • The blog content is only focusing on technical discussion, hence can not be used as commercial basis, nor should be used as SAP official offering documentation.

Acknowledgment to contributors/reviewers/advisors:

Spoiler
Ke Ma (a.k.a. Mark), author, Senior Cloud Architect, RISE Cloud Advisory RA group

Special THANK YOU to RISE with SAP community members, who contributed to this blog:
Ferry Mulyadi, Partner Solution Architect, Amazon Web Services
Micah Waldman, Product Management Lead, Google Cloud Business Continuity
Thorsten Staerk, Customer Engineer, Google Cloud

Frank GongDigital Customer Engagement Manager, SAP ECS
Marc Koderer, Chief Architect, SAP ECS
Boris Maeck, Head of Technology and Architecture, SAP ECS
Aaron Smyth, Principle Service Architect, SAP
Sven BedorfHead of Cloud Architecture & Advisory, RISE Cloud Advisory, MEE
Kevin FlanaganHead of Cloud Architecture & Advisory, RISE Cloud Advisory, EMEA North
Luc DUCOIN, Cloud Architect & Advisor Expert, RISE Cloud Advisory, EMEA North
Richard Traut, Head of Cloud Architecture & Advisory, RISE Cloud Advisory, EMEA North

Extended Reading:

Spoiler