arretx Posted February 27, 2023 Posted February 27, 2023 I've gone through some growing pains here as one of my cache drives failed and I wasn't sure how to handle it. In the process I've lost databases and had to re-install some docker containers. I currently have docker and vm's disabled. I've set Prefer:Cache for /appdata, /domains, /isos, and /system, yet each of these shares have files both in the cache pool and disk1. The mover reports a bunch of existing files, and ultimately leaves some files on disk1 when it's complete. If this is normal, I'm okay with it, but what I don't know about is what would happen if I ran a restore from my CA_backup from a week or so ago before this all happened. When the cache pool failed, I set the cache for these folders to Yes, shut everything down, then ran a move to get everything off the cache. The problem was that I re-enabled the VM's and Docker before setting cache to NO, so the cache started to populate with data again, so now there's information split between the two. Any advice on the next steps to take to clean up the mess? I'd like /appdata, /domains, /isos, and /system to be 100% on the cache so I can run a backup routine on it every night and ensure that I get everything. Thanks! Quote
apandey Posted February 27, 2023 Posted February 27, 2023 26 minutes ago, arretx said: The mover reports a bunch of existing files, and ultimately leaves some files on disk1 when it's complete Does enabling mover logs give any more useful details? Mover won't move any open files or firs connected via terminal 28 minutes ago, arretx said: I'd like /appdata, /domains, /isos, and /system to be 100% on the cache Set cache to "only", then run mover while docker / VM service is stopped Quote
Solution itimpi Posted February 27, 2023 Solution Posted February 27, 2023 3 hours ago, apandey said: 3 hours ago, arretx said: Set cache to "only", then run mover while docker / VM service is stopped That will not do anything as mover ignores shares which are set to ‘Only’. I suspect the current issue is that due to earlier activity some files exist on both the cache and the array. Mover will not overwrite an existing file. Such a situation needs to be cleaned up manually and it is up to the user to decide whether the copy on the cache or the copy on the array is the one to keep/ 1 Quote
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.