A summary of the known benefits and current limitations of Time Machine backups to APFS, with links to more detailed accounts.
When a “fixed” formatting string proves anything but fixed, then breaks without warning or even mention in a release note.
Does Big Sur’s Time Machine preserve sparse files and clones when backing up to APFS volumes?
How Apple made changes to Foundation routines which format dates and times which can break their formatting when in 12-hour clock mode.
Adds support for reporting whether a file is a sparse file, or has been cloned, in Big Sur.
A good improvement appears to have been abandoned unfinished and suffering from bugs. Will Apple fix these and finish it off in 11.3?
Consolation, Ulbow, Mints, T2M2, Cirrus and Taccy all updated to cope with increasing complexity and unreliability of the unified log.
New version searches for sparse files and clones, reporting their individual sizes and totals for the folder or volume examined.
Big Sur has recently introduced a bug which can change the format of log datestamps, which can break Ulbow, Mints and T2M2. Here’s how to fix it.
APFS can ‘clone’ files when copying or duplicating them within the same volume. But how can you tell whether any given file is a clone?