Rsync is not a TrueNAS thing. It is a *nix tool.
Typically, you create a “recipe” in a config file on each client for your server to use. This allows you to keep things organized. The questions you need answers to are: how, what, when, and where
So, on each client, you’d set up a “RSYNCD (daemon)” for one part of the transfer. On the server side, you only need the rsync tool installed.
Typically the process works like this (bear with me, not working on a *nix machine so we’re free-flying here):
These are the instructions for the client side rsync to find information and etc. There are different clients and each have their own way to start a daemon.
client: /etc/rsyncd.conf (chmod 644)
secretes file = /etc/rsync.secrets
hosts allow = 192.168.1.1/24
uid = nobody
gid = nobody
list = yes
readonly = yes
use chroot = no
log file = /var/log/rsyncd.log
[mine]
path = /home/mine
comment = My directory
ignore nonreadable = yes
uid = 555
gid = 14
auth users = mine
secrets file = /etc/rsyncd.secretes
Then you need a place to store your password (safely).
client: /etc/rsync.secrets (owned/read by root only – chmod 600).
mine:password
Then on the server side, you store passwords
create a secretes file with: (owned/read by root only – chmod 600) which looks like this:
a_user:client-password
another_user:client-password
Now your server knows how and what to get, you just need to tell it where to put it and when.
You could set up a cron task to do it or even create a rc.d script to do it:
rsync -avzz --stats --password-file=rsync.secretes user@machine::mine backup\backup-mine\
Forgive any mistakes (and I didn’t proof-read what I just typed much so take it with a grain of salt; this was more to give you a 10,000 foot overview of the process).
What are you doing (what is: ‘rsync-task gui’)?
