![]() Select the task you just named, ‘backupISOs’ You will want to ‘+add’ a new task, it’s a button on the right side of the GUIĬlick the ‘Okay’ button. Warning a bug exists that will crash the container and will cause you to start all the way over, please follow directions explicitly. In this example I will be backing up a share called “isos”. It can be easy to overwrite data if you aren’t careful. Just be careful not to copy your appdata directory from your primary server over top of your backup servers’ appdata directory. ![]() In my example we will be only backing up individual Shares, however, you can back up all Shares at once. The Backup Server has pre-created Shares that are named identically to my Main/Primary Server. The Main Server is where all of my files, pictures, videos, and ISO’s are we want to essentially copy those over to our Backup Server just in case something goes wrong. Both the Main Server and Backup Server are plugged into the same 10Gigabit switch. This is an extremely simple diagram showing how the network is setup. Please use this guide as a learning tool and whenever possible, practice good cybersecurity techniques. It is very common for administrators to create a specific account/non-user account to perform the backups of a system or server. Please note that it is not best practice to use the ‘root’ user to execute backups. FeaturesĮxecute other commands before or after a task LuckyBackup is a very user-friendly GUI backup container that uses rsync on the backend and only transfers over any changes rather than all your data, all of the time. While the steps to make this happen may seem daunting, they are actually very simple and mostly painless! What is LuckyBackup , -identity , -webui.listen :) if you don't need additoonal special configuration (see ).In this guide we will backing up Unraid to another Unraid server using LuckyBackup. chown : /home/.serviceĪfter=network.target network-online.targetĮxecStart=/usr/bin/rslsync -config /etc/resilio-sync/.jsonįor each instance generate a dedicated resilio sync config file /etc/resilio-sync/.json Make the necessary sync directories under each user home folder like mkdir /home//pictures and mkdir /home//music and ensure that they are owned by the user (i.e. I assume that sync directories for each user are under its home directory. You can disable login if you don't want these users to login onto you server by changing "bin/bash" to "/bin/false" for the specific user in the /etc/passwd file. Setup an account for each user on your home server. But it is in configuration mode without a WebUI. I am running several resilio sync instances in parallel on my Ubuntu 20.04 home server. Perhaps someone else can comment on that? I am not sure about removing the source files once you have moved them to your RAID array. ![]() I have a single user case with multiple windows, linux and android clients, so I have my always on Pi hosting a shared folder. Multitple users: You can do this with the Family key, you could then decide on the folder type that would be shared across your users. so all my backups are automated, and up to four months old at any point. Why not run an rsync cron to synchronize/mirror to your RAID array? Or something such as rsnapshot? Backup is accomplished using rsnapshot to save it to a software raid array on a daily basis. You create "myshare" and it would then have a path of "/home/pi/sync/myshare" home/pi/sync:/sync # a shared folder gets stored here. docker/resilio-sync/cache:/downloads # cache dir for partial downloads docker/resilio-sync/config:/config #main program dir where config info is stored on local disk outside of the container I find the docker solution elegant and very simple to replicate on other linux clients. You could run the docker container of resilio sync on each machine (linux) or the regular Windows, MAC clients. The problem I'm having is knowing how to run 4 separate instances - ideally using systemd to auto start them at boot - and how/if to get those instances to run with 4 different users. Moving the files would also then ensure they get cleaned off the source device.ĭoes that make sense or is there a way better way of doing it? i would then do some manual pruning and moving files i really want to keep to a separate folder for backup on a raid disk. Once the instances are running 24/7 (and configured to sync to folders in user's own home directory) then any time one of us opens sync on a device like my phone - it syncs the photos to the linux server. My idea is to have 4 instances of sync running in parallel so they all get their own web-gui as well to help with setup and maintenance. Hi I'm trying to figure out the best way to setup sync on my home linux server so all 4 members of the family have an 'always on' client ready to receive syncs from each persons phone, tablet and pc.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |