Fixes a bug which could cause the app to crash when starting to run an audit.
bug
Now collects log entries reporting progress and rates of transfer during a backup, and giving info on what is slowing them down.
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?
When making a first full backup of less than 2 GB takes 86 minutes, and you then can’t restore from it anyway.
The plan was simple: replace my 8 year-old Promise Pegasus RAID system with a shiny new SSD RAID system, for Time Machine backups. What could go wrong?
Here’s what happens when a Time Machine backup, normally the first, slows to the point where it’s just never going to finish.
Catches and issues with the 10.15.3 update – and good news on two important bugs which it fixed.
Five updates in a single day? Here’s the explanation.
Why couldn’t a user specify times before 0100 and after 1300, when the DatePicker worked fine using the 24-hour clock?
