functions – Stop com.apple.find from scanning my Time Machine drive?

After digging into this additional myself I discovered that the com.apple.find job (/System/Library/LaunchDaemons/com.apple.find.plist) launches a script at /usr/libexec/find.updatedb.

It seems inside that script that Time Machine volumes are supposed to be excluded, nonetheless the trail for matching them is */Backups.backupdb" which solely matches old-style (HFS+) Time Machine volumes, as APFS Time Machine volumes are structured very in another way.

The right answer to this drawback can be to offer completely different exclusion guidelines, however each the launchd job and script are lined by System Integrity Safety, although there’s a means round this.

One other a part of the issue is that backupd has a behavior of leaving snapshots mounted below /Volumes/.timemachine when it now not wants them, which seems to be the place the discover course of is getting caught, so unmounting these supplies one other doable answer.

So this provides two doable options (each would require you to be logged in as root to do that, if you do not know how or will not be snug with the command line then you might simply have to attend for Apple to repair this):

Add Customized Exclusions to /usr/libexec/find.updatedb

1. Copy /usr/libexec/find.updatedb to a different location (akin to /usr/native/lib)
2. Discover the road: : ${PRUNEPATHS="/non-public/tmp /non-public/var/folders /non-public/var/tmp */Backups.backupdb"} # undesirable directories
3. After */Backups.backupdb add /Volumes/.timemachine like so: : ${PRUNEPATHS="/non-public/tmp /non-public/var/folders /non-public/var/tmp */Backups.backupdb /Volumes/.timemachine"} # undesirable directories
4. Copy /System/Library/LaunchDaemons/com.apple.find.plist to /Library/LaunchDaemons
5. Edit /Library/LaunchDaemons/com.apple.find.plist to level to your customized script (/usr/libexec/find.updatedb to /usr/native/lib/find.updatedb).
6. Unload the outdated job utilizing: launchctl unload -w /System/Library/LaunchDaemons/com.apple.find.plist
7. Load your substitute job utilizing: launchctl load /Library/LaunchDaemons/com.apple.find.plist

OR

Unmount Leftover Snapshots

1. Flip off computerized Time Machine backups in System Preferences.
2. Create a launchd job that can set off Time Machine, and cleanup snapshot mounts afterwards (see beneath for a pattern job).
3. Load the launchd job with: launchctl load /Library/LaunchDaemons/customized.backup.plist

/Library/LaunchDaemons/customized.backup.plist

       Label     customized.backup     ProgramArguments              bash         -c                   StartCalendarInterval              Minute         0        

This can run Time Machine each hour, on the hour (or after waking, in case your laptop was asleep on the time), and after operating efficiently it can search for all snapshots mounted below /Volumes/.timemachine and attempt to unmount them, so com.apple.find will not have the ability to index them.

Whereas this selection is somewhat cleaner (and is helpful if you’d like extra management over when Time Machine runs and what occurs earlier than and after it does) it has the draw back of timing since there isn’t any assure com.apple.find will not run whereas snapshots are nonetheless mounted, although with the mounts being cleaned up the prospect of that ought to be low.