Cancelled, errors
16. Cancelled backups. The most common reason for a scheduled backup being cancelled is when it tries to start too soon (less than ten minutes) after the last backup. However, there can be other reasons, and any cancelled backups are reported:
cancelled 1 backups.
If no backups are cancelled, no message is produced.
17. Methods used to determine each backup (Catalina only). Each time that Time Machine examines a volume to determine what to back up in 10.15, it chooses between making a full first backup, performing a deep traversal scan (default for the Recovery volume), performing a consistency scan, using the FSEvents database, or calculating the difference between snapshots (only for APFS volumes). Additional information reported includes the total number of volumes backed up over the period
Of 9 volume backups:
then the number of times each method was used:
0 were full first backups,
3 were deep scans,
6 used FSEvents,
0 used snapshot diffs
0 used consistency scans,
0 used cached events.
Those are typical results for Time Machine backing up 3 volumes (System, Data, Recovery) over 3 hours = 9 volume backups.
18. Error messages. Normally, no errors should result, and this is stated clearly as
No error messages found.
If any errors are found, they are listed individually after
2 errors reported:
and given as, for example,
2017-05-24 10:13:13.555672+0100 Error: (-8084) SrcErr:YES Copying /Users/hoakley/Library/Preferences/com.apple.dt.Xcode.plist to (null)
Errors are given simply as the timestamp of that log entry, followed by the error message. Those which are unimportant are not included here, but not all error messages will necessarily be of significance. If you're in doubt, open ➜ Consolation , set it to retrieve Time Machine log entries, and enter the same time period as used for T2M2. You will then be able to see the full details for those errors.
Any error message automatically sets the traffic light to red.
The Eclectic Light Company – https://eclecticlight.co