So I've read a couple conflicting articles on how Time Machine backups are affected by Sierra's new "Store in iCloud" feature - in summary:
Pre-Sierra, a user could have potentially 3 copies of a file: locally, in iCloud, and via Time Machine backup.
With Sierra's "Store in iCloud" enabled, some explain that if a file is in the Desktop or Documents folder (now synced to iCloud), potentially only one copy that will exist (iCloud), as it may eventually be removed from local storage, and as a result, will no longer be backed up by Time Machine. This is not to mention the difference between iCloud file storage and Time Machine versioning storage. Others explain that Time Machine will still back up these "iCloud-only" files, by Sierra downloading them as necessary for this purpose.
I've gotten no positive confirmation on any forums or Apple support site on what's actually going on, so I'll throw this idea out there and see if anything sticks:
Sierra Time Machine Paradigm (assuming an "always-connected" TM solution, or Time Capsule)
1. Mac is updated to Sierra (all local files still local)
2. Time Machine backs up all local files as usual
3. Sierra "optimizes" old files, removing them from local storage
3.a. At this point, Time Machine does not need to back up these old files again, as they are unchanged from (2).
4. User makes changes to "optimized" file on Mac: Sierra downloads file for editing; is now in iCloud AND local
4.a. Time Machine backs up this new version of the file, as it is now local
4.b. Time Machine has now backed up the two versions of this file (versions in step 2 and step 4)
So with this explanation, even with "Store in iCloud" enabled, a user still has at least 2 copies of the file (TM and iCloud), even if the file becomes "old" and "optimized" again.
So my questions are:
a) Can anyone confirm this behavior, and
b) What if step 4's file change was done by an iOS device, instead of the Mac? Would the file then become "recent" to all iCloud devices and thus be downloaded locally to each device (to then be backed up by TM)?
Sorry this is so wordy, but *every* attempt by tech sources to explain how this works has been very wordy, and unclear (which points to Apple's inability to keep a "simple" feature "simple.)
Pre-Sierra, a user could have potentially 3 copies of a file: locally, in iCloud, and via Time Machine backup.
With Sierra's "Store in iCloud" enabled, some explain that if a file is in the Desktop or Documents folder (now synced to iCloud), potentially only one copy that will exist (iCloud), as it may eventually be removed from local storage, and as a result, will no longer be backed up by Time Machine. This is not to mention the difference between iCloud file storage and Time Machine versioning storage. Others explain that Time Machine will still back up these "iCloud-only" files, by Sierra downloading them as necessary for this purpose.
I've gotten no positive confirmation on any forums or Apple support site on what's actually going on, so I'll throw this idea out there and see if anything sticks:
Sierra Time Machine Paradigm (assuming an "always-connected" TM solution, or Time Capsule)
1. Mac is updated to Sierra (all local files still local)
2. Time Machine backs up all local files as usual
3. Sierra "optimizes" old files, removing them from local storage
3.a. At this point, Time Machine does not need to back up these old files again, as they are unchanged from (2).
4. User makes changes to "optimized" file on Mac: Sierra downloads file for editing; is now in iCloud AND local
4.a. Time Machine backs up this new version of the file, as it is now local
4.b. Time Machine has now backed up the two versions of this file (versions in step 2 and step 4)
So with this explanation, even with "Store in iCloud" enabled, a user still has at least 2 copies of the file (TM and iCloud), even if the file becomes "old" and "optimized" again.
So my questions are:
a) Can anyone confirm this behavior, and
b) What if step 4's file change was done by an iOS device, instead of the Mac? Would the file then become "recent" to all iCloud devices and thus be downloaded locally to each device (to then be backed up by TM)?
Sorry this is so wordy, but *every* attempt by tech sources to explain how this works has been very wordy, and unclear (which points to Apple's inability to keep a "simple" feature "simple.)