RsyncUI implements default parameters which are working fine for simple synchronize and restore tasks. The actual parameters used in tasks are depended upon executing rsync over network connection or not. Which standard parameters to use is computed during startup of application by reading the configuration file. The user can also remove default parameters if required. Parameters to rsync is saved by task. The ssh parameter might be set global to all tasks. The global ssh parameters might by overridden by ssh parameter by task.
About verify changes in parameters, see below about Verify.
Default rsync parameters
Selecting the default tab presents the default parameters to rsync. The defaults parameters can also be switched on or off on a task.
The following parameters are applied to all tasks:
--archiveensures that all files are transferred with all attributes preserved
--verbosemake rsync very outspoken, required for counting files in RsyncUI
--deletedelete all files at destination which are not in the source
- this parameter also applies when restoring files, always do a restore to a temporary restore catalog
Default rsync parameters networked tasks only
The following parameters are for networked tasks only. A networked task is a task where destination is on a remote server, either on local LAN or on Internet.
--compresscompress files before transmitting, applies only if remote server
-e sshto ensure rsync tunnels traffic through a ssh-tunnel, applies only if there is a remote server
-e "ssh -p nn"choose another port nn if standard port 22 is not used, enable by setting port number in parameters, applies only if remote server
Ssh parameters (local)
There are two parameters to set for ssh. The local ssh parameters overrides global ssh parameters set in the user config.
- ssh port, set if ssh uses other port than standard port 22
- the ssh keypath and identity file, normally this is
.ssh/id_rsa, set name only if other keypath and identity file to be used by ssh
The Verify button
The resulting commandline string is dynamically updated when changing parameters. By the
Verify button new parameters might be tested before saving. The verify executes a
--dry-run task for verification of parameters. The above applies to both default and user set parameters. The
Verify is context sensitive. If like the
verify swicth is selected the verify executes a verify. And likewise for
Regarding the Verify button and the
verify switch is on. If there are many files a verify will take some time due to rsync computes the checksum and compares each files by checksum.
Adding parameters to rsync
Selecting the parameters tab enables adding new parameters to rsync. Rsync utilizes a ton of parameters.
Parameters are normally constructed as:
- parameter only
For a full list of parameters to rsync please see the rsync docs.
You can instruct rsync to save changed and deleted files in a separate backup catalog ahead of the change. This feature is utilized by setting the following parameters:
--backupparameter instructs rsync to save changed files
--backup-dirparameter where to save changed or deleted files before rsync synchronize source and destination
- RsyncUI does suggest a value for the
--backup-dirbut you might set it to whatever you want
- RsyncUI does suggest a value for the
- rsync daemon:
::enabling rsync daemon puts a double colon
::in address parameter to rsync. It forces rsync to use the rsync daemon remote.
There are two possible setup for using the rsync daemon. Utilizing a rsync daemon setup does not encrypt the transfer between client and server. To encrypt the transfer require tunneling traffic in a ssh protocol, see how to setup ssh passwordless logins.
Default catalog for backup of
<catalog to synchronize> relativ to the synchronized catalog is:
../backup_<catalog to synchronize>
Suffix on changed and deleted files
Rsync can also set a time stamp as suffix on files. This might be useful if there are several revisions of files. The –suffix parameter set suffix on files, suffix can be set on files together with the –backup parameter. One suffix might rename files which are either deleted or replaced newer files with a trailing date and time stamp.
- sample suffix FreeBSD
- sample suffix Linux
I have experienced some variations regarding the suffix. If you want to use suffix you might try an alternative suffix if the above is not working as expected. If so is true use instead. You just have to try and see what works
Author Thomas Evensen
License CC BY-NC-ND 4.0