{"id":45466,"date":"2024-10-22T14:01:46","date_gmt":"2024-10-22T18:01:46","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=45466"},"modified":"2025-02-16T17:06:02","modified_gmt":"2025-02-16T22:06:02","slug":"time-machine-in-sequoia","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2024\/10\/22\/time-machine-in-sequoia\/","title":{"rendered":"Time Machine in Sequoia"},"content":{"rendered":"

Der Teilweise<\/a>:<\/p>\n

\n

Backing up to a NAS currently says 3 days (!) left, after having backed up ~160GB.\nWas using WiFi with TX rate 133MBit.<\/p>\n

Now I connected using Gigabit Ethernet, does not seem to be faster.<\/p>\n

Plus: CPU usage is ridiculously high, fans spinning up to medium\/max speed several times per hour.<\/p>\n

[…]<\/p>\n

I did not change all<\/em> files on my disk …<\/p>\n

Maybe they removed the alert that was shown when the backup got corrupted? Seems to be the case because I did not get that alert and all my old backups (on the NAS) seem to be gone.<\/p>\n

[…]<\/p>\n

So it seems like Apple indeed removed the confirmation dialog that they showed when they delete corrupted backups, taking away the chance to manually repair it.<\/p>\n<\/blockquote>\n\n

I wonder whether this happened pre-Sequoia? Even on Sonoma, I would regularly have Time Machine backups where I would imagine that less than 50 GB changed, but it took all day to back up to a local hard drive. (Yet it wasn’t so slow that it seemed to be starting from scratch.) I wish Time Machine were better at showing which files are being copied<\/a> and how the space is being used<\/a>. (I guess some of this can be figured out using BackupLoupe<\/a>.)<\/p>\n\n

Miguel Arroz<\/a>:<\/p>\n

There’s some annoying bug in Sequoia that makes a Time Machine backup fail with an error “The backup failed because some files were not available”.<\/p>

How on earth can files “not be available” on something running locally? And whatever it is, why isn’t Time Machine dealing with it properly? It’s all made by the same company. And it had all night to do whatever it has to.<\/p>

I needed to have a current backup fresh in the morning, and now I’m sitting here waiting.<\/p><\/blockquote>\n\n

Der Teilweise<\/a>:<\/p>\n

I wouldn’t be surprised if the opendir<\/code> bug described by @cdfinder<\/a> is a race condition that also happens (more rarely) for local filesystems.<\/p><\/blockquote>\n\n

Previously:<\/p>\n