Not related to your question, but several of your shares are misconfigured, as indicated by Fix Common Problems. Oct 13 23:24:09 Rivendell root: Fix Common Problems: Warning: Share Foundry Data is an implied array-only share, but files / folders exist on the cache
Oct 13 23:24:09 Rivendell root: Fix Common Problems: Warning: Share system is an implied array-only share, but files / folders exist on the cache
Oct 13 23:24:09 Rivendell root: Fix Common Problems: Warning: Share Time Machine is an implied array-only share, but files / folders exist on the cache
Oct 13 23:24:09 Rivendell root: Fix Common Problems: Warning: Share appdata set to cache-only, but files / folders exist on the array
Oct 13 23:24:09 Rivendell root: Fix Common Problems: Warning: Share Documents set to cache-only, but files / folders exist on the array
Oct 13 23:24:09 Rivendell root: Fix Common Problems: Warning: Share Emulators set to cache-only, but files / folders exist on the array
Oct 13 23:24:09 Rivendell root: Fix Common Problems: Warning: Share Files set to cache-only, but files / folders exist on the array
Oct 13 23:24:09 Rivendell root: Fix Common Problems: Warning: Share Macintosh OS set to cache-only, but files / folders exist on the array
Oct 13 23:24:09 Rivendell root: Fix Common Problems: Warning: Share Video set to cache-only, but files / folders exist on the array
Oct 13 23:24:09 Rivendell root: Fix Common Problems: Warning: Share Windows OS set to cache-only, but files / folders exist on the arrayMover will ignore these shares because they have no Mover action because they have no Secondary. Ideally, Docker/VM related shares - appdata, domains, system - will have all files on cache or other pool with none on the array, so Docker/VM will perform better, and so array disks can spin down since these files are always open. Nothing can move or delete open files, so you have to disable Docker and VM Manager in Settings before these shares can be worked with.