Skip to main content

Details on Hana Fast Restart

Details on HANA Fast restart

The SAP HANA Fast Restart option helps speed up the restart of the SAP HANA service. It does this by reusing certain data fragments stored in the file system instead of reloading them from the storage. This is useful when the operating system doesn't need to be restarted.

With the Fast Restart option, the SAP HANA service can quickly start up by using the data fragments already stored in memory, which reduces the time it takes to get everything up and running again. This is different from the usual method of reloading data from the storage, which can be slower. The Fast Restart option stores these data fragments in a special type of file system that can grow and shrink as needed.

The Fast Restart option works with different types of hardware and operating systems that are supported by SAP HANA. It doesn't affect the performance or sizing of SAP HANA when it's running normally.

When comparing it to another feature called Persistent Memory, the Fast Restart option is an alternative for situations where servers with Persistent Memory are not available or cannot be used together with Persistent Memory. While the Fast Restart option reduces the downtime, it doesn't offer the same cost savings as Persistent Memory. Here's a comparison of when each option can be used to reuse the data fragments without reading them from the storage:

- HANA restart: Both options can be used.

- HANA service restart: Both options can be used.

- HANA upgrade/service patch: Both options can be used.

- Operating system update/service patch: Only Persistent Memory can be used.

- Planned server reboot: Only Persistent Memory can be used.

- Server reboot due to hardware failure: Only Persistent Memory can be used.

- Power outage: Only Persistent Memory can be used.

- BIOS/firmware update: Only Persistent Memory can be used.

- Hardware upgrade without Persistent Memory replacement: Only Persistent Memory can be used.

To sum it up, the SAP HANA Fast Restart option makes it faster to restart the SAP HANA service by reusing data fragments stored in the file system. It's a convenient option when the operating system doesn't need to be restarted. However, it's not as cost-efficient as using Persistent Memory, which provides even faster restart times.

To use the SAP HANA Fast Restart option, you need to follow these steps:

1. Determine the number of CPU sockets (The number of CPU sockets available on a HANA server is important because it determines the maximum number of CPUs that can be installed and utilized by the system. Each CPU socket can typically accommodate a single physical CPU chip, which may contain multiple CPU cores) available on your HANA server by running the following command:


cat /sys/devices/system/node/node*/meminfo | grep MemTotal | awk 'BEGIN {printf "%10s | %20s\n", "NUMA NODE", "MEMORY GB"; while (i++ < 33) printf "-"; printf "\n"} {printf "%10d | %20.3f\n", $2, $4/1048576}'


This will provide you with information about the nodes, such as their numbers and the amount of memory they have.

2. Create a directory and mount for each node that has memory. Make sure that all tmpfs mounts have a preferred NUMA policy. Here's an example:


mkdir -p /hana/tmpfs0/<SID>

mount tmpfs<SID>0 -t tmpfs -o mpol=prefer:0 /hana/tmpfs0/<SID>

mkdir -p /hana/tmpfs1/<SID>

mount tmpfs<SID>1 -t tmpfs -o mpol=prefer:1 /hana/tmpfs1/<SID>


Replace `<SID>` with the appropriate identifier for your system. Ensure that you have proper access rights for these directories:


chown -R <SID>adm:sapsys /hana/tmpfs*/<SID>

chmod 777 -R /hana/tmpfs*/<SID>


3. If you want to limit the size of these mounts, you can use the SIZE option of the mount command. For example:


mount tmpfs<SID>0 -t tmpfs -o mpol=prefer:0,size=250G /hana/tmpfs0/<SID>


4. To ensure that the mount points remain available after an operating system reboot, you need to add entries to the file system table, usually located at `/etc/fstab`. Add the following entries, replacing `<sid>` with your system's identifier:


tmpfs<sid>0 /hana/tmpfs0/<sid> tmpfs rw,relatime,mpol=prefer:0 0 0

tmpfs<sid>1 /hana/tmpfs1/<sid> tmpfs rw,relatime,mpol=prefer:1 0 0



In the [persistence] section of the global.ini file, you need to define the basepath location for the in-memory storage of MAIN data fragments. Use the `basepath_persistent_memory_volumes` parameter to specify the basepath location. 

You can define multiple locations corresponding to NUMA nodes, separated by a semicolon. For example:




Ensure that you also refer to the Persistent Memory topic for further details on using the same basepath parameter.

You can enable the Fast Restart option for partitions, tables, or columns by using SQL CREATE and ALTER table statements with the `alter_persistent_memory_spec` clause. Refer to the examples in the Persistent Memory section for more information.

To limit the overall tmpfs memory usage for all NUMA nodes, you can set the `persistent_memory_global_allocation_limit` parameter in the [memorymanager] section of the global.ini file. By default, no limit is specified, and HANA determines a reasonable value. You can enter a value in MB to set a limit on the size of the used tmpfs space for each host.

When unloading tables from memory, the standard UNLOAD statement and implicit table unloads do not free the memory by default. The `table_unload_action` parameter in the [

persistent_memory] section of the indexserver.ini file controls this behavior. The default value for tmpfs is DELETE, which clears the MAIN data fragments from tmpfs. However, you can set it to RETAIN if needed.

To completely free memory, you can use the UNLOAD statement with the additional DELETE PERSISTENT MEMORY clause:




If you wish to limit the size of the main memory storage, you can decrease the tmpfs file system size or use the `persistent_memory_global_allocation_limit` parameter to restrict the used tmpfs size.

Remember to adjust the commands and configuration settings to match your specific system setup and requirements.



You might find these interesting

How to properly Start/Stop SAP system through command line ?

Starting/stopping an SAP system is not a critical task, but the method that most of us follow to achieve this is sometimes wrong. A common mistake that most of the SAP admins do is, making use of the 'startsap' and 'stopsap' commands for starting/stopping the system.  These commands got deprecated in 2015 because the scripts were not being maintained anymore and SAP recommends not to use them as many people have faced errors while executing those scripts. For more info and the bugs in scripts, you can check the sap note 809477.  These scripts are not available in kernel version 7.73 and later. So if these are not the correct commands, then how to start/stop the sap system?  In this post, we will see how to do it in the correct way. SAP SYSTEM VS INSTANCE In SAP, an instance is a group of resources such as memory, work processes and so on, usually in support of a single application server or database server with

sapstartsrv is not started or sapcontrol is not working

 What is sapstartsrv ? The SAP start service runs on every computer where an instance of an SAP system is started. It is implemented as a service on Windows, and as a daemon on UNIX. The process is called  sapstartsrv.exe   on Windows, and   sapstartsrv   on UNIX platforms. The SAP start service provides the following functions for monitoring SAP systems, instances, and processes. Starting and stopping Monitoring the runtime state Reading logs, traces, and configuration files Technical information, such as network ports, active sessions, thread lists, etc. These services are provided on SAPControl SOAP Web Service, and used by SAP monitoring tools (SAP Management Console,  SAP NetWeaver  Administrator, etc.). For more understanding use this link : How to check if it is working or not ? In case of linux , you can simply ps -ef | grep sapstartsrv In case of windows, you need

HANA System Replication - Prerequisites & Setup

Hey Folks! Welcome back to Hana high availability blog series. In our last blog we checked out operation & replication modes in hana system replication. If you haven't gone though that blog, you can checkout  this link In this blog we will be talking about the prerequisites of hana replication and it's setup. So let's get started. When we plan to setup hana system replication, we need to make sure that all prerequisite steps have been followed. Let's have a look at these prerequisites. HANA System Replication Prerequisites: Primary & secondary systems should be up & running HDB version of secondary should be greater than or equal to Primary database sever But, for Active/Active(read enabled config), HDB version should be same on both sites. System configuration/ini files should be identical on both sides Replication happe

ST03N : The chapter for all BASIS Admins

This blog is targeted to BASIS ADMINS Transaction for workload analysis statistical data changed over time are monitored using transaction code ST03 , now ST03N (from SAP R/3 4.6C) . With SAP Web AS 6.4 the transaction ST03 is available again. From time to time ST03 and ST03N has seen many changes but later in SAP NW7.0 ST03N has reworked in detail specially processing time is now shown in separate column. Main Use of ST03N  is to get detailed information on performance of any ABAP based SAP system. Workload monitor analyzes the statistical data originally collected by kernel. You can compare or analyze the performance of a single application server or multiple application server. Using this you start checking from the entire system and finding your way to that one application server and narrowing down to exact issue. By Default :- You see data of current day as default view , you can change the default view. Source of the image : Let's discuss the WORKLOAD MONITOR By D

How to resolve Common Error : Standard Template "sap_sm.xls" missing

Hey everyone, putting forward a common error we usually face when we have “ Excel inplace” functionality enabled in our SAP system. This error occurs when validity of the signature of SAP standard templates expired or were incorrectly delivered via support packages. We can reproduce the error by doing as below.. Click on “spreadsheet” icon after any SAP ALV grid view of data is on screen to make this data to export into excel directly from SAP.

HANA hdbuserstore

The hdbuserstore (hana secure user store) is a tool which comes as an executable with the SAP Hana Client package. This secure user store allows you to store SAP HANA connection information, including user passwords, securely on clients. With the help of secure store, the client applications can connect to SAP HANA without the user having to enter host name or logon credentials. You can also use the secure store to configure failover support for application servers in a 3-tier scenario (for example, SAP Business Warehouse) by storing a list of all the hosts that the application server can connect to. To access the system using secure store, there are two connect options: (1)key and (2)virtualHostName. key is the hdbuserstore key that you use to connect to SAP HANA, while virtualHostName specifies the virtual host name. This option allows you to change where the hdbuserstore searches for the data and key files. Note

SAP HANA System Replication - Operation Mode & Replication Mode

Hey Folks! Welcome back to Hana high availability blog series. In our last blog we checked out what is hana system replication and how it basically works. If you haven't gone through that blog, you can checkout link In this blog we will be talking about the replication modes and operation modes in hana system replication. So let's get started. When we setup the replication and register the secondary site, we need to decide the operation mode & replication mode we want to choose for replication. For now we won't focus on setting up replication as we'll cover it in our next blogs.  Operation Modes in Hana System Replication: There are three operation modes available in system replication: delta_datashipping, logreplay and logreplay_readaccess. Default operation mode is logreplay. 1. Delta_datashipping: In this operation mode initially one full data shipping is done as part of replication setup and then a delta data shipping takes place occasionally in addition to cont

SUM Tool : An Introduction

Let’s Discuss about the famous tool, that is asked in almost all the Basis and HANA interview and it is very easy to understand but a bit tricky. Tighten your seatbelts and Let’s understand in one go. SAP Technical Upgrade is a periodic project that is implemented across companies to upgrade their SAP system to the latest released version. Most of the upgrade activities are done by the technical team and the role of functional consultants is limited and mostly confined to regression testing What are the maintenance that are performed by help of SUM ? Release upgrade (major release change) System update (EHP installation) applying Support Packages (SPs) / Support Package Stacks applying Java patches correction of installed software information combine update and migration to SAP HANA (DMO: Database Migration Option) System Conversion from SAP ERP to SAP S/4HANA   First thing first , never confuse in these two things : Upgrade and Update. Updating SAP products is for applying support pac

Work Process and Memory Management in SAP

Let’s talk about the entire concepts that are related to memory when we talk about SAP Application. Starting with few basic terminologies, Local Memory :  Local process memory, the operating system keeps the two allocation steps transparent. The operating system does the other tasks, such as reserving physical memory, loading and unloading virtual memory into and out of the main memory. Shared Memory :  If several processes are to access the same memory area, the two allocation steps are not transparent. One object is created that represents the physical memory and can be used by various processes. The processes can map the object fully or partially into the address space. The way this is done varies from platform to platform. Memory mapped files, unnamed mapped files, and shared memory are used.  Extended Memory : SAP extended memory is the core of the SAP memory management system. Each SAP work process has a part reserved in its virtual address space for extended memory. You can set

Complete Guide : XPI Inspector Tool

Content of this blog :           What is an XPI Inspector Tool ? Why XPI Tool is used ? XPI standard URL How to check XPI Tool version ? How to Install/Update XPI version using TELNET How to Use XPI Tool ? References – SAP Notes What is XPI Inspector tool ?          -    XPI Inspector is a diagnostics web application developed by SAP that collects logs and debug traces from various PI components in a very simple way and is useful for SAP PI consultants, developers, and administrators to get more insights on an issue. Why XPI is used  – 1.  Used to collect traces and logs from Messaging system or XI module. 2. Used to collect the related information to solving the issues or improving the PI or PO systems’ performance. 3. Using XPI Inspector application you will be able to collect a lot of information about your system that will help you to learn about problems in the past, to analyze new and detect such at an early stage. 4. Performs certain number of configuration checks, such as SSL c