Imported from the Apple Support Forums via the Wayback Machine 🔗
Since I updated to Mojave, my Mac Mini's late 2012 Time Machine is slow as ****. Sometimes it seems to freeze altogether. I tried rebooting in safe mode, that seemed to solve the problem at least for a while, but then it started to run slow again.
I have a SSD as main drive and an HDD as backup drive, the first with 256 Gb and the second with 512 Gb. In previous versions of OSX I haven't detected this problem except once, and the safe mode trick worked fine and it continued working fine until the update to Mojave. Both SSD and HDD are internal disks, and the HDD is the Apple original that came with the Mac Mini itself, so I don't think is a hardware problem at all.
Please tell us more about your system like how much memory is installed. Is the SSD the original one installed with the system? Is the system performance otherwise fine as long as Time Machine isn't used?
Good luck, and please share what you find.
0
lllaass·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Could be that the original HD which is now the TM disk is failing. The original disk in my 2012 Min failed a few years ago.
0
Marzoa·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I run First Aid on both disks as suggested (both are internal, BTW), and it said both disks were perfectly fine BUT after running it the next backup worked as expected, so this made the trick somehow. Go figure...
Answering your questions, it's an i5 late 2012 Mac Mini, I added the SSD (Samsung EVO, if I don't recall it wrong) like five years ago and it's worked without problems so far. The SSD has like 77 Gi free out of 233. It's got 8 Gb of RAM since January, before it has 4 Gb only, and the difference on performance has been noticeable. All applications working perfectly except for these issues with Time Machine.
Thanks a lot!
0
Marzoa·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Nah, it's broken again. It seems it does well the first backup right after using First Aid, but the subsequent ones won't work. Using First Aid is too time consuming to make it reasonable to run it right before each backup.
0
Marzoa·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Memory and cpu usage by backupd is very low, but so is data transfer. I'm getting both read and write transfers per second from 0 to just a bunch of kilobytes in the best case. This only seems to happen with backupd, all other applications work just fine.