{% extends "layout/base.html" %} {% block content %}

Dashboard

Inbox
{{ inbox_count }}
Open items
Success
{{ jobs_success_count }}
Success (override)
{{ jobs_success_override_count }}
Expected
{{ jobs_expected_count }}
Warning
{{ jobs_warning_count }}
Failed
{{ jobs_error_count }}
Missed
{{ jobs_missed_count }}
Legend
Success — job run completed successfully
Failed — job run failed, action required
Warning — job run completed with a warning
Missed — job run expected but did not execute
Expected — job run not yet due
Success (override) — marked as successful via override
{% if news_items %}
News {% if active_role == 'admin' %} Manage {% endif %}
{% for item in news_items %}
{{ item.title }}
{% if item.pinned %} Pinned {% endif %} {% if item.severity == 'warning' %} Warning {% else %} Info {% endif %}
{{ item.body }}
{% if item.link_url %} Open link {% endif %}
{% endfor %}
{% endif %} {% if active_role == 'admin' %}
System status
Database size: {{ db_size_human }}
Free disk space: {% if free_disk_warning %} {{ free_disk_human }} (mail import will be blocked below 2 GB) {% else %} {{ free_disk_human }} {% endif %}
{% endif %}

Backupchecks provides a centralized and consistent overview of the health and reliability of all backups within your environment. The platform collects backup results from multiple backup solutions and normalizes them into a single, clear and consistent status model. This enables teams to monitor backup quality across different vendors and environments in a predictable and uniform way.

Backup results are imported and evaluated automatically. Each backup run is analyzed and assigned a status such as Success, Warning, Failed, or Success (override). These statuses are determined by interpreting exit codes, detected error messages, log content, and configured rules, ensuring that the reported outcome reflects the real operational impact rather than raw technical output alone.

Daily operational validation is performed from the Run Checks page. This page acts as the primary workspace for reviewing backup runs. All runs that require attention are listed here, allowing operators to systematically review results and decide on the appropriate next step. The main objective of this process is to actively review backup runs and keep the Run Checks page clear.

{% endblock %}