Rsync's protocol is always used regardless if the transport is Rsync or SSH. Using an Rsync daemon has a number of benefits. For one it is noticeably faster then using SSH as the transport. An Rsync daemon or server will allow building of shares and ACLs.
I use FreeNAS which has a neat GUI for building Rsync modules (shares) but I didn't understand what most of the options did under-the-covers until I stumbled onto this useful rsync guide. If you are just learned the introductory concepts to running an Rsync Deamon/Server/service check this guide out for key concepts.
Anyways, for my testing I created an Rsync module with the following properties:
Module name: taco Comment: taco Path: /mnt/tank/pipeline/downloads Access Mode: rw Maximum connections: 0 User: nobody Group: nobody Hosts allow: empty Hosts deny: empty Auxiliary parameters: empty
Then from my Ubuntu desktop I was able to sync this remote path to a local directory using the following command:
rsync -aRv rsync://192.168.1.113/taco/ taco/
I also tested the same sync using the SSH transport and compared the network speeds:
rsync -aRv firstname.lastname@example.org:/mnt/tank/pipeline/downloads/ taco/
On the FreeNAS box I ran the following command to watch the network speeds:
systat -ifstat 1
- SSH transport Average
- 58 MB/s
- SSH transportPeak
- 58 MB/s
- Rsync transport Average
- 95 MB/s
- Rsync transport Peak
- 113.73 MB/s
As you can see the Rsync transport was nearly double and seems to have nearly hit the limits of my !Gbps home network.
View Rsync modules and contents
rsync -aRv rsync://192.168.1.113/ taco taco
View module content:
rsync -aRv rsync://192.168.1.113/taco/ receiving incremental file list drwxr-xr-x 5 2014/11/28 19:06:37 . drwxr-xr-x 7 2014/11/28 19:42:25 a-movie.2014.720p.WEB-DL -rw-r--r-- 3,352,418,008 2014/11/28 19:42:24 a-movie.2014.720p.WEB-DL/a-movie.2014.720p.WEB-DL.avi -rw-r--r-- 3,061 2014/11/28 18:55:07 a-movie.2014.720p.WEB-DL/a-movie.2014.720p.WEB-DL.nfo