![]() Not the outdated full-screen TM UI that we have now. I'd much rather pick a file, see a list of previous versions of that file with previews, and maybe a diff, all integrated properly into the Finder. So wasting 2x space for one identical file.Īlso TM is sluggish on networked disks and the UI is pretty awful. Change the title of that file and the entire thing gets copied across again, without the other file being deleted on the backup. For a 1kb file that doesn't matter, but nowadays with file sizes ballooning, 1GB+ files are pretty common. A snapshot stores only the block-level difference between files, whereas Time Machine copies the entire file across again even if there's one single bit changed. Whether APFS supports this right now, I'm not is completely right with his comment. However, snapshots don't technically have to be stored on the source drive. How would an APFS snapshot on the same physical disk save your data from the failure of said disk? These backups are called local snapshots. ![]() Your Time Machine backup disk might not always be available, so Time Machine also stores some of its backups on your Mac. Why aren't they retiring this antique approach to back-ups? I mean, they now have a filesystem that supports snapshots Time Machine lets you restore files from local snapshots of the files on your Mac, even when your Time Machine backup disk isnt available.
0 Comments
Leave a Reply. |