make array only spin op when mover is invoked

[Theflygamer]

I have a Cache drive in my server that want to be only (drive) active 24/7 my array should only spin up when the mover is invoked or if data is needed in a VM/Docker else the HDD´s are spind down I have tried many setting on my shares but nothing seems to make the array stay spined down

[trurl]

Depending on the settings of your User Shares that should be possible, assuming your cache has enough capacity to take all writes between mover runs.

 

Probably you have some shares on the array with open files, such as for VMs/Dockers.

 

Attach diagnostics to your NEXT post in this thread.

[Theflygamer]

here is the diagnostics file =>

 

also a picture of the shares (but igeuss you can see that ind the file) 

tower-diagnostics-20220412-0008.zip

[itimpi]

The moment you have files for the 'appdata' and 'system' shares on disk1 when you really want them on the cache to avoid spinning up array drives.  The following should rectify this:

• Set the 'appdata' Use Cache setting to Prefer.  (you may want the Domains share set to Prefer as well to put VM related vdisk files on the cache).
• Disable the VM and Docker Services so they do not hold files open (which stops them being moved)
• Run Mover by clicking on it on the Main tab to get files moved to the cache.
• When mover completes re-enable the Docker and VM services

 

[ChatNoir]

Then post new diags.

[Theflygamer]

looks like the array stays spin downed now :)) 

 

just a few questions when the mover runs next time all the new data will be but on the array (protected) ??

 

and if data is needed from the array it will spin up and provide the nessesay data

 

 

@ChatNoir NEW diagnostics file 

tower-diagnostics-20220412-1419.zip

[itimpi]

7 minutes ago, Theflygamer said:

just a few questions when the mover runs next time all the new data will be but on the array (protected) ??

Not for shares that have the ‘prefer’ or ‘only’ Use Cache setting so their contents is kept on a pool (unless the pool in question is itself redundant).  Their are plugins to automate backing up docker containers and VM vdisks from a pool to the array.

 

Shares set to ‘yes’ or ‘no’ in their Use Cache setting will end with their content up on the array.

[ChatNoir]

There is still something on the drives for appdata and isos.

It might be an empty directory. You can check, if it is an empty directory, do you know how to delete it ?

[Theflygamer]

okay so i should set them all to YES or use a plugin in that case can you recommend a plugin ? 

[Theflygamer]

@ChatNoir there is somthing on the 2 shares but the array stays spin down so all good :))

[trurl]

On 4/12/2022 at 8:40 AM, Theflygamer said:

okay so i should set them all to YES

No, appdata, domains, system shares should be cache-only or prefer so they will stay on fast pool (cache). If they are on the array your dockers and VMs will not perform as well and will keep array disks spinning since these shares always have open files.

 

If these files are on fast pool (cache), and you have duplicates on the array, then those on cache would be accessed instead, and those on the array can be deleted.

 

Looks like your appdata has files or folders on the array. You can delete those after you check to make sure those on cache are indeed the ones you want to keep.

 

Do you know how to work with files on the disks? File Manager plugin is probably the best reason to upgrade to 6.10rc