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:
1 parent
64961b1141
commit
e517de35af
11 files changed
+9248
-9
No files matched your search
@@ -1675,6 +1675,7 @@ export const duplicatiSources = sqliteTable("duplicati_sources", {
|
||||
.notNull()
|
||||
.default(sql`(current_timestamp)`),
|
||||
lastReportAt: text("last_report_at"), // ISO
|
||||
lastReport: text("last_report"), // JSON: what the last report turned out to be, and how many of each kind there have been (see services/duplicati.ts, SourceActivity)
|
||||
});
|
||||
|
||||
// One backup job of one source, as its last report left it. A job is learned from its first report (by name) and is expected to succeed every `expectedHours`.
|
||||
|
||||
Reference in new issue
Block a user