{"id":26685,"date":"2019-09-26T13:23:26","date_gmt":"2019-09-26T17:23:26","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=26685"},"modified":"2021-09-08T11:29:25","modified_gmt":"2021-09-08T15:29:25","slug":"what-time-machine-doesnt-back-up","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2019\/09\/26\/what-time-machine-doesnt-back-up\/","title":{"rendered":"What Time Machine Doesn’t Back Up"},"content":{"rendered":"

Apple<\/a>:<\/p>\n

\n

You can use Time Machine, the built-in backup feature of your Mac, to automatically back up all of your files, including apps, music, photos, email, documents, and system files.<\/p>\n<\/blockquote>\n\n

Maxwell Swadling<\/a>:<\/p>\n

\n

Time Machine backups skip a bunch of files. Some you might expect, some might surprise you!<\/p>\n

[…]<\/p>\n

The Voice Memos iPad App On The Mac seems to exclude the one bit of data it is responsible for saving... recordings...<\/p>\n

[…]<\/p>\n

I covered in another blog post that the key Photos Photo Library database file is missing[…] Missing this and all its associated files needed to restore Photo Libraries without data loss.<\/p>\n<\/blockquote>\n\n

I don’t use Photos enough to know what its database stores that isn’t in iCloud Photo Library. But print projects<\/a> definitely don’t sync using iCloud, and they can represent a huge time investment. It looks like some project-related files do get backed up—maybe Photos is able to rebuild them into a new database?<\/p>\n\n

But I would feel more comfortable with everything backed up and not relying on a potentially lengthy or buggy rebuild. Some other backup software will exclude files by default, but you can adjust the settings to manually include them. That’s not possible with Time Machine.<\/p>\n\n

Maxwell Swadling<\/a>:<\/p>\n

\n

I was genuinely surprised iCloud Drive wasn’t backed up because I think of time machine as having the “go back in time a year and see what the file was” feature, which doesn’t work on iCloud Drive files!<\/p>\n<\/blockquote>\n\n

This sounded really bad to me, because iCloud Drive files don’t necessarily get stored in the cloud, either. Your Mac may not currently have a network connection, and sometimes uploads get delayed or wedged<\/a>. Once in the cloud, the files are subject to beta bugs<\/a>, and you have only a very limited<\/a> ability to restore the latest version of individual files that it thinks you deleted.<\/p>\n\n

But Howard Oakley<\/a> says iCloud Drive does<\/em> get backed up, and I do, in fact, see the files in my Time Machine backups.<\/p>\n

\n

Maxwell notes that Time Machine doesn’t back up folders which are found in iCloud Drive, but in my experience it’s not as simple as that. The rule seems to be that Time Machine does back up the contents of your current iCloud Drive, but only those items which are currently stored locally. Any items which have been evicted to iCloud, and are only represented by local stub files, aren’t backed up.<\/p>\n

[…]<\/p>\n

For Time Machine to be able to back up a file evicted to iCloud Drive, that file would need to be downloaded to local storage first. Imagine having a 512 GB internal SSD, and over a terabyte of documents in your iCloud Drive, almost all of which were evicted from local storage.<\/p>\n<\/blockquote>\n\n

This makes sense and is probably the only reasonable thing for Time Machine to do. But, to me, it’s yet another reason to avoid the Optimize Mac Storage<\/a> option. If your files in iCloud Drive are important enough to sync between devices, they’re probably important enough that you want to have your own backups of them.<\/p>\n\n

Previously:<\/p>\n