Hi all,

 

I'm a long time unraid user but i'm using a cache drive for the first time and i'm not sure if i'm using the recomended configuration for appdata because i'm getting the warning "some or all file unprotected":

 

 

I just have 1 one cache drive and previously the appdata was in the array. This is the reason for the warning?

 

The system share as a warning also and it is set with array->cache option. Is the same case?

 

Thanks in advance.

 

 

 

If your cache pool is a single drive then it is expected that the appdata share will show as some or all files unprotected as the cache has no redundancy if it is a single drive pool  The whole idea of keeping appdata on the cache is to maximise performance and to avoid spinning up array drives unecessarily.   You want to install the Appdata Backup plugin to make regular scheduled backups to the main array,

 

Note that you also want to make sure the System share is also on the cache drive for best performance.

And the best configuration for appdata is Array->Cache or Cache->Array? 

7 hours ago, Duarte said:

And the best configuration for appdata is Array->Cache or Cache->Array? 

You normally want array->Cache as you get better performance if the files are on the cache.

Hi all,

Managed to get myself in a little pickle.  The appdata share is now residing primarily on the cache only and not on the array.

 

All docker containers have the default location: /mnt/cache/appdata/

 

Whats the best steps to stop all dockers, and fix the appdata share up and migrate the dockers to all be primarily on the array then secondary as cache?

 

Thanks,

Dwarfboysim

 

PS: Have about 25 dockers

 

1 hour ago, Dwarfboysim said:

The appdata share is now residing primarily on the cache only and not on the array.

Why do you want them on the array - they perform much worse if they are there.   It is normal to want them on a pool (e.g. cache) to maximise performance and allow array disks to be spun down when not in use.

2 hours ago, itimpi said:

Why do you want them on the array - they perform much worse if they are there.   It is normal to want them on a pool (e.g. cache) to maximise performance and allow array disks to be spun down when not in use.

Wouldnt I want them on the array at some point at least to offer backup.  I do also have the appdata backup add on

 

9 minutes ago, Dwarfboysim said:

Wouldnt I want them on the array at some point at least to offer backup.  I do also have the appdata backup add on

 

Any file can only be in one location at a time so it cannot be on both cache and array at the same time..  The appdata backup plugin is the standard way to make a backup of a share that is completely on a pool (cache).

So should I just have the Primary storage for appdata set to Cache and no secondary storage.  Then use the appdata backup plugin to back these up to a place on the array?

No secondary is fine if you don't fill up that pool. That is what I do, but I have plenty of space in the pool appdata is on.

Appdata and dockers are best left on a cache pool. Use the appdata backup plugin to make backups and have those backups stored on your array.

 

Appdata share:
Primary: (name of your cache pool here)

Secondary: None

 

What ends up happening if dockers and appdata are located on the array is that any time you start writing data and parity is calculating, your dockers become non-responsive due to the IO taking place.

Edited April 30, 20251 yr by MowMdown

On 12/3/2023 at 9:50 PM, itimpi said:

You normally want array->Cache as you get better performance if the files are on the cache.

could you help me here: i have the same setting as mention in the screenshot above (cache 1x disk 1TB and array 2x disk 1TB each) but i don't get the setting if:
primay = cache
second = array

why mover need to transfer array -> cache, means this, files often request will be move back to cache?

13 minutes ago, lex87 said:

could you help me here: i have the same setting as mention in the screenshot above (cache 1x disk 1TB and array 2x disk 1TB each) but i don't get the setting if:
primay = cache
second = array

why mover need to transfer array -> cache, means this, files often request will be move back to cache?

New files are first written to primary storage, then, when mover moves those files, they are permanently relocated to the secondary storage.

What happens when mover is set to Array -> Cache, those files are brought back to Cache pool in case of an overflow when the cache pool runs out of writable space.

Edited September 1, 2025Sep 1 by MowMdown

35 minutes ago, lex87 said:

why mover need to transfer array -> cache, means this, files often request will be move back to cache?

This only applies if the cache pool filled up and so the share overflowed and was written to the array. In such a case when if space subsequently becomes available on the cache then mover moves files from the array to the cache. It has nothing to do with how often a file is requested.