Kloudz

I knew this was an issue that I ran into in the past and resolving it was to just change the share to only write to array. But today I was wondering if this was resolved because I'm tired of my Proxmox performing backups at a slow rate because the share is only going to an 'Array'. You sir are my savior today lol. This resolved the issue where I can use a cache drive in Proxmox. Tried to see if rebooting keeps the setting and Proxmox connects to the share just fine. I also performed backups and what a relief, I can definitely tell its faster.

I'm using the NUT Master Username and password and works fine for me. When heading to Diagnostics, it took a few seconds to show up. Also check your Unraid syslog too, it tells you if theres a successful authentication Followed: https://docs.opnsense.org/manual/how-tos/nut.html

The reason why to use the plugin is a setting that doesnt exist in Unraid. Which is to disable mover while Parity check is running

I was trying to avoid creating a script of my own. I figured someone out there created a plugin by now where you can just do everything in the GUI and this plugin is very close. But thank you for the suggestion, I guess scripting is the way to go

Is there an option to 'Skip All Container Backups' instead of setting each container to Yes to skip the container? Or Is there an option to just back up the Flash Drive without backing up the containers? Having either options would be great if I just want to backup the flashdrive

The new plugin seems to ignore the setting 'Let scheduled mover run during parity/rebuild'. My scheduler is set every 3 months to perform a parity check and my server is running a parity check right now. I have this setting set to 'no'. This morning, I checked its progress and noticed that after 8 hours, the server only has done 2TB of parity check. I told myself thats slow then checked the logs and saw mover moving files during parity check. Has anyone experienced this issue?

love how this still works today

I modified the tuning file and manually set the threshold to 0. This modification resolves my issue. I no longer have to wait for the cache drive to fill up 5% to be considered to move. 0% should definitely be in global setting

There should be a 0% option on the Scheduler page. Minimum is 5%. I like one of the users here always have data coming in and want to move them to the array as soon as the scheduler triggers. On the old plugin version it would move everytime but updating to the new version of the plugin, I have to wait until it hits 5% or manually trigger. Why not have a global setting? Kind of sucks to have to do it on every share

I just want to go back to this. I rebooted my server today to change some bios settings. Mover stopped working. Performed Step #6 and it started working again. Just an FYI not sure if the issue is fixed yet

SWEET! Thank you! Also, one more enhancement that I would like to see is changing the order of the previews. Right now it's Web, Logs, Console. If we can reorder them. I'm a happy camper. Thanks again!

Not sure if someone asked this already but is there a way to add the "Console/CLI" button just like how there's a WebGUI button and Logs button on

Its been a few days, seems to stop working today. The only thing I did today was stop then started my array. Needed to check some configs but didn't make any changes. Anyway, I even added 3 additional files. Triggered Mover via Main screen and nothing. Then I followed your steps that you posted last week and went all the way to Step #6 and its now working again. Something is definitely up here. Just to Recap, since I last posted that it was working. There hasn't been any issues since. But earlier this morning, I noticed theres still a file in my cache drive. Ran Mover like usual and didn't think of any till 5 mins later and noticed that the file was still in the cache. From here, I stopped the Array to check some configs, didn't change anything then started the Array. Ran Mover again and nothing. So I tried to perform all the troubleshooting steps again and went all the way to Step #6 and once I performed step #6. Mover started working again from the Main Screen. Between Steps 1-5, I didn't make any changes until Step #6

Quick update, with Scheduler set, Movers is working as expected. Mover is triggered every 2 hours based on settings. So, not sure what happened.

I've had the movers tuning plugin uninstalled for some time now since I last replied to this thread. Also, I'm sorry I haven't gotten back to anyone. Been busy doing RL stuff lol. That said, I was holding off on installing the Movers Tuning plugin until it's been updated but looks like it hasn't. Anyway, I installed it today. And the first thing I did before doing anything is to see if "/boot/config/plugins/ca.mover.tuning/ca.mover.tuning.cfg" existed. I checked the directory and the ca.mover.tuning.cfg file didn't exist. So I went to Settings > Scheduler > Toggled "Disable Mover running on a schedule" to "Yes" then I toggled it back to "No". Once I did this, the file was created then I toggled "Move Now" from the Main screen and Unraid started Moving files like it should. So not sure what happened here, maybe because ca.mover.tuning.cfg didn't exist? But then again, I was doing some server maintenance like converting my cache pools to zfs. Moving my appdata from a cache to the array then back to cache. Recreated my system folder that has libvert and docker folders. Suffice it to say, it looks like it's working now which is weird. I haven't tested whether or not mover will kick in based on the schedule I set. So I'm waiting for that to happen. Kinda happy, I have the movers tuning plugin installed again. I missed having the ability to disable mover while a parity check was happening. I was due for a parity check. anyway, I think I wrote too much