Say Hello to HANA Fast Restart!

What is the concept of HANA Fast restart ?

In-memory data in SAP HANA is primarily stored and managed within the main memory of the server. The Fast Restart option does not involve continuous data flow between multiple locations.

The Fast Restart option leverages the use of the file system to store and reuse certain data fragments called MAIN data fragments. These MAIN data fragments are typically loaded into memory from persistent storage during the initial system startup. With the Fast Restart option enabled, instead of reloading the MAIN data fragments from persistent storage during subsequent restarts, they are preserved in tmpfs file systems within the main memory itself.

The tmpfs file systems act as a temporary storage location for the MAIN data fragments, allowing for faster restart times by eliminating the need to reload the data from the slower persistent storage. The MAIN data fragments are stored in the tmpfs file systems, ensuring they are readily available in memory when the system restarts, thereby minimizing the downtime.

So, while the Fast Restart option uses the file system to store MAIN data fragments temporarily, the primary storage and processing of in-memory data in SAP HANA still occur within the main memory itself. There is no continuous flow of data between multiple locations; rather, the Fast Restart option facilitates faster system restarts by leveraging the file system for storing and reusing specific data fragments.

Certainly! Let's understand how the Fast Restart option works in a more straightforward manner:

In SAP HANA, there are two key locations where data resides: the persistent storage and the main memory. The persistent storage is like a large database where data is stored for long-term use, while the main memory is a faster workspace for processing data in real-time.

During the initial startup of SAP HANA, data is loaded from the persistent storage into the main memory to enable quick access and processing. However, this data loading process can take some time, especially when dealing with large amounts of data.

To speed up system restarts and minimize downtime, the Fast Restart option was introduced. It utilizes a file system called "tmpfs" within the main memory itself. Think of it as a temporary storage area that is faster to access than the persistent storage.

When the Fast Restart option is enabled, specific data fragments known as MAIN data fragments are stored in the tmpfs file system within the main memory. These MAIN data fragments are important pieces of data that are frequently accessed and processed by the system.

During a system restart, instead of reloading all the data from the slower persistent storage, the system simply retrieves the MAIN data fragments from the tmpfs file system in the main memory. This significantly reduces the time it takes to restart the system since the data is already available in the faster main memory.

It's important to note that the Fast Restart option doesn't continuously move data between locations. It simply stores crucial MAIN data fragments in the tmpfs file system within the main memory, making them readily accessible for faster system restarts.

By utilizing the Fast Restart option, SAP HANA can quickly resume its operations after a restart, minimizing any interruptions and allowing users to continue their work without delay.

FAQs/Myths about HANA Fast Restart:

1. What is HANA Fast Restart, and how does it work?

- HANA Fast Restart is a feature that speeds up system restarts by reusing MAIN data fragments stored in a tmpfs file system within the main memory. It eliminates the need to reload data from the slower persistent storage.

2. Does HANA Fast Restart require additional memory?

- The MAIN data fragments stored in the tmpfs file system utilize space within the main memory itself. Therefore, enabling Fast Restart does not require additional memory beyond what is already allocated to HANA.

3. Is there a trade-off between memory usage and HANA Fast Restart?

- The tmpfs file system used for Fast Restart consumes a portion of the allocated main memory. However, this space is utilized to store crucial data fragments, enabling faster restarts. It's important to consider this memory usage when planning HANA system sizing.

4. Can we choose between HANA Fast Restart and normal restart?

- Enabling Fast Restart does not provide an explicit option to choose between Fast Restart and normal restart. Once Fast Restart is enabled, it becomes the default method for system restarts.

5. How do we enable HANA Fast Restart?

- Fast Restart is enabled by configuring the necessary mount points for the tmpfs file system and setting the appropriate permissions. These configurations are typically done during the initial installation or setup of the HANA system.

6. Is there any impact on HANA sizing with Fast Restart enabled?

- The Fast Restart option does not impact HANA sizing guidelines directly. However, the memory allocated for the tmpfs file system should be considered when planning the overall memory requirements for the HANA system.

7. Does HANA Fast Restart improve overall system performance?

- HANA Fast Restart primarily focuses on reducing system restart times and minimizing downtime. It does not directly impact the ongoing performance of the HANA system during normal operations.

8. Can HANA Fast Restart be used with all hardware and operating systems?

- Yes, HANA Fast Restart is compatible with all supported SAP HANA hardware platforms and operating system versions.

9. Does HANA Fast Restart work with both single-node and multi-node HANA systems?

- Yes, HANA Fast Restart can be used with both single-node and multi-node HANA systems. The configuration and usage remain the same across these deployment scenarios.

10. Is HANA Fast Restart suitable for all types of HANA deployments?

- HANA Fast Restart is beneficial for environments where minimizing restart times and reducing downtime are critical. However, the specific suitability of Fast Restart may vary based on individual deployment requirements and workload characteristics.

Q11: Does the tmpfs file system used in SAP HANA Fast Restart hold redundant data?

No, the tmpfs file system employed in SAP HANA Fast Restart does not hold redundant data. The tmpfs file system acts as a temporary storage area within the main memory, specifically used to store MAIN data fragments that are crucial for faster system restarts. Its purpose is to avoid reloading these data fragments from the slower persistent storage during a restart.

However, it's important to understand that the tmpfs file system is volatile, meaning its contents are not preserved across system reboots or power outages. The data stored in tmpfs is held in memory and is not redundantly backed up in the same way as data in persistent storage.

To ensure data durability and consistency, any modifications made to the warm data during the Fast Restart scenario are eventually written back to the persistent storage. This process guarantees that the changed data is securely preserved in a durable and persistent manner.

In summary, while the tmpfs file system plays a role in speeding up system restarts, it does not hold redundant data and is not intended for long-term data storage. The data in tmpfs is temporary and subject to being reloaded from the persistent storage when the system restarts.

Comments

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 : https://help.sap.com/doc/saphelp_nw73ehp1/7.31.19/enUS/b3/903925c34a45e28a2861b59c3c5623/content.htm?no_cache=true How to check if it is working or not ? In case of linux , you can simply ps -ef | grep s...

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...

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...

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 : sap-perf.ca Let's discuss the WORKLO...

SAP application log tables: BALHDR (Application Log: Header Data) and BALDAT (Application Log: Detail Data)

BALHDR (Application Log: Header Data): Usage : The BALHDR table stores the header information for application logs. It serves as a central repository for managing and organizing log entries. Example Data Stored: The table may contain entries for various system activities, such as error messages, warnings, or information logs generated during SAP transactions or custom programs. Columns Involved: LOGNUMBER: Unique log number assigned to each log entry. OBJECT: Identifies the object associated with the log entry (e.g., a program, transaction, or process). SUBOBJECT: Further categorizes the object. USERNAME: User ID of the person who created the log entry. TIME: Date and time when the log entry was created. ADD_OBJECT: Additional information or details related to the log entry. BALDAT (Application Log: Detail Data): Usage : The BALDAT table contains the detailed data for each log entry, linked to the corresponding entry in the BALHDR table. It stores the specific log details an...

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...

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.

ABAP Dumps Analysis

Ever now and then have you heard about ABAP Dumps, We also have a joke everything in temporary in life except ABAP dumps for SAP Consultants. Lets try to understand ABAP dumps from perspective of a SAP BASIS Consultant. Dumps happen when an ABAP program runs and something goes wrong that cannot be handled by the program We have two broad categories of Dumps , In custom program Dumps and SAP provided program Dumps. Dumps that happen in the customer namespace ranges (i.e. own-developed code) or known as Custom Program , can usually be fixed by the ABAP programmer of your team. Dumps that happen in SAP standard code probably need a fix from SAP. You do not have to be an "ABAPer" in order to resolve ABAP dump issues. The common way to deal with them is to look up in ST22 How to correct the error ? Hints are given for the keywords that may be used to search on the note system. Gather Information about the issue Go to System > Status and Check the Basis SP level as well as info...

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...

Let's Talk SAP

Search This Blog