A backup that stopped landing

The backup-age maintenance duty (#13331) files one issue when the newest backup in the backup directory is more than 36 hours old: a missed night is loud once, not silent.

time. File times only; nothing is opened, run or shelled out to. Symlinks are not followed.

newest file's path and when it last changed. While one is open a later run files none (fileIssueOnce); closing it lets the next miss file a new one.

a directory with no file yet, and a backup under 36 hours old.

file, so the duty then judges no age and files nothing; its finding says the directory was not read.

newest copy that left the machine, from the snapshot record. This duty reads the local directory's files themselves, so it catches a record that says a backup landed while the files are not there or not fresh, and a directory nothing is writing to. The limits differ on purpose: the alarm is a live banner for the off-box copy, this is one issue for the local one.

naming age and path and not again, symlinks and the entry cap, the board row.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs