Page tree

Welcome to FreeSoftwareServers Confluence Wiki

Skip to end of metadata
Go to start of metadata


rsync options source destination

Over SSH: To specify a protocol with rsync you need to give “-e” option with protocol name you want to use. 

rsync -avzhe ssh source destination


       This  tells  rsync  to remove from the sending side the files (meaning non-directories) that are a
       part of the transfer and have been successfully duplicated on the receiving side.

       Note that you should only use this option on source files that are quiescent.  If  you  are  using
       this to move files that show up in a particular directory over to another host, make sure that the
       finished files get renamed into the source directory, not directly written into it, so that  rsync
       can’t  possibly transfer a file that is not yet fully written.  If you can’t first write the files
       into a different directory, you should use a naming idiom that lets rsync avoid transferring files
       that  are  not  yet  finished (e.g. name the file "" when it is written, rename it to "foo"
       when it is done, and then use the option --exclude='*.new' for the rsync transfer).
       This tells rsync to delete extraneous files from the receiving  side  (ones  that  aren’t  on  the
       sending  side),  but  only  for  the directories that are being synchronized.  You must have asked
       rsync to send the whole directory (e.g.  "dir"  or  "dir/")  without  using  a  wildcard  for  the
       directory’s  contents  (e.g.  "dir/*")  since the wildcard is expanded by the shell and rsync thus
       gets a request to transfer individual files, not the files’  parent  directory.   Files  that  are
       excluded   from   the   transfer  are  also  excluded  from  being  deleted  unless  you  use  the
       --delete-excluded option or mark the  rules  as  only  matching  on  the  sending  side  (see  the
       include/exclude modifiers in the FILTER RULES section).

              Prior  to rsync 2.6.7, this option would have no effect unless --recursive was enabled.  Beginning
              with 2.6.7, deletions will also occur when --dirs (-d) is enabled, but only for directories  whose
              contents are being copied.

              This option can be dangerous if used incorrectly!  It is a very good idea to first try a run using
              the --dry-run option (-n) to see what files are going to be deleted.

              If the sending side detects any I/O errors, then the deletion of any files at the destination will
              be  automatically  disabled. This is to prevent temporary filesystem failures (such as NFS errors)
              on the sending side from causing a massive deletion of files on the destination.  You can override
              this with the --ignore-errors option.

              The  --delete  option  may  be combined with one of the --delete-WHEN options without conflict, as
              well as --delete-excluded.  However, if none of the --delete-WHEN  options  are  specified,  rsync
              will  choose  the  --delete-during  algorithm  when  talking  to  rsync  3.0.0  or  newer, and the
              --delete-before  algorithm  when  talking  to  an  older  rsync.   See  also  --delete-delay   and

Common Flags:


To run it in the background use:

nohup [rysnc command] > nohup.log &

Useful Flags:

-n,                              --dry-run perform a trial run with no changes made
-v,                              --verbose increase verbosity
-a,                              --archive archive mode; equals -rlptgoD (no -H,-A,-X)
-P,                              --progress show progress during transfer
--remove-source-files            --sender removes synchronized files (non-dir)
--delete                         --delete extraneous files from dest dirs
-z,                              --compress compress file data during the transfer
--iconv=iso-8859-1,utf8          =--iconv=[localenc],[remoteenc] (Conv. Enc. on the fly) 

Note: It is better to Rsync over SSH than to rsync two "local" folders which are actually NFS/Remote Mounts. 

  • No labels