dopeytree Posted October 20, 2022 Share Posted October 20, 2022 (edited) Possible could get this added via mover tuning but it would be great to have mover settings per share. So for example I want my backups share to move to the array as soon as possible but I want my plex downloads to hang around on the cache for 30days... at the moment I have not found a way to do this. Also we need some kind of simple GUI for mover progress Edited October 20, 2022 by dopeytree 1 Quote Link to comment
-Daedalus Posted October 26, 2022 Share Posted October 26, 2022 +1 I have exactly the same use-case. I tried shoehorning something like this with Mover Tuning, but not possible. Quote Link to comment
kizer Posted October 27, 2022 Share Posted October 27, 2022 On 10/20/2022 at 3:23 PM, dopeytree said: Possible could get this added via mover tuning but it would be great to have mover settings per share. So for example I want my backups share to move to the array as soon as possible but I want my plex downloads to hang around on the cache for 30days... at the moment I have not found a way to do this. Also we need some kind of simple GUI for mover progress Easy do like I did. Set up your user share to backup to the array vs SSD. You can't get any more instant than that. Quote Link to comment
dopeytree Posted October 27, 2022 Author Share Posted October 27, 2022 6 hours ago, kizer said: Easy do like I did. Set up your user share to backup to the array vs SSD. You can't get any more instant than that. So write the backup share to array and skip any ssd caching? I.e new files go straight to array. and mover is not involved? Quote Link to comment
kizer Posted October 28, 2022 Share Posted October 28, 2022 20 hours ago, dopeytree said: So write the backup share to array and skip any ssd caching? I.e new files go straight to array. and mover is not involved? Yep, can't be any more "move to the array as soon as possible" than that. Quote Link to comment
Andiroo2 Posted January 23, 2023 Share Posted January 23, 2023 I'd love to see per-share mover settings as well. I have a similar use case...I want my Appdata backups (~300GB file) to write to the cache, and then stay on the cache while it's transferred to my external storage. I want to benefit from the fast read and write for the backup processes. Once that's done, the mover can move that huge file onto the array so it's not soaking up valuable NVMe cache space. Quote Link to comment
NGHTCRWLR Posted February 10, 2023 Share Posted February 10, 2023 +1 to Mover Settings per Share Quote Link to comment
trurl Posted February 10, 2023 Share Posted February 10, 2023 On 1/23/2023 at 5:38 PM, Andiroo2 said: the mover can move that huge file onto the array so it's not soaking up valuable NVMe cache space. Actually, you want appdata, domains, and system shares to stay on cache or other fast pool and not on the array, so Docker/VM performance won't be impacted by slower array, and so array disks can spin down since these files are always open. 8 minutes ago, NGHTCRWLR said: +1 to Mover Settings per Share Each share already has settings that control what mover does with its files. 1 Quote Link to comment
Andiroo2 Posted February 10, 2023 Share Posted February 10, 2023 (edited) 1 hour ago, trurl said: Actually, you want appdata, domains, and system shares to stay on cache or other fast pool and not on the array, so Docker/VM performance won't be impacted by slower array, and so array disks can spin down since these files are always open. Oh I keep those on cache…I’m referring specifically to my backups that I want to move off the server quickly after creation and then archive them on the array for safe keeping. Edit: I’ve manually implemented this by calling the per-share mover script via scheduled task: find "/mnt/cache/CommunityApplicationsAppdataBackup" -depth | /usr/local/sbin/move -d 1 Edited February 10, 2023 by Andiroo2 Quote Link to comment
Swarles Posted June 15, 2023 Share Posted June 15, 2023 +1 Anyone know if there is a work around to still achieve this? Quote Link to comment
dopeytree Posted June 16, 2023 Author Share Posted June 16, 2023 Mover schedule settings per share would be the easiest way for this to work. Quote Link to comment
-Daedalus Posted June 16, 2023 Share Posted June 16, 2023 Or an option with Mover Tuning to ignore settings and move certain shares on a schedule or something. I have the same issue; I have my backups going to an SSD for write speed, but I don't want them sitting there taking up space that could otherwise be used for frequently accessed files that I'd like to keep on the SSDs for a longer period. Quote Link to comment
Swarles Posted June 18, 2023 Share Posted June 18, 2023 I'm working on implementing this in Mover Tuning 1 Quote Link to comment
Swarles Posted June 20, 2023 Share Posted June 20, 2023 (edited) My implementation is going well, some good news and some bad news! Good News: Per-share mover functionality is fully up and running. GUI created and functional. Initial testing shows expected results. Bad News: The per-share mover settings will run at the same time as the normal mover. There will be no separate mover schedules. It will only work for cache-->array moves (shareUseCache="yes"). This is because the current Mover Tuning Plugin only uses the settings for this move (to the best of my knowledge). But I believe this is probably covers 95% of peoples use cases anyway. It's gonna require more testing and validation before release. Supported Settings: AGE: Move based on age. Use CTIME (as opposed to MTIME) SIZE: Move based on min size. Sparseness: Move files based on min sparseness. FILES LIST: Ignore files in a list. <-------- I might remove this one, because it doesn't really make a difference and is more limited FILE TYPES: Ignore specified file types. HIDDEN: Ignore hidden files and directories. Move All From Cache Threshold: Toggle only, threshold set in main settings. Edited June 21, 2023 by Swarles Changed to cache-->array 1 Quote Link to comment
itimpi Posted June 20, 2023 Share Posted June 20, 2023 1 hour ago, Swarles said: It will only work for array-->cache moves (shareUseCache="yes"). That does a cache->array move - I assume you got it backwards Quote Link to comment
Swarles Posted June 21, 2023 Share Posted June 21, 2023 (edited) 4 hours ago, itimpi said: That does a cache->array move - I assume you got it backwards Oh yep sorry! edited lol...wrote that one at 6am after not being able to sleep. 😬 Edited June 21, 2023 by Swarles Quote Link to comment
Swarles Posted July 3, 2023 Share Posted July 3, 2023 On 10/21/2022 at 9:23 AM, dopeytree said: Possible could get this added via mover tuning but it would be great to have mover settings per share. Feature has now been officially released! On 10/21/2022 at 9:23 AM, dopeytree said: Also we need some kind of simple GUI for mover progress I believe hugenbdd has created something like this but it requires some kind of manual implementation for now, you can see the relevant files on his GitHub. 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.