Skip Navigation

SAP S/4HANA on HANA large instances with HA and DR

This solution architecture illustrates how a user request flows through an SAP landscape built on high-performance Azure Virtual Machines and an in-memory HANA database running on HANA large instances for unparalleled scalability and performance. This system takes advantage of OS clustering for database performance, high availability using HANA system replication and a full disaster recovery (DR) configuration for guaranteed system availability.

SAP S/4 HANA nas instâncias grandes do HANA com HA e DRA arquitetura desta solução ilustra a forma como o pedido de um utilizador flui por um ambiente SAP criado nas Máquinas Virtuais do Azure de alto desempenho e numa base de dados HANA de alto desempenho em execução nas instâncias grandes do HANA para assegurar desempenho e escalabilidade sem paralelo. Este sistema tira partido do clustering de SO para assegurar o desempenho da base de dados, elevada disponibilidade com o HANA System Replication e uma configuração completa de recuperação após desastre (DR) para garantir a disponibilidade do sistema.123456789

In this example, an on-premises SAP user executes a sales order via Fiori interface, custom interface, or other.

Azure high speed express route gateway is used to connect to Azure Virtual Machines.

Request flows into highly available ABAP SAP Central Services (ASCS) and then through application servers running on Azure Virtual Machines in an availability set offering a 99.95 percent uptime SLA.

Request is sent from App Server to SAP HANA running on primary large instance blades.

Primary and secondary blades are clustered at OS level for 99.99 percent availability and data replication is handled through HANA System Replication in synchronous mode (HSR) from primary to secondary enabling zero RPO.

In-memory data of SAP HANA is persisted to high-performance NFS storage.

Data from NFS storage is periodically backed up in seconds, using built-in storage snapshots on the local storage, with no impact to database performance.

Persistent data volume on secondary storage is replicated to dedicated DR system through a dedicated backbone network for HANA storage replication.

Large instance on DR side can be used for nonproduction to save costs by mounting both the QA storage and DR replicated volume (read-only).

  1. 1 In this example, an on-premises SAP user executes a sales order via Fiori interface, custom interface, or other.
  2. 2 Azure high speed express route gateway is used to connect to Azure Virtual Machines.
  3. 3 Request flows into highly available ABAP SAP Central Services (ASCS) and then through application servers running on Azure Virtual Machines in an availability set offering a 99.95 percent uptime SLA.
  4. 4 Request is sent from App Server to SAP HANA running on primary large instance blades.
  5. 5 Primary and secondary blades are clustered at OS level for 99.99 percent availability and data replication is handled through HANA System Replication in synchronous mode (HSR) from primary to secondary enabling zero RPO.
  1. 6 In-memory data of SAP HANA is persisted to high-performance NFS storage.
  2. 7 Data from NFS storage is periodically backed up in seconds, using built-in storage snapshots on the local storage, with no impact to database performance.
  3. 8 Persistent data volume on secondary storage is replicated to dedicated DR system through a dedicated backbone network for HANA storage replication.
  4. 9 Large instance on DR side can be used for nonproduction to save costs by mounting both the QA storage and DR replicated volume (read-only).

Implementation guidance

Products/Description Documentation

SAP HANA on Azure large instances

SAP HANA on Azure (large instances) run on dedicated blade servers located in a Microsoft Azure Datacenter. This is specific to the database server.

NFS storage for Azure HANA large instances

The Azure high performance NFS storage system offers the unmatched capability to perform snapshot backups and replication to secondary storage. In addition, HANA Large Instance is the only cloud infrastructure to provide storage volume encryption.

Virtual Machines

SAP on Azure requires that you run your SAP workloads on certified Microsoft Azure Virtual Machines. SAP requires at least two vCPUs and a ratio of 6:1 between memory and vCPU.

Premium Storage

Microsoft Azure Premium Storage provides improved throughput and less variability in I/O latencies. For improved performance, Premium Storage uses solid state disk (SSD) in Azure Storage nodes and read cache that is backed by the local SSD of an Azure compute node.

ExpressRoute (front end)

Azure ExpressRoute used on the front end (see diagram) provides secure, high-bandwidth connectivity to establish reliable connections between your network and the Microsoft Azure network.

ExpressRoute (back end)

Azure ExpressRoute used on the back end (see diagram) enables you to communicate between your Azure components in the Azure Datacenter and your SAP HANA on Azure (large instance) systems. The cost of the back end ExpressRoute is included in your SAP HANA on Azure (large instance).

Related solution architectures

SAP NetWeaver on SQL ServerThis NetWeaver on SQL Server application solution illustrates how a user request flows through an SAP landscape built on NetWeaver using Azure Virtual Machines to host SAP applications and a SQL Server database. This system takes advantage of OS clustering for high availability, premium storage for faster storage performance and scalability, SQL Server AlwaysOn capability for replication, and a full disaster recovery (DR) configuration for 99.95 percent system availability.123456789

SAP NetWeaver on SQL Server

This NetWeaver on SQL Server application solution illustrates how a user request flows through an SAP landscape built on NetWeaver using Azure Virtual Machines to host SAP applications and a SQL Server database. This system takes advantage of OS clustering for high availability, premium storage for faster storage performance and scalability, SQL Server AlwaysOn capability for replication and a full disaster recovery (DR) configuration for 99.95 percent system availability.