![]() The next one is scheduled for 4:30pm, I’ll see.Īll in all, I’ve times, I really start to miss the simplicity and reliability of 10.6.ĭont’t get me wrong but, any time I read about new emojis being added to the “OS” announced as part of system upgrades, I’m about to loose it. In the past more than two hours backups were postponed to the next hour. Immediately after the reboot a backup started and … that was it! It’s not really possible to find a pattern in what was saved and what not. I had a deeper look at this with ‘Backup Loupe’ which confirmed my suspicion. I just became aware of this only because I needed some files restored. Most apparent (because I ran into this), some parts of my home-directory haven’t been saved to the backup for a couple of days. On the bottom-line it looked as if anything filesystem-related started to cause hickups. Hi, just found your article and I share your frustration:Ģ and a half hours ago I had to reboot the system after 10 days, because it overall became unreliable. Clearly you have done alot of research on this. On all backups I get this line in the logs:Ĭould not back up OS X Recovery to /Volumes/Time Machine Backups/Backups.backupdb: Error Domain=NSCocoaErrorDomain Code=-69830 “Failed to get info for unmounted Recovery partition (error -69830): This operation requires an unmounted disk” UserInfo=Īfter rebooting and with backups running normally, that error is gone.ītw I have sent Apple your articles hoping it would point them in the right direction. One note the Apple advisor and I picked up on. Now that I have rebooted my backups are back to being their normal hourly happy self again. For the OS I reminded them that High Sierra just came out what a month ago and i’m on Sierra which should be still supported and going to HS is not an option for me. Yes they blamed it on 3rd party apps AND also suggested I’m not on the latest OS. I will give you one guess as to what their response was…. At first they were only slightly off (90 mins in between) but it got exponentially worse over time. I was going NUTS trying to figure out what was going on with my backups. ![]() I cannot thank you enough for these articles. Whatever anyone likes to call the affected system. My DispatchView tool is an excellent way of diagnosing this problem, and I have the log extracts to demonstrate how this bug occurs. The only solution is restarting the Mac when backups become irregular.ĭAS is part of an undocumented system in macOS which I have previously referred to here as Grand Central Dispatch (GCD), which is incompletely documented – and have been criticised in comments for doing so. Those systems most likely to be affected are those running macOS Server, as reported in comments on this blog. I reported this bug to Apple in February, and initial experience with Sierra 10.12.4 suggested that it may have been fixed. All activities managed by DAS are affected. They then become extremely irregular and unreliable – backups may be made several hours apart, for example. It also may not affect Macs which are left running continuously for many days, but which enter system sleep I am unable to let my Mac enter system sleep because when it does so, it sleeps its hard drive (despite being set not to).Īfter a variable period of continuous running, usually longer than 7 days, sometimes over 30 days, Time Machine backups and other activities which are managed and dispatched by the Duet Activity Scheduler (DAS) will cease being scheduled correctly. This bug does not affect Macs which are shut down daily, or even weekly, for example. The old bug in macOS Sierra, which has been present since its first release last year, resulting in Time Machine backups and other background tasks becoming highly irregular and unreliable, has not been fixed in Sierra 10.12.4.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |