Skip to content
+90 850 885 27 43 info@argeict.com

Article · Cloud and infrastructure

SAP HANA hosting options and infrastructure requirements

SAP HANA is an in-memory database, and SAP supports it only under defined hardware conditions. This article explains the options and criteria for IT managers and SAP system owners deciding where to host HANA.

ARGE ICT · Published November 11, 2026 · Updated November 15, 2026

The first question in a move to HANA, or in a hardware refresh, is where the system will run. The answer depends on SAP's support conditions, the size of the database, and who will run operations.

What HANA requires of the infrastructure

HANA keeps and processes data in memory, and writes changes to data and log volumes on disk for persistence. Three resources therefore matter most: the amount of memory, the write latency of the log volume, and the network between servers.

HANA runs on the Linux distributions SAP supports: SUSE Linux Enterprise Server for SAP Applications and Red Hat Enterprise Linux for SAP Solutions. If another distribution is being considered, SAP's support conditions are confirmed separately first.

Certified hardware and SAP's support conditions

SAP supports two installation models. The first is the appliance, a system that the hardware vendor configures in advance and SAP certifies. The second is Tailored Data Center Integration (TDI), in which the organization places certified server, storage, and network components in its own data center layout.

Supported hardware is published in SAP's hardware directory. After installation, the hardware is measured with SAP's hardware measurement tool (HCMT).

SAP may decline to support a production system that runs on an unsupported configuration, so the conditions are confirmed before installation. The conditions are updated with each HANA release, so plan the installation against the conditions in force at that time.

Hosting options

The four options are compared on the same criteria. These are capital expenditure (CAPEX) and operating expense (OPEX), responsibility for hardware refresh, how fast capacity can grow, where the data is located, and who runs operations.

In an organization's own server room, hardware, power, cooling, and refresh all belong to the organization. The organization bears the capital expenditure, and adding capacity depends on ordering and installation time. The data stays in the organization's building, and the team that runs HANA also comes from the organization.

With hosting in a data center or a private cloud, the provider operates the hardware and resources are allocated to the organization. Cost moves mostly into operating expense, the provider is responsible for refresh, and the contract states which facility holds the data.

A public cloud uses the virtual server types that SAP has certified for HANA; SAP's hardware directory lists the certified types by provider. Capacity can usually be added without waiting for an order and cost follows usage, while the location of the data depends on the region selected.

With SAP's own cloud services, infrastructure and basic operations fall under SAP's contract. The organization concentrates on the application and functional side, and how far it can adjust infrastructure settings is set by the limits of the contract.

This comparison is not a ranking, and the suitable option depends on how much weight the criteria above carry for the organization.

Sizing

The memory requirement is calculated from the compressed size of the database and an allowance for working memory. SAP Quick Sizer is used for a new installation, and SAP's sizing report is used when an existing system is converted.

A growth allowance is added separately, and the memory for development, test, and quality systems is calculated on its own. Because the organization's own data and SAP's tools determine the result, a general ratio or a sample size would be misleading.

Backup, high availability, and disaster recovery

HANA has its own data and log backup, and third-party backup tools connect through the Backint interface. A backup has to be tested by restoring it to another system; the Restore test guide covers the scope and the record of such a test.

HANA System Replication copies data to a second system, either synchronously or asynchronously. For high availability (HA), automatic takeover can be set up with cluster software (Pacemaker).

Replication does not replace a backup, because logical corruption and accidental deletion are copied to the second system as well, so a backup with earlier recovery points is still needed.

Split of responsibilities

Responsibility is considered in four layers:

  • Infrastructure: servers, storage, network, and the operating system
  • Database and SAP Basis operations
  • Application and functional support
  • The SAP license

A hosting contract usually covers only the first layer, and the others are separate services. The responsibility matrix in the contract should state who is responsible for each layer.

SAP HANA on ARGE Cloud

We build and operate HANA infrastructure on ARGE Cloud or in the customer's server room. We size according to SAP's sizing report, confirm SAP's support conditions before installation, and do not recommend a configuration for production if it fails those conditions. HANA System Replication and the HA cluster are optional. We do not sell SAP licenses or provide functional consulting; the scope of the service is described on the SAP HANA infrastructure page.

Frequently asked questions

Do development and test systems also have to run on certified hardware? SAP's certified hardware requirement applies to production systems; the conditions for development and test systems are more flexible. Even so, if the quality system used for performance tests does not resemble production, the test results will be misleading. Check the current conditions in SAP's hardware directory and the relevant SAP Notes.

Can HANA run on a virtual server? Yes, under conditions that SAP defines. SAP supports HANA on specific virtualization platforms and publishes the memory, CPU allocation, and configuration conditions for each platform in separate SAP Notes. Before virtualizing a production system, confirm that the platform and version you plan to use are covered by those notes.

How is an existing HANA system moved to another infrastructure? There are two common methods: restoring a backup to the target system, or using HANA System Replication to synchronize the data to the target and then performing a planned switchover. The choice depends on the size of the database and the acceptable downtime. Before the move, confirm that the target environment meets SAP's support conditions, and run a rehearsal migration before the production cutover.

Sources

  • Certified and Supported SAP HANA Hardware Directory, SAP (sap.com)
  • SAP HANA Tailored Data Center Integration (TDI) documentation and the SAP HANA Administration Guide, SAP Help Portal (help.sap.com)

Expert call for your SAP HANA infrastructure

Share your sizing report or current HANA memory usage, and your system landscape; we respond to your request within one business day.

Speak to an expert