Keep large directory structures in sync quickly with rsync
While tar over ssh is ideal for making remote copies of parts of a filesystem, rsync is even better suited for keeping the filesystem in sync between two machines. Typically, tar is used for the initial copy, and rsync is used to pick up whatever has changed since the last copy. This is because tar tends to be faster than rsync when none of the destination files exist, but rsync is much faster than tar when there are only a few differences between the two filesystems.
To run an rsync over ssh, pass it the -e switch, like this:
root@rover:~# rsync -ave ssh greendome:/home/ftp/pub/ /home/ftp/pub/
Notice the trailing / on the file spec from the source side (on greendome.) On the source specification, a trailing / tells rsync to copy the contents of the directory, but not the directory itself. To include the directory as the top level of whatever is being copied, leave off the /:
root@village:~# rsync -ave ssh bcnu:/home/six .
This will keep a copy of the ~root/six/ directory on village in sync with whatever is present on bcnu:/home/six/.
By default, rsync will only copy files and directories, but not remove them from the destination copy when they are removed from the source. To keep the copies exact, include the -- delete flag:
six@jammer:~/public_html# rsync -ave ssh -- delete greendome:~one/reports .
Now when old reports are removed from ~one/reports/ on greendome, they're also removed ...