All the information is available under global.ini file which stores global configuration properties for each service in the landscape.These are the global properties most frequently used for extended storage configuration −Name                                    Section                Value                  Defaultbasepath_logbackup      persistence                File path ($DIR_INSTANCE)/backup/log

All the information is available under global.ini file which stores global configuration properties for each service in the landscape.These are the global properties most frequently used for extended storage configuration −               Name                                                Section                                                  Value                  Defaultbasepath_databackup  persistence        File path($DIR_INSTANCE)/backup/data               

M_SAVEPOINTS view stores Current and historical savepoint statistics. There is column DURATION which tells the total time taken by savepoint.You can extract the following information from the numbers in this view −CRITICAL_PHASE_DURATION shows the period of time during which the updaters were blocked in a savepoint. Normally, this should be in the milliseconds range, except for a global savepoint for data backup, which may take longer due to global synchronization across all nodes. If the critical phase duration is too long, there is probably some problem (e.g., I/O load is too high).DURATION shows the total time taken by a savepoint. ... Read More

M_SAVEPOINT_STATISTICS view shows information about executed savepoints.This view contains columns- START_TIME, STATE, VERSION and LAST_* relate to the last executed or currently-executing savepoint.Following information is available −

This can be checked using M_SAVEPOINT_STATISTICS. This view has a resettable counterpart. This means, you can also see the values since the last reset in the dependent view: M_SAVEPOINT_STATISTICS_RESET.To reset the values, use the SQL command −ALTER SYSTEM RESET MONITORING VIEW SYS.M_SAVEPOINT_STATISTICS_RESETor the management console command −monitor reset -n M_SAVEPOINT_STATISTICS_RESET

You can run savepoint manually by executing the below command −ALTER System SAVEPOINTChecking savepoint statistics of SAP HANA

In SAP HANA database, changed data is automatically saved from memory to disk and at the interval on which it is saved is called savepoints and by default they are set to occur every five minutes. In SAP HANA, there is a persistence layer which is used to make these savepoint at regular interval. During this operation changed data is written to disk and redo logs are also saved to disk as well.The data belonging to a Savepoint tells consistent state of the data on disk and remains there until the next savepoint operation has completed. Redo log entries are ... Read More

SAP Persistence layer is required in the following scenarios −In any database, main memory is volatile therefore data is lost during a restart or when a power outage occurs.Data needs to be stored in persisted medium.Backup & Restore is available.It ensures that the database is restored to the most recent committed state after a restart and that transaction are either completely executed or completely undone.

In SAP HANA, Persistence layer is used for handling all operational and transaction data to take secure backup and restoring data incase of corruption or database crash. It provides use of Save point which can be used for restoring data.With use of concept of persistence layer of SAP’s relational database, it ensures the successful data restores. Besides managing log data on the disk, HANA’s persistence layer allows read and write data operations via all storage interfaces.Persistence layer in HANA ensures that database can be restored to the most recent committed state after a restart or after a system crash and ... Read More

SAP HANA Replication allows migration of data from source systems to SAP HANA database. Simple way to move data from existing SAP system to HANA is by using various data replication techniques.System replication can be set up on the console via command line or by using HANA studio. The primary ECC or transaction systems can stay online during this process. We have three types of data replication methods in HANA system −SAP LT Replication methodETL tool SAP Business Object Data Service (BODS) methodDirect Extractor connection method (DXC)These methods are based on different mechanism of data replication and is recommended for ... Read More