Say what the last Duplicati report was, so a machine with no jobs explains itself

Each machine's card shows whether the last report was a backup, another
operation that was set aside, or one that could not be read (with the reason),
and counts of each since it was added. Administrators can see the start of an
unreadable report.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
bobbanandClaude Sonnet 5.5 committed 2026-11-09 23:33:03 +01:00
1 parent 64961b1141
commit e517de35af
11 files changed
+9248 -9

No files matched your search

+2 -1
View File
@@ -248,7 +248,8 @@ Duplicati tells this app how each backup went ([INTEGRATIONS.md](../INTEGRATIONS
| **Failed** | The last run ended in `Error` or `Fatal` | warning; **critical from the second failure in a row** |
| **Overdue** | It has not succeeded for longer than it is **expected** to — 2 days unless you set it per job (6 hours to 90 days) | warning; **critical at three times that** |
The alert says which job, on which machine, why (the first error Duplicati reported) and when the last good backup was. Only the *Backup* operation counts: a compact, a repair or a verification does not say whether the data is safe. A job can be **muted** (no alert; it is still listed),
The alert says which job, on which machine, why (the first error Duplicati reported) and when the last good backup was. Only the *Backup* operation counts: a compact, a repair or a verification does not say whether the data is safe. A machine that is heard but has no jobs says why on its card (the last report was another operation, or could not be read, with counts since it was added) — see [INTEGRATIONS.md](../INTEGRATIONS.md#duplicati).
A job can be **muted** (no alert; it is still listed),
**Alert on warnings** (an operator's button on each job, off until switched on — some jobs always have a few, and a backup with warnings is still a backup) raises a warning-level alert while the job's last run had warnings, naming the job, how many there were and the first thing they said; the next clean run ends it. A job that is muted raises nothing, this included. Maintenance on the server silences it like the others.
A job can also be muted, and one that no longer exists can be **forgotten** (with its history; if Duplicati reports it again it is learned again). Each machine can be tied to a server, so **maintenance on that server silences its backups' alerts**.