{% extends "documentation/base.html" %} {% block doc_content %}
Understand how backup jobs are created and configured in BackupChecks through the Inbox approval workflow.
Unlike traditional systems where you manually configure backup jobs, BackupChecks uses an Inbox-based approval workflow. Jobs are created by approving backup report emails, and all job configuration is automatically determined by Mail Parsers.
The job creation process follows these steps:
| Step | What Happens | Where |
|---|---|---|
| 1 | Backup report email arrives in monitored mailbox | Email system |
| 2 | Mail import fetches the email via Microsoft Graph API | Background process |
| 3 | Email appears in Inbox (no matching job exists yet) | Inbox page |
| 4 | Operator selects customer and clicks "Approve job" | Inbox page |
| 5 | Mail Parser extracts job configuration from email | Background process |
| 6 | Job is created with parser-determined configuration | Jobs page |
| 7 | Email is linked to job and removed from Inbox | Run Checks page |
To create a new backup job:
In the email detail modal, you'll see a Customer field with "Select customer" placeholder text. This field has autocomplete functionality:
Once you've selected a customer:
When you click on an email in the Inbox, a detail modal displays the parsed backup report information:
| Field | Description |
|---|---|
| From | Email sender address |
| Backup | Detected backup software (e.g., Veeam, Acronis) |
| Type | Backup type (e.g., Configuration Job, Full, Incremental) |
| Job | Parsed job name from the email |
| Overall | Backup result (Success, Failed, Warning) |
| Customer | Customer selection field (autocomplete) |
| Received | Date and time the email was received |
| Parsed | Date and time the email was parsed |
The Details panel on the right shows the parsed backup report content, including:
When you approve a job, the Mail Parser automatically determines the following job configuration:
| Configuration | How It's Determined |
|---|---|
| Backup Software | Detected from email subject, sender, or body patterns (e.g., Veeam, Acronis, Windows Server Backup) |
| Backup Type | Extracted from email content (e.g., Full, Incremental, Differential) |
| Job Name | Parsed from email subject or body |
| Sender Email Pattern | Email sender address (used to match future emails) |
| Subject Pattern | Email subject pattern (used to match future emails) |
| Success/Failure Detection | Parser rules for identifying successful vs. failed backups |
After approving your first job for a customer, you can automatically process other emails that match the same pattern:
To view a job's configuration after it has been created:
The job detail page shows:
If a backup job is no longer active, you can archive it:
Archived jobs:
To permanently delete a backup job:
A typical backup job goes through the following lifecycle:
| Stage | Description | Visibility |
|---|---|---|
| 1. Email in Inbox | Backup report arrives, no job exists yet | Inbox page |
| 2. Job Approved | Operator approves job from Inbox | Jobs page, Run Checks |
| 3. Active Job | Job receives regular backup reports | Daily Jobs, Run Checks, Jobs page |
| 4. Schedule Learned | System learns backup schedule after several runs | Daily Jobs (appears on expected days) |
| 5. Job Archived | Backup no longer runs, job archived for history | Hidden from operational views |
| 6. Job Deleted | Job and all data permanently removed | Completely removed |
No. Jobs can only be created by approving emails from the Inbox. This ensures that every job has a valid Mail Parser configuration and prevents misconfiguration.
No. Job configuration is determined by Mail Parsers and cannot be manually edited. If a parser is incorrectly identifying fields, contact the system developer/maintainer. Mail Parsers are code-level components and cannot be modified by administrators through the BackupChecks interface.
BackupChecks uses sender and subject patterns to uniquely identify jobs. If multiple jobs could match the same email pattern, the system will match to the first job created. Ensure each backup job sends reports with unique sender or subject patterns.
No, not directly. If a job was approved with the wrong customer, you need to:
Deleting a job returns its emails to the Inbox, allowing you to re-link them to the correct customer.