Nepherim

Did you ever get this working? It looks like you should be able to forward port 55415 from your proxy to your uBackup server. However, I've not been able to get this to work.

Moving backups from one volume to another needs to be done carefully as urBackup uses hard links extensively. I just moved my backups from one unraid disk to another using Unbalance mod, and the -H parameter, and saw a large spike in incremental backup szes, I suspect due to messed up links. Not sure I'd go the route of backing up to cache.

Having moved backup files to a different disk using Unablance plugin and the -H parameter, I'm now trying to clean-up symbolic links with remove-unknown: sh-5.1# urbackupsrv remove-unknown 2022-12-12 22:28:39: Going to remove all unknown files and directories in the urbackup storage directory. Waiting 20 seconds... 2022-12-12 22:28:59: Shutting down all database instances... 2022-12-12 22:28:59: Opening urbackup server database... 2022-12-12 22:28:59: WARNING: SQLite: cannot open file at line 39363 of [3bfa9cc97d] errorcode: 14 2022-12-12 22:28:59: WARNING: SQLite: os_unix.c:39363: (13) open(/var/urbackup/backup_server_files.db) - errorcode: 14 2022-12-12 22:28:59: Could not open db [urbackup/backup_server_files.db] 2022-12-12 22:28:59: ERROR: Database "urbackup/backup_server_files.db" couldn't be opened 2022-12-12 22:28:59: ERROR: Couldn't open backup server database. Exiting. Expecting database at "/var/urbackup/backup_server_files.db" Any ideas? Edit 1: Solution Solution is to ensure the command is running as root user: urbackupsrv remove-unknown -u root

Here's where I'm at in terms of using urBackup as a means to backup Unraid shares. You need to backup a bunch of files and directories, permissions/execute flags are important. After installing urbackup client on your server, use the tar command below to make a copy of the urbackup client. (Use the server to configure paths and other client settings.) This will create a directory on your flash drive /boot/urbackup with the tar file inside: tar -cvf /boot/urbackup/urbackup.tar \ /usr/local/var/urbackup \ /usr/local/bin/urbackupclientctl \ /usr/local/sbin/uninstall_urbackupclient \ /usr/local/sbin/urbackupclient_dmsnaptool \ /usr/local/sbin/urbackupclientbackend \ /etc/default/urbackupclient Then update the /boot/config/go file: nano /boot/config/go and add the following to ensure urBackup is reinstalled and restarted on your Unraid server after reboot. tar -xvf /boot/urbackup/urbackup.tar -C / /usr/local/sbin/urbackupclientbackend -d What I'm now stumped on is how to actually have the client run. Anyone able to help identify where/how to run the client? My local client uses systemd, which isn't what unraid uses, so kind of stumped at this point. Edit 1: updated to add: Here's what the systemd service runs, which (removing the ExecStart= part) fails since there is no /etc/sysconfig on Unraid, nor is there a urbackupclient anywhere. ExecStart=/usr/local/sbin/urbackupclientbackend --config /etc/sysconfig/urbackupclient --no-consoletime Presumably urbackup has an init file somewhere, but not able to find it. Edit 2: found the daemon Updated process above to run the daemon: /usr/local/sbin/urbackupclientbackend -d

Is anyone able to share exactly how to do this? Which directory on the flash-drive would it be appropriate to store a copy of the client directory? I can do the copy from flash to /usr/local/bin/urbackupclientctl, but not sure how to actually have the client start up.

Old topic I realize, but did you ever get this working?

Looks like this is a known thing with OpnSense. Implementing the changes recommended here appears to get things working. Basically in OpnSense, Firewall > Settings > Advanced enable: Reflection for port forwarding 1: 1 reflection Automatic outbound NAT for reflection NAT Then add your NAT Redirection rules, Firewall > NAT > Port Forwarding: WAN TCP * * WAN address 443 (HTTPS) <<UNRAID SERVER IP>> 1443 (HTTPS) Name WAN TCP * * WAN address 80 (HTTP) <<UNRAID SERVER IP>> 180 (HTTP) Name

So far everything seems to be working. LetEncrypt has the certs all setup. Routing from my subdomain through to Nginx seems to all work. However, when accessing from inside my network I cannot access the subdomain -- the browser never loads the page. When I access outside the network, the login page loads. If I then switch back to access from inside the network, the login page is displayed. To me this suggests that some part of the login page is not available from inside my network, but is subsequently cached in the browser when accessed from outside the network. Which then allows internal access to function. I'm using OpnSense as my firewall, and have NAT Reflection turned on for both port forwarding rules. However, OpnSense options here are a little different to pfSense, so perhaps an alternate option is required? Particular OpnSense auto creates a Filter Rule association. Anyone have any suggestions for enabling access from within my internal network?

This was the part I wasn't understanding at the start, and is the key. Basically a "share" is represented by a top level folder on any of he disks in the array. Doesn't matter how that top-level folder gets there, either as a copy onto the array through a 'share', or direct to the disk via Krusader or rsync. Everything is now back up and running, with none of the many warning previously seen. Telegram notifications have been setup so this time I'll actually see them! Thanks trurl for you help and patience. Out of interest what are you looking at which tells you this -- I'd like to know what to look for.

Appreciate your patience here, thanks for the help! My question is more oriented around the fact that Unraid may split folders within a share across multiple disks. That is typically transparent to Unraid users as Unraid handles all the splitting and shows just the share, regardless of which disk the data happens to be on. In this case though I have a disk which I'm reading from which contains parts of what was once on a share. So for example I have some files from Share1, some from Share2, etc all on the 'failed' disk. Given there's around 1Tb of files, I can't really pick and choose at the low level, so I need to basically grab all files on the unassigned drive under the Share1 directory and copy them to the array share Share1. In theory this simply merges data from the unassigned drive with the data in the array share. There should be no duplicate files names since this disk was originally part of the entire array. I just want to be sure that when I do a copy /failed disk/Share1/dir1/dir1a/* doesn't end up removing whatever existing files or data there might be in /Unraid/Share1/dir1 or even dir1a. Doesn't sound like it'll be an isse, but rather be safe than sorry.

Here's where I'm at: Made a backup of key folders made to an off-Unraid drive using parity to emulate the failed disk. Mounted a LUKS USB drive as Unassigned Device, and from terminal did an rsync of /mnt/disk2 (failed drive) to /mnt/disks/<<USB-DRIVE>>. My next steps as above is to remove the failed drive, and then "New Config without the disk, reassign disks if you want to fill in that gap left by the missing disk2 (making sure you don't change parity assignment, of course), and go ahead and rebuild parity.". The step after that is unclear. What is the process for restoring the files from the failed drive to the array? My confusion is that the failed drive has files from every high level share on the array. Can i simply use Krusader to copy the files from each high level directory on the failed-drive copy over to the appropriate Unraid share, and files will simply merge to the existing sub-directories? Or is it more nuanced than that? One other thought here is I actually have a drive in the array which was recently added, and is not actually being used. Is there a sequence to use this drive somehow? Or is that more messing than is needed?

To answer my own question... goto Settings > Unassigned Devices, in the "Set Encrypted Disk Password" section find your device, and enter the LUKS passphrase. Then back in the Main menu mount the drive.

The backup drive being used is LUKS encrypted. Is this procedure the right way to mount a LUKS drive as Unassigned? Also, when I get to the point where I want to restore the files from the failed drive back to the array it seems like the only practical approach is to restore from a copy of the failed drive if it's still readable. Any other approach is going to require some means of identifying what partial sub-(sub-sub...) directory file content was on the failed drive. What is the best approach to identifying and then restoring the files from the failed drive?

Before the failure, I did see some 'sectors being reallocated' info warnings, and read that as an informational alert saying action had been taken. Is there a way to differentiate a few sectors being reallocated vs a lot of sectors indicating problems? Or are all reallocates cause for the same level of concern? Email alerts make sense, but only if they are user actionable. Yes, I meant Krusader. Not used it with Unassigned Devices, but when I created the docker I did setup an Unassigned folder mapping. Not yet tested that -- will wait for backup to complete fist.

The drive was originally being used as normal drive in a different machine. It did start showing some errors, which prompted me to start using Unraid. At that point I reformatted the drive thinking that might avoid whatever bad parts of the drive there might be. I then used it outside Unraid for a bit, and it "seemed" okay -- although to be honest I'd really have no way of knowing. I then decided it seemed good, so put it in the array. I did see a few notifications, but it's only been in the array for a week or so, and didn't really have a way of assessing if they were danger notifications or just fyi types. Clearly danger notifications tl;dr: Probably been failing for a while without me realizing. Can the final step be done by mounting the backup drive (or worst case the failed drive) as Unassigned and using rsync or Konqueror to copy the data to the array?