APPLICATIONS: keep away from that com.pple.Find scan my time machine unit?

After deepening this, I found that the com.apple.find activity (/System/Library/LaunchDaemons/com.apple.find.plist) launches a script in /usr/libexec/find.updatedb.

Seems inside that script that the volumes of the time machine are meant To be excluded, nonetheless, the way in which to match them is */Backups.backupdb" that solely coincides with the previous -style time machine volumes (HFS+), since APFS time machine volumes are structured very in another way.

The right answer to this drawback can be to supply totally different exclusion guidelines, however each the launching activity and the script are lined by the integrity safety of the system, though there’s a technique to keep away from this.

One other a part of the issue is that backupd It has the behavior of leaving mounted snapshots /Volumes/.timemachine When he not wants them, which appears to be the place he discover The method is getting caught, so the dismantling of those gives one other potential answer.

Subsequently, this affords two potential options (each would require that it registered as root to do that, if you happen to have no idea how or you don’t really feel snug with the command line, you might have to attend for Apple to resolve this):

Add customized exclusions to /usr/libexec/find.updatedb

1. Copy /usr/libexec/find.updatedb to a different location (similar to /usr/native/lib)
2. Discover the road: : ${PRUNEPATHS="/personal/tmp /personal/var/folders /personal/var/tmp */Backups.backupdb"} # undesirable directories
3. After */Backups.backupdb add /Volumes/.timemachine So: : ${PRUNEPATHS="/personal/tmp /personal/var/folders /personal/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. Obtain the earlier activity utilizing: launchctl unload -w /System/Library/LaunchDaemons/com.apple.find.plist
7. Load your alternative activity utilizing: launchctl load /Library/LaunchDaemons/com.apple.find.plist

EITHER

Excellent snapshots

1. Flip off computerized backup copies of the time machine in system preferences.
2. Create a launch activity that prompts the time machine and clear the snapshot assemblies later (then see a pattern activity).
3. Load the launching activity with: launchctl load /Library/LaunchDaemons/customized.backup.plist

/Library/LaunchDaemons/customized.backup.plist

    Label
    customized.backup
    ProgramArguments
    
        bash
        -c
        <!(CDATA(
if tmutil startbackup --auto --block --rotation; then
    mount | grep -o '/Volumes/.timemachine/.*.backup' | whereas learn mountpoint; do
        diskutil unmount ${mountpoint}
    accomplished
fi
))>
    
    StartCalendarInterval
    
        Minute
        0
    

This can execute the time machine each hour, on the time (or after waking up, in case your pc was asleep at the moment), and after working efficiently you’ll search for all snapshots mounted on /Volumes/.timemachine And attempt to disassemble them, so com.apple.find You can’t index them.

Whereas this selection is a bit cleaner com.apple.find It is not going to be executed whereas the snapshots are nonetheless mounted, though with the clear frames, the chance that it’s low.