January 22, 20224 yr Hi folks, I've found countless threads asking about adding a SECOND drive to a cache/pool, however my initial setup was 4 HDDs in an array with no cache or pool. I've only just added two 1TB NVMe SSDs as a cache for the first time. I run plenty of Docker apps so I have a pre-existing appdata share. I have a VM (domain controller) as well so I also have a pre-existing domains share. I added the two SSDs without problem. Set them up in the cache pool. I went into Shares and edited each of my data shares Use Cache Pool: to Yes. My intention is for all data shares to use this pool as a cache, then copy the data to the array later. I also set appdata, domains, and system shares to Cache: Only. My intention is for all Docker apps and my DC VM to run directly off the cache pool for performance. Per the docs, this SHOULD copy files for these shares to the cache, however from what I understand this will only work if the files are not in use. How likely is it the mover will do anything at all if my Docker apps and VM are running overnight? Should I instead shut everything down and manually copy from the array to the cache, then fire it all back up? Thanks for reading!
January 23, 20224 yr 10 hours ago, keiser said: How likely is it the mover will do anything at all if my Docker apps and VM are running overnight? None since : nothing can move an open file and shares set to ONLY and NO are not considered when running the mover You should probably set appdata, domains and systems to Prefer anyway and set a Minimum free space on your cache Pool so it cannot get full and damage the file system.
January 23, 20224 yr 10 hours ago, keiser said: Should I instead shut everything down and manually copy from the array to the cache, then fire it all back up? Either move manually or with the mover.
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.