SirCadian

Thanks, I'll keep an eye out for updates. In the meantime, if I change to stopping all containers, backing up and then restarting all containers...do PreBackup or PostBackup run in the window while the containers are stopped? I'm assuming not.

A few quick questions about scripts: Do pre-run and post-run execute before/after appdatabackup does anything at all, so right at the start and end of the whole backup process? Are pre-backup and post-backup run per docker container, so if I have 10 containers they will run 10 times? Are pre-backup/post-backup run after a container has been stopped and before it is restarted? Are any parameters passed to the scripts? It would be useful to have the current backup directory name and the current container directory name passed via parameters. Currently I work out the current backup directory name by just grabbing the most recently created directory like this "BACKUPDIR=$(ls -td /mnt/user/Backups/appdatabackup/* | head -1)" but that feels like a bit of a kludge. Essentially, I'm trying to get a working remote backup of appdata to Backblaze using Duplicacy to de-duplicate. At the moment, appdatabackup wraps everything up into per-container tar files. This is fine/preferable for local backup but because each tar file probably contains at least one changed file, every tar file is different from the previous backup and the entire contents of appdata (~70Gb for me) gets uploaded every time I run the backup. I plan to use a pre-backup script (assuming it runs after each container has been stopped) to copy the container appdata directory to a local backup location and then using a scheduled Duplicacy backup to send the files to Backblaze. That should give me local tar backups from appdata backup and a nice versioned de-duplicated backup on Backblaze that makes efficient use of my cloud storage and network connection.

This would be amazing. Currently my Duplicacy backup has to upload ~70Gb to my S3 bucket every time I backup my appdatabackup folder remotely. I've been considering writing a user-script to extract all the tar backups into individual folders ahead of the Duplicacy backup to reduce the load on the network. Having that functionality native to the plugin would be better/cleaner.

I've been looking into remote backup of my Flash and Appdata backups. My Appdata folder is quite large (~65Gb) largely thanks to the PhotoPrism folder (34Gb). As a consequence, I'm reluctant to store multiple copies of the backups remotely as remote storage can be costly. I'd rather have a few daily backups locally and one remotely for that "just in case the house burns down" scenario. The issue is that the Appdata plugin stores the Appdata backups in a unique date and timestamped directory (format: ab_'datestamp'_'timestamp'). Whilst the flash backup file itself is stored in the unique backup directory, it also has a unique filename that is date/timestamped (format: 'server-name'-flash-backup-'datestamp'-'timestamp'.zip). All other docker appdata backup files are uniformly named and don't change ('container-name'.tar.gz & my-'container-name'.xml). This means, if I try to send the backups to a Backblaze B2 storage bucket, a full copy of the Appdata and Flash backups will be kept per day. That's going to quickly get pretty expensive. With that in mind, I've created a small bash script to run after the backups complete which will identify the latest backup directory and copy it to a static directory ('ab_latest'). It then renames the Flash backup in that directory to a static filename ('server-name'-flash-backup.zip). After that has completed a scheduled Duplicacy backup will run and send an encrypted version of 'ab-latest' up to the Backblaze B2 bucket. The bucket is configured to only store one version of each file to keep storage size down. I'm in the process of running the initial backup now and will schedule future ones to run maybe monthly. Appdata seems pretty volatile and the size of most of the backups seem to change each night. I don't want to engage in a +60Gb upload more regularly than that. My question is this; is this the most sensible way to approach remote backup of Appdata & Flash? It seems a little bit more complex than necessary for something I imagine a lot of people want to do? Is there an easier way to handle this in the Appdata plugin so that I can retain multiple nightly backups and back up the most recent remotely?

Just in case anyone else has this problem, I found the answer in this reddit thread. I had to amend the LAN_NETWORK container variable in the binhex-privoxyvpn docker container to add my wireguard local tunnel network pool (you can find this in Unraid Settings - VPN Manager). So, assuming your LAN range is 192.168.1.0/24 and your Wireguard Local Tunnel Network Pool is 10.253.0.0/24 then you should set it as follows. Hope this helps anyone having similar problems.

I have an issue that I would welcome some assistance on. I have a number of docker containers set to route traffic through a binhex-privoxyvpn container using the '--net=container:binhex-privoxyvpn' flag in the extra parameters section. All of that works well and traffic for the dependent containers routes through the binhex-privoxyvpn container network as expected. I've set up the VPN input ports and can access the WebUI for each of the containers. So far so good... I've also set up a wireguard tunnel to my Unraid server using the 'remote access to LAN' access type. When connected through the tunnel I couldn't access my Pi-Hole container or any of the dependent containers running their traffic through binhex-privoxyvpn. I read around a bit and followed the wireguard instructions for configuring complex networks here so that I can get access to dockers with custom IPs. This worked for my pi-hole container which was inaccessible prior to the above changes (a tracert hung at 10.253.0.1) but is accessible post change (I can see the Pi-Hole WebUI and tracert shows the traffic being routed on to the container appropriately). The changes above did not fix the issue for any containers routed through binhex-privoxyvpn. I'm still unable to access the containers when connected to my network through a wireguard tunnel. Any suggestions as to what I need to do here to be able to access the WebUI for those containers?

I have a very strange issue and I'm hoping someone knows the root cause. I have a share set up in Unraid for my photos. That share is accessible over SMB. When accessing it over SMB, I can see three files. When I browse to the share from the Unraid shares tab, I can only see one of the files. Accessing the directory via a terminal as root, I can see all three files. If I look at the ownership and permissions via terminal 'ls -al', all three files have the same owner and permissions. This has meant that, whilst I can see three of my photos over SMB, my PhotoStructure docker container can only see one of the photos. I've run the tool "Docker Safe New Perms" and that didn't fix the problem. I moved the files over SMB onto my PC, deleted them and then copied them back, this didn't fix the issue. I deleted the files, copied them from my PC into a different Unraid share and then used 'mv' in the Unraid terminal to copy them into the Photos share. This fixed the issue, the trouble is that I have no idea why.... I'm concerned that a number of my Photos might be hidden from my docker containers in this way. I have tens of thousands of photos so a manual check is out of the question. Any suggestions as to what the issue was and how I can check to make sure the rest off the files on my Photos share are OK?

Thanks. I followed the instructions on editing myservers.cfg in this post. Issue is now fixed.

Does anyone know how to change the profile picture in the dashboard? It looks like it links out to my forum profile pic, which is fine. I've tried changing it in a number of places but I still get a missing image, as below. Help would be much appreciated...it's bugging the heck out of me!

Sent via DM. Thanks for this.

Will do. I ran with test logging enabled last night to provide you with the diagnostics. Parity Check Tuning updated overnight at 5.15am but not until after Appdata Backup concluded at 4.50am. Parity Check did not resume but that's probably because PCT hadn't been updated at the point Appdata Backup finished. I'll leave everything as is and see if the new update fixes things and if not, I'll dm you the diagnostics. I'll post here either way. Thanks.

Will do. Thanks.

Quick question. I've got my Parity Check set to run once a month and Parity Check Tuning ensures it runs between 1am and 9am each day. It's also set to pause when Appdata Backup is running (@4am each day) but it does not automatically resume once Appdata Backup concludes (usually around 5am each day). The tooltip suggests that it should resume as it is still within the increment window of 1am to 9am. Have I misunderstood?

Hopefully there's a simple answer to this question. I run both Appdata Backup and Parity Check Tuning. My Parity Check runs once a month and I've set up Parity Check Tuning to split that into chunks so that it only runs between 1am and 9am each day until finished. It's also set to pause when Appdata Backup is running, which happens between 4am and 5am (approx). I've written a short script to resume Parity Check once Appdata Backup concludes and it runs fine but I get an error in the logs saying that the script did not return 0. I think I've set the script up to do that but it doesn't seem to work. Have I got something wrong here? #!/bin/bash parity.check resume exit 0 I'm relatively new to Linux so I've probably just got something wrong with the exit code here. Thanks for the help.

I've got "Resume array operations on next array start" set to yes. I'll PM you the diagnostics.

I have the Parity Check Tuning plugin and have the parity check scheduled to run incrementally overnight. It starts at 1am and pauses at 9am each night until the parity check completes. I had cause to reboot the server yesterday during the day. The parity check was paused at 64% from the previous night. Parity check did not resume last night as I would have expected. Is there a setting I'm missing here?

Good to know. That might be an issue for me. I tend to use download so that I can watch films on flights etc. Think I'll need to do some testing with that as I "only" have 32Gb of RAM with about 10Gb of that in use. I was planning on a 10 - 16Gb RAM drive.

Cool. I'll give it a punt. Thanks.

I mean if I don't use the tmpfs suggestion above. I've got 32Gb RAM which is usually around 30-40% utilised. My understanding is Plex won't clean up until the transcode location is full. If the transcode location is /tmp that's effectively my RAM without limitation? Seems much more sensible to me to create a ram drive of fixed size. I like the idea of using a user-script. I think I'll do it that way as it's visible in the UI. Thanks for the suggestion.

I'm thinking about implementing transcoding in RAM for plex but also run HD Homerun and suspect i'll run into RAM issues. I'm a relative linux newbie but have been running with Unraid for a year and a half at this point so my knowledge is improving. I'm not a fan of implementing stuff without understanding what it's doing. I get what all the commands above do and how to map the temp ram drive in Plex. What I don't understand is, what is a "go" file? A quick google tells me it sits in /boot/config for Unraid. There's not a right lot in mine at the moment. Is it essentially just a shell script that runs on boot? Also, once I've edited the go file, I assume I either need to reboot my unraid server or manually type in those commands before I'll be able to map the drive in Plex? Thanks for the help.

I have a question about configuring Privoxy VPN now that Unraid supports User Defined Networks for Docker. Currently I have binhex-privoxyvpn set up on a user defined network. I route a number of other containers through it using the extra parameter '--net=container:binhex-privoxyvpn'. I have VPN Input & Output ports set up as necessary and have added additional ports for each container. Everything works fine. Is this still the best way to have privoxyvpn set up now that we have access to user defined networks? Recently I've been having issues with my VPN provider and have been considering how to easily swap VPN node or provider. At the moment I'd have to either drop a new OVPN file into the config/openvpn folder and restart the container (which will restart all the dependent containers) or stop the binhex-privoxyvpn container, start up a 'vpn_failover' container and manually alter the extra parameters on each of the dependent containers to point to the new vpn container. Neither option is particularly quick and I'm wondering if there's something I'm missing here. Is there an easy/quick way to change the VPN that multiple containers route through?

You, Sir, are a god amongst men. Thanks!

Also moved to the AnalogJ image. Works as expected. I didn't consider that I would lose my historical data in the move. Not a big issue but worth noting.

I had done that, I cleared all cookie data associated with the IP:Port. That didn't fix it. I would guess that there must be some data not stored under the standard port for VNC that needs clearing. Bizarrely the issue seems to have fixed itself though. I tried to log on tonight to investigate further and it just worked...which is great...but I'd liked to have got to the bottom of why it was happening. Ho hum.

Yes. I'd like to get it working in standard browser window though...