When Sierra’s automatic backups stop or become irregular, other functions fail too. Here are some important and more obvious ones. Is this fixed in High Sierra, and does it affect iPhones too?
CTS
This new version lets you select which log file to analyse, and to add custom processes to examine within log files. Lots of power with elegant simplicity.
High Sierra has done away with the ntpd daemon for keeping your Mac’s clock in sync with a standard time server. This now works as in iOS, using the timed daemon.
Should fix a bug in which T2M2 reports an error message rather than completing an analysis of Time Machine backups.
It looks much the same as Sierra. Looking at High Sierra’s logs, though, shows that there are significant internal changes. Here’s a first glimpse at SkyLight, APFS and dasd at work.
Tools to explore and use the DAS and CTS scheduling and dispatching systems in Sierra and High Sierra.
Scheduling background activities like making backups has moved from cron to launchd, and now to a more complex system. This has reduced the reliability of macOS and made it harder to support.
Automatic backups will still become irregular or fail altogether, making Sierra 10.12.6 unsuitable for servers and systems requiring sustained operation.
How to diagnose this bug, manage it when it occurs, and try to prevent it from happening: latest information.
Lack of sleep can do strange things to people. Perhaps it can to Macs too. Could this solve the Time Machine irregularity bug?