==== HANA backups ====

=== Purpose ===
Backups are important for disaster recovery, you have to make sure that DATA and LOG are saved regularly. This monitor will look for the time elapsed between last backup as well as backup size and duration.
=== Configuration hints ===

**Last backup age** 
For LOG and DATA backup, you can set a threshold to get an alarm if the last backup is too old. Threshold and severity can be set separately


**Backup size and duration** 
For each type of backup, you can monitor size and duration and get notified in case threshold is reached.

**Expected log mode** 
You can define the expected log mode and get an alarm if the current mode is not as expected

**Automatic log backup** 
You can define the expected automatic log backup setting and get an alarm if the current setting is not as expected

=== Atomic fields ===
^Auto clear|If set, the generated alarms will be automatically cleared from the console if the alarm condition is not fulfilled anymore|
^Log metric|If enabled, metrics will be sent for LOG backup statistics|
^Data alarm|If enabled, alarms will be sent for DATA backups|
^Last data backup threshold|The threshold of the maximum age of the last DATA backup (sec, min, h)|
^Severity|Last log backup severity|
^Severity|Log backup duration severity|
^Severity|Expected log mode severity|
^Severity|Automatic log backup severity|
^Data backup duration threshold|Data backup duration threshold  (sec, min, h)|
^Data metric|If enabled, send metrics on DATA backups statistics|
^Log backup duration threshold|Log backup duration threshold (sec, min, h)|
^Failures alarm|If enable, send an alarm if a backup is in failed state|
^Severity |Severity of last data backup|
^Severity|Severity of data backup duration|
^Log alarm|If enabled, send alarms for LOG backups|
^Last log backup threshold|The max age of the last LOG backup|
^Expected log mode|The expected log mode|
^Automatic log backup|The automatic log backup setting|
^Severity|The severity of the alarm sent for backup failures|

=== Surveillance table ===

^Parameter^Description^
^Active|If checked, the rule is enabled and will be processed|
^Host|Can be used to restrict the monitoring to a given host (multi instance case). A star (‘*’) will matchany host.|
^Service|: Defines from which service the backup files will be checked. A star (‘*’) will match any service.|
^Backup type|The type of backup.|
^Max size (TB/GB/MB)|The maximum file size. Unit can be specified: TB, GB, MB or KB. If no unit specified, the valuewill be assumed as bytes. If set to 0, the size won’t be monitored.|
^Severity|Defines the level of severity of the alarm that will be generated if one of the thresholds isreached.|
^Alarm tag|You can define some text to use as a prefix of the alarm message generated by the current rule.|
^Alarm|Defines if an alarm/metric has to be generated for the given rule.|
^Metric|Defines if an alarm/metric has to be generated for the given rule.|
=== Generated metrics ===
 
^metricId^metricUnit^metricTarget^metricDescription^
|LOG_BACKUP_DURATION|Minutes|SERVICE|The duration of the last LOG backup in minutes.|
|DATA_BACKUP_DURATION|Minutes|SERVICE|The duration of the last DATA backup in minutes.|
|TIME_SINCE_LAST_LOG_BACKUP|Minutes|TYPE|The number of elapsed minutes since last LOG backup.|
|TIME_SINCE_LAST_DATA_BACKUP|Minutes|TYPE|The number of elapsed hours since last DATA backup.|
|DATA_BACKUP_FILE_SIZE|Bytes|HOST - SERVICE|The size of the DATA backup file.|
|LOG_BACKUP_FILE_SIZE|Bytes|HOST - SERVICE|The size of the LOG backup file.|