a12vman

I will throw my hat in the ring here. I have always had a backup strategy in my household to protect the important stuff. I I was always a big fan of Acronis and ran it from my windows machine to file-based backups. I have been searching for a decent file backup utility within Unraid Docker. I stumbled onto Duplicacy and decided to give it a try. I was able to backup about 1 TB from my Unraid Server to a Synology Box on my local network. I was averaging about 20MB/s but I suspect that Synology was the bottleneck. I tested the restore functionality - no issues with that. I added scheduled jobs within Duplicacy and they are running without issue. I am ready to take it to the next level: 1. Purchase personal license 2. Sign up for Backblaze Account 3. Setup secondary jobs for each backup and point to Backblaze for true 3-2-1 protection. Has anyone had experience with Duplicacy and Cloud backups? I'm not sure how long the cloud backups will take, do they have to be contiguous? I have the CA AppData backup process where Docker service is shutdown. Not sure what would happen to a backup that is running, would a long running job complete?

Reporting similar issue here with the 2021.01.19 Version: Last check completed on Fri 05 Feb 2021 07:08:36 AM EST (yesterday), finding 0 errors. Duration: 1 day, 6 hours, 38 minutes, 30 seconds. Average speed: 126.9 MB/sec Parity Check Tuning: 06-02-2021 00:15 [MEDIATOWER] Correcting Parity Check aborted (0 errors) 0% completed Elapsed Time Unavailable, Runtime Unavailable, Increments 1, Average Speed nanB/s

I decided to give Duplicati a try as my backup solution. I have been using UnRaid for the last 10 years but I stepped up my game in the last year by setting up several dockers along with a few VM's on my Quad Xeon with 64GB Ram. I installed the Docker and scheduled a 220GB backup from Unraid to a remote SMB Share(Synology Box) for 3am. When I woke up this morning it looks as if the backup was complete(~220GB of duplicati files in my Synology Share). I attampted to access the Duplicati WebUI but it won't come up - stuck on loading. I stopped and re-started the Docker - same result. I stopped the array and re-booted the server - same result I can't access the WebUI. No errors in the Docker Log and no errors in Syslog. Where do I go next?

Update: My issue was network-related. I had enabled a 2nd NIC on my server. I disabled the 2nd NIC and rebooted the server -. All is well now. I think I will leave it alone before I create more problems. I have been sailing with Deluge for some time now without issue. I have VPN enabled in Deluge routing thru Toronto. I rebooted my unraid server today. I am not able to open the Deluge WEBUI without first disabling the VPN. What is the issue? This was working fine before I did the re-boot. I just get the "site cannot be reached" error. Using port 8112. Here is my log: 2020-02-19 20:39:33,304 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2020-02-19 20:39:33,305 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2020-02-19 20:39:33,425 DEBG 'start-script' stdout output: [info] Default route for container is 172.17.0.1 2020-02-19 20:39:33,431 DEBG 'start-script' stdout output: [info] Adding 209.222.18.222 to /etc/resolv.conf 2020-02-19 20:39:33,436 DEBG 'start-script' stdout output: [info] Adding 84.200.69.80 to /etc/resolv.conf 2020-02-19 20:39:33,442 DEBG 'start-script' stdout output: [info] Adding 37.235.1.174 to /etc/resolv.conf 2020-02-19 20:39:33,448 DEBG 'start-script' stdout output: [info] Adding 1.1.1.1 to /etc/resolv.conf 2020-02-19 20:39:33,454 DEBG 'start-script' stdout output: [info] Adding 209.222.18.218 to /etc/resolv.conf 2020-02-19 20:39:33,459 DEBG 'start-script' stdout output: [info] Adding 37.235.1.177 to /etc/resolv.conf 2020-02-19 20:39:33,465 DEBG 'start-script' stdout output: [info] Adding 84.200.70.40 to /etc/resolv.conf 2020-02-19 20:39:33,471 DEBG 'start-script' stdout output: [info] Adding 1.0.0.1 to /etc/resolv.conf 2020-02-19 20:41:33,599 DEBG 'start-script' stderr output: Error: error sending query: Could not send or receive, because of network error 2020-02-19 20:43:33,724 DEBG 'start-script' stderr output: Error: error sending query: Could not send or receive, because of network error 2020-02-19 20:45:38,847 DEBG 'start-script' stderr output: Error: error sending query: Could not send or receive, because of network error 2020-02-19 20:47:43,970 DEBG 'start-script' stderr output: Error: error sending query: Could not send or receive, because of network error 2020-02-19 20:49:49,092 DEBG 'start-script' stderr output: Error: error sending query: Could not send or receive, because of network error 2020-02-19 20:51:54,221 DEBG 'start-script' stderr output: Error: error sending query: Could not send or receive, because of network error Then I shut down the Docker and deleted the Config Files in OpenVPN. Copied the original certificates back and changed my end point from Toronto to France. Same results in the logfile. Also looking at my Unraid Log I am seeing the following : Feb 20 07:36:16 MediaTower kernel: docker0: port 4(veth9c959ce) entered blocking state Feb 20 07:36:16 MediaTower kernel: docker0: port 4(veth9c959ce) entered forwarding state Feb 20 07:36:16 MediaTower kernel: docker0: port 4(veth9c959ce) entered disabled state Feb 20 07:36:17 MediaTower kernel: eth0: renamed from vethde49b44 Feb 20 07:36:17 MediaTower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth9c959ce: link becomes ready Feb 20 07:36:17 MediaTower kernel: docker0: port 4(veth9c959ce) entered blocking state Feb 20 07:36:17 MediaTower kernel: docker0: port 4(veth9c959ce) entered forwarding state Feb 20 07:38:37 MediaTower kernel: docker0: port 4(veth9c959ce) entered disabled state Feb 20 07:38:37 MediaTower kernel: vethde49b44: renamed from eth0 Feb 20 07:38:37 MediaTower kernel: docker0: port 4(veth9c959ce) entered disabled state Feb 20 07:38:37 MediaTower kernel: device veth9c959ce left promiscuous mode Feb 20 07:38:37 MediaTower kernel: docker0: port 4(veth9c959ce) entered disabled state Feb 20 07:38:41 MediaTower kernel: docker0: port 4(veth55c0157) entered blocking state Feb 20 07:38:41 MediaTower kernel: docker0: port 4(veth55c0157) entered disabled state Feb 20 07:38:41 MediaTower kernel: device veth55c0157 entered promiscuous mode Feb 20 07:38:41 MediaTower kernel: IPv6: ADDRCONF(NETDEV_UP): veth55c0157: link is not ready Feb 20 07:38:41 MediaTower kernel: docker0: port 4(veth55c0157) entered blocking state Feb 20 07:38:41 MediaTower kernel: docker0: port 4(veth55c0157) entered forwarding state Feb 20 07:38:41 MediaTower kernel: docker0: port 4(veth55c0157) entered disabled state Feb 20 07:38:43 MediaTower kernel: eth0: renamed from veth37cc761 Feb 20 07:38:43 MediaTower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth55c0157: link becomes ready Feb 20 07:38:43 MediaTower kernel: docker0: port 4(veth55c0157) entered blocking state Feb 20 07:38:43 MediaTower kernel: docker0: port 4(veth55c0157) entered forwarding state Feb 20 07:57:51 MediaTower kernel: docker0: port 4(veth55c0157) entered disabled state Feb 20 07:57:51 MediaTower kernel: veth37cc761: renamed from eth0 Feb 20 07:57:52 MediaTower kernel: docker0: port 4(veth55c0157) entered disabled state Feb 20 07:57:52 MediaTower kernel: device veth55c0157 left promiscuous mode Feb 20 07:57:52 MediaTower kernel: docker0: port 4(veth55c0157) entered disabled state Feb 20 07:59:46 MediaTower kernel: docker0: port 4(vethc3f7b23) entered blocking state Feb 20 07:59:46 MediaTower kernel: docker0: port 4(vethc3f7b23) entered disabled state Feb 20 07:59:46 MediaTower kernel: device vethc3f7b23 entered promiscuous mode Feb 20 07:59:46 MediaTower kernel: IPv6: ADDRCONF(NETDEV_UP): vethc3f7b23: link is not ready Feb 20 07:59:46 MediaTower kernel: docker0: port 4(vethc3f7b23) entered blocking state Feb 20 07:59:46 MediaTower kernel: docker0: port 4(vethc3f7b23) entered forwarding state Feb 20 07:59:46 MediaTower kernel: docker0: port 4(vethc3f7b23) entered disabled state Feb 20 07:59:47 MediaTower kernel: eth0: renamed from veth3940a12 Feb 20 07:59:47 MediaTower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethc3f7b23: link becomes ready Feb 20 07:59:47 MediaTower kernel: docker0: port 4(vethc3f7b23) entered blocking state Feb 20 07:59:47 MediaTower kernel: docker0: port 4(vethc3f7b23) entered forwarding state