In SAP HANA Studio the persistence section under global.ini shows the system properties. We will then use the “fsfreeze” Linux utility to halt any IO to the volume and ensure consistency. Take the value offered by the global.ini file and remove the database name from the path to only get the base path mount point (this assumes that the SAP HANA systems has been setup with a mount point and single volume each for log and data). The data persistence mount point can be identified by inspecting the global.ini persistence section for “basepath_datavolumes”. Open a terminal (SSH or local to the system) and ensure the prompt is logged in as a user who has read, write and execute permissions on the SAP HANA data persistence mount point. (Optional)Freeze the filesystem for the SAP HANA data persistence mount point The process for creating application consistent snapshots differs for systems deployed with multiple database containers (a system with a single tenant is still deployed as MDC), single containers, single host (scale up) and distributed host (scale out) systems.
Sap hana studio plugins software#
The process can also be automated using programmatic logic interfacing with HANA database SQL, secure shell bash commands, and Pure Storage Flash Arrays REST API or the associated software development kit (SDK). SAP HANA using the naming convention "Data Snapshot" for application consistent storage snapshots.Īpplication consistent snapshots can be manually performed using SAP HANA Studio, a secure shell terminal (SSH) signed in with a user who has read/write and execute permissions to the SAP HANA data volume and the Pure Storage FlashArray web user interface. In order to create application consistent storage snapshots for SAP HANA databases it is important to note that this operation requires the database instance, operating system, and storage system to all be synchronized during execution.