Mover settings per share

[dopeytree]

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

[-Daedalus]

+1

 

I have exactly the same use-case. I tried shoehorning something like this with Mover Tuning, but not possible.

[kizer]

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.

 

[dopeytree]

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?

[kizer]

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.

[Andiroo2]

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.  

[NGHTCRWLR]

+1 to Mover Settings per Share

[trurl]

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.

[Andiroo2]

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 by Andiroo2