Flick

Did anyone ever find an elegant solution for this? I just went from 6.9.2 to 6.10.3 and now I'm having the same issue with Userscripts. Files/folders being created by a downloader script have root/root ownership instead of the prior nobody. Playing havoc with my auto-processing setup. Thanks.

I believe you missed that I said "seemed not to work." It took a few minutes for the system to recognize the new UUID and then the "Array" label went away and I was able to mount.

So after posting I discovered the "Change UUID" function. It didn't seem to work, but when I went back in just now to get a screenshot for you, the drive now shows as Mountable. I'll need to do this to one more drive, so I'll capture a screenshot there to help you troubleshoot more, if you like, but I'm now content that there is indeed a workaround. Thanks for the super fast follow-up!

At first blush I thought the new "mark as 'Array'" feature was great, as I can see the benefits. However, I have a unique use case and it's tripping me up. Basically, I have an old array drive that was pulled out of the array and replaced with a larger drive. I have a need (don't ask, seriously) to mount this old drive as Unassigned and copy some files from it. I've done this a couple of times in the past, no big deal. Now, however, the new feature blocks me from mounting it. I've poked around for an override option but I don't see one. Suggestions? Thank you, as always, for all your hard work on this! We all appreciate you!

My Excluded Folders entry is this, working fine: /mnt/cache/.appdata/Plex/Library/Application Support/Plex Media Server/Media/,/mnt/cache/.appdata/Plex/Library/Application Support/Plex Media Server/Metadata/ Obviously change the "/mnt/cache/.appdata" part to wherever you keep yours.

Brilliant! I'm going to do this as well. Thanks!

I knocked out /mnt/user/appdata/Plex/Library/Application Support/Plex Media Server/Media/ and that seems to work fine. Once in a blue moon I'll remove it, let the backup take everything, then store the backup elsewhere. That way if I do need to recover, I can pull that snapshot and then the latest as an "incremental" from there.

Had the same issue and this solution resolved it. Thanks!

Yup, that was my issue too. Thanks!

After I upgraded to Unraid v6.4, I moved Pi-hole to its own IP. Since then, many ads are popping up a username/password prompt rather than failing silently or showing a Pi-hole page. Any suggestions? Thank you.

Anyone figure out how to get alerts to go to Telegram? Thanks.

Did you ever figure out how to do this? This is of interest to me as well. Thanks!

To be clear, though, I'd still like the option for incrementals. Seven hours of downtime isn't ideal for a single backup. Thank you.

Backup ran for 7 hours and 11 minutes. Verify and compression both turned off. TAR is 617GB in size. So, for doing a full backup, I am indeed impressed. I don't mind not having compression turned on but not having verify makes me a wee bit nervous. That would double the time, though, so I guess it's a trade-off. Now if I could just figure out why it insists on creating a new folder called "Backup" on my disk10 when it completes the backup job. Sigh. (My backups go to disk1\Backups). Thank you again for all your work on this.

I second the request for incrementals. My cache drive is 676GB in total, with the bulk of that being: 476 GB in "/mnt/user/.appdata/Plex/Library/Application Support/Plex Media Server/Media/" 106 GB in "/mnt/user/.appdata/Plex/Library/Application Support/Plex Media Server/Metadata/" Sure, I could exclude those during my regularly scheduled backup, dropping my backup to only 94GB but, since I have the space, I'd rather keep them backed up so that if I do lose the cache drive, Plex won't have to download/transcode/whatever all of that again. That's over half my monthly data cap on data that's pretty consistent, hence the v1 plug-in approach of renaming the oldest and then just updating the diff worked really well. Still took several hours to run, though, making me nervous about how long this new method is going to take. I did indeed have cache drive failure earlier this year and your v1 plug-n saved my bacon! Unfortunately, though, it's now been throwing errors so each backup has "-error" at the end and I can't figure out the reason. I saw this thread about v2, figured I was one of the ones affected and went ahead and upgraded. First backup scheduled to run tomorrow night, so fingers crossed! Overall, though, to be clear - *thank you* for providing this plug-in! It's a life saver!