Irrelevant errors
Errors that are not relevant for restore are automatically corrected rule-based (e.g. open temporary files)
Re-evaluation of backup jobs
Backups that only contain irrelevant errors are re-evaluated as error-free (rc = 0)
Less effort and more quality
Daily control is reduced to backups with only relevant errors
Deviations in quantity and time
Detection of backups whose amount or duration differs from the average of e.g. the last 8 backups by more than 30%
Self-healing for underground backups
Automatic correction of faulty backup if subsequent backup is without error
Logical inconsistencies
Detection of e.g. backups with an amount of 0 bytes – because the backup job was changed by mistake
Detailed information at a glance
For each backup job: results, error messages, quantities, runtimes, start, end, last comment, …
Filter, search and sort options available
30 days review
For each backup job: the last 30 results are directly bvisible
Comments list
Fast commenting of faulty backups by selection from last comments (client and user)
Missing backups
Detect missing backups – e.g. because they were erroneously deleted from automation
Application server without any backup
Detect servers for which (so far) no backup at all exists
Dedicated protocols for all backups / restores
Automatically get a separate protocol for each backup / restore
Cumulated results
Month view over all days and year view over all months
Grouping option
Backup servers, backup clients or tenants
Zooming
Year > Months > Days
