![]() Each "hourly" backup takes 30+ minutes to complete, even though the amount of data backed up each time is under 2GB. I'm asking because I'm trying to diagnose slow Time Machine incremental backups on my late-2015 MacBook Pro running High Sierra. "sometimes TM does XXX, sometimes YYY") then what are the reasons why TM would be making many filesystem calls for each unchanged file in a folder? If the answers to the questions above vary (e.g.to fetch a directory listing? Or will it make 1+ calls per file to pull additional info like file contents, attributes, etc.? ![]() What filesystem API calls does Time Machine use to check which files have changed? Specifically, does it make one (or a small number) of calls per folder, e.g.in a folder with 1 changed files and 999 files unchanged since the last backup) does TM use to determine which files are same as the last backed-up version? Does TM look only at file size & modification time? Does it actually read file contents? Does it read file attributes? What information about each file (e.g.I'm looking for a detailed technical explanation, not high-level info about Time Machine itself. What I don't know is what TM does when it learns that 1+ files in a folder have changed. How does Time Machine (on a High Sierra MacBook Pro with APFS) know which files in a folder have changed since the last backup? I know that TM relies on FSEvents to watch for directories with changed file(s).
0 Comments
Leave a Reply. |