Availability of asynchronous Determine which tables encountered the table As table replication - Monitors error replication error using system view 80 messages related to async table M_ASYNCHRONOUS_TABLE_REPLICAS, and replication check the corresponding indexserver alert traces Most recent savepoint operation- Investigate why there was a delay defining the last How long ago the last savepoint savepoint and consider triggering the operation 28 was defined; that is, how long ago manually by executing the SQL statement ALTER a complete, consistent image of SYSTEM SAVEPOINT the DB was persisted to disk Log mode LEGACY- If the DB is running in log mode "legacy." Log mode "legacy" does not 32 If you need point-in-time recovery, reconfigure the support and is log mode of your system to "normal." In the not recommended for productive "persistence" section of the global.ini configuration systems file, set the parameter "log_mode" to "normal" for Log mode OVERWRITE - If the the System layer. When you change the log mode, DB is running in log mode you must restart the DB system to activate the "overwrite."Log mode changes. It is also recommended that you perform a 33 "overwrite" does not support full data backup. point-in-recovery (only recovery to data backup) and is not recommended for prod systems 35 Daily Existence of data backup Perform a data backup as soon as possible Investigate why failed, resolve the problem, and 36 Daily Status of most recent data backup perform a new data backup as soon as possible Age of most recent successful 37 Daily Perform a data backup as soon as possible data backup Status of most recent log backups - If the most recent log backups Investigate why the log backup failed and resolve 38 Daily for services and volumes were the problem successful Savepoint duration - Identifies 54 long-running savepoint disk I/O performance operations. Run time of the log backups As currently running - If the most Investigate why the log backup runs for too long, 65 recent log backup terminates in and resolve the issue the given time Storage snapshot is prepared - If As the period when the DB is Investigate why the storage snapshot was not 66 prepared for a storage snapshot confirmed or abandoned, and resolve the issue exceeds threshold Enablement of automatic log Enable automatic log backup. For more details 69 backup - If automatic log backup please see SAP HANA Administration Guide. is enabled
80 As Availability of asynchronous table replication - Monitors error messages related to async table replication Determine which tables encountered the table replication error using system view M_ASYNCHRONOUS_TABLE_REPLICAS, and check the corresponding indexserver alert traces 28 Most recent savepoint operation- How long ago the last savepoint was defined; that is, how long ago a complete, consistent image of the DB was persisted to disk Investigate why there was a delay defining the last savepoint and consider triggering the operation manually by executing the SQL statement ALTER SYSTEM SAVEPOINT 32 Log mode LEGACY- If the DB is running in log mode "legacy." Log mode "legacy" does not support and is not recommended for productive systems If you need point-in-time recovery, reconfigure the log mode of your system to "normal." In the "persistence" section of the global.ini configuration file, set the parameter "log_mode" to "normal" for the System layer. When you change the log mode, you must restart the DB system to activate the changes. It is also recommended that you perform a full data backup. 33 Log mode OVERWRITE - If the DB is running in log mode "overwrite."Log mode "overwrite" does not support point-in-recovery (only recovery to data backup) and is not recommended for prod systems 35 Daily Existence of data backup Perform a data backup as soon as possible 36 Daily Status of most recent data backup Investigate why failed, resolve the problem, and perform a new data backup as soon as possible 37 Daily Age of most recent successful data backup Perform a data backup as soon as possible 38 Daily Status of most recent log backups - If the most recent log backups for services and volumes were successful Investigate why the log backup failed and resolve the problem 54 Savepoint duration - Identifies long-running savepoint operations. disk I/O performance 65 As Run time of the log backups currently running - If the most recent log backup terminates in the given time Investigate why the log backup runs for too long, and resolve the issue 66 As Storage snapshot is prepared - If the period when the DB is prepared for a storage snapshot exceeds threshold Investigate why the storage snapshot was not confirmed or abandoned, and resolve the issue 69 Enablement of automatic log backup - If automatic log backup is enabled Enable automatic log backup. For more details please see SAP HANA Administration Guide.