Now collects log entries reporting progress and rates of transfer during a backup, and giving info on what is slowing them down.
log
How can you tell what causing a backup to run so slowly? If it is this bug, what can you do about it? A plain user’s guide.
Surely these problems with Time Machine are old hat and not news? Or are they simply errors occurring with disks or the file system?
Running an AppleScript which tries to run a shell command with root privileges can fail. Here’s why, and what we can’t do about it.
New beta-release can check your log file structure and send a simple test command to log, confirming that all is in working order.
Here’s what happens when a Time Machine backup, normally the first, slows to the point where it’s just never going to finish.
Logs are normally backed up by Time Machine, but Apple provides no tool which can access those backed up logs. Here’s how to do it.
The more frequently your Mac writes entries to its log, the shorter will its log record be: anything from a couple of days to almost a month.
If a Time Machine snapshot can’t be thinned, nothing warns you of the problem, and without Terminal or the log you can’t even find out.
What does your Mac get up to when you’re away from it? Mine was busy writing hundreds of thousands of entries in the log because of a couple of snapshots.
The Eclectic Light Company 