dedi

Thank you, I used your example and it works good. One problem I have with my script is, when the ssh connection cant get established I dont get a fail warning, it looks like everything went well. How could I fix that?

Thanks, I'll keep that in mind I'm still curious, why can I connect to an IP that isn't up? My config: eth0: 192.168.0.20, after the problem I shut it down with (ifconfig eth0 down). eth1 takes over and network starts working again. eth1: 192.168.0.21 On other devices on the network, I still can connect to 192.168.0.20

Thank you for the answer. I could not find that myself. At least glad to hear it is already known. Since I never had any other problems with these NICs I'll just wait for a fix or maybe downgrade in the meantime.

I'm on 6.6.2 and still have this problem:

Since a few weeks (about since 6.6.0) I'm repeatedly loosing my network connection after a uptime from one to a few days. From that moment on I get "r8169 0000:0f:00.0 eth0: link up" spamed in the syslog. I can manually put eth0 down and up with no success, also plugin in to another switch doesn't help. I can shut down eth0 and start using eth1, I currently have no bridging or bonding active. (A side note: isn't it strange that I can still connect to the IP of eth0 even it is down?). The same thing happens when I switch eth0 with eth1. Hardware: Mainboard Z68 Professional Gen3, I2500k with 2 onboard NICs (r8169), 16 GB RAM Unraid 6.6.2 dednas-diagnostics-20181019-1624.zip

I thought I share my rsync config. I still feel like Unraid as a Storage Server should provide a build in method to backup or sync its data to an other location, but configuring rsync gives you a lot of power, and once set up, it's just great. I based my config and setup on the tutorial found here: https://lime-technology.com/forums/topic/52830-syncronize-servers-using-rsync-over-ssh-next-door-or-across-the-world/ And I made some adjustments, specially the option to watch the sync going on, and the notification that works with the build in unraid notification. So on "errors" you will get a E-Mail notification if your unraid is setup for that. The above tutorial covers the SSH setup and connect via key instead of login, and the basic rsync setup. You can continue after that guide. What you need is the NerdPack Plugin, and there install "screen". It is used to run rsync in it own screen, giving you the option to pull the progress up in a console at any time. The second one is optional but recommended, its the "User Scripts" plugin. It allows you to add own scripts and execute it via cron in your unraid GUI. I created 2 scripts for my rsync: The first one I called "rsync" and does the rsync job, and depending on its exit code, it gives the notification to the Unraid Notification Service. #!/bin/bash rsync -avu --bwlimit=4000 --numeric-ids --log-file=/mnt/user/Backup/rsync-logs/log.`date '+%Y_%m_%d__%H_%M_%S'`.log --progress --exclude 'C Sys' --timeout=600 -e "ssh -p 4222 -i /root/.ssh/DSStoDMS-key -T -o Compression=no -x " /mnt/user/Backup/Devices/ [email protected]:/volume2/Backup/Unraid_rsync if [ $? -eq 0 ] then /usr/local/emhttp/webGui/scripts/notify -s "`hostname` to DMS Rsync Backup complete" -d "Sync compled. `date` `tail /mnt/user/Backup/rsync-logs/last.log`" else /usr/local/emhttp/webGui/scripts/notify -s "`hostname` to DMS Rsync Backup FAILED" -i "alert" -d "Sync compled. `date` `tail /mnt/user/Backup/rsync-logs/last.log`" fi Of course, the rsync command would need some adjustments. If your Unraid server is setup to send you a E-Mail on errors, it will do that too if rsync fails! The second one is for calling that script in a "screen" session. #!/bin/bash export SCREENDIR=/root/.screen screen -dmS rsyncdms /boot/config/plugins/user.scripts/scripts/rsync/script You can pull it up as long as it is running with screen -r from a console. You can just use the build in one from the WebGUI. Attention, if you name the first script different than "rsync", you have to adjust this location. Now just set a schedule for the second script. Watch its progress with "rsync -r" I hope this can help somebody. Im not a rsync expert, so if anyone is around with more experience has some input, its very welcome. And I have a questions myself: I have large files to transfer, sometimes a lot of new data comes up at once. So if I have to transfer >400GB, it needs more than 24h, and the rsync backup script (which is scheduled to run daily) is started again. It starts with the files that is currently transfering in the first instance of rsync. It works, but it will transfer that big file twice. Should I check when running the script if rsync is already running? Or does running rsync with --partial do any good or bad here?

Thanks Hoopster for your reply. Not really the kind of solution im looking for. I am used to console, but I dont like it at all on "it should just run" system like my NAS. I dislike it because not only the work to put in until it works, it's also a thing I never know if it will still run when upgrading unraid. Still because of lack of alternatives I'll give it a try. So far Im 2 hours in fiddling around and still not working. And it wont stop after that guide. This is still only a sync, not a backup.

Hello everyone I'm on Unraid since the start of this year, and with most things pretty happy. The one thing I do miss hardly is no good way to backup the unraid server to another server. In my case my old synology. I mean it is absolutely nessesairy to do another backup - and there is no build in function for that? Even worse, including all the available dockers there seems no useable solution. I tried duplicati - it is just slow as hell. after 20h i got 300GB of my 8TB to backup. All wired LAN network. Rsync seems like a method, but there is simply no GUI available? setting up would be one thing via console - but I need some monitoring. Is there anything left Im missing? How is every one else doing it?