Sync Remote Directories: Difference between revisions

From Littledamien Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
== `rsync` command ==
Use `rsync` on the command line:
Use `rsync` on the command line:


Line 4: Line 6:
$ rsync -av -e "ssh -p [NON_DEFAULT_SSH_PORT]" [USER]@[REMOTE_ADDRESS]:/path/to/remote/dir/ /path/to/local/dir
$ rsync -av -e "ssh -p [NON_DEFAULT_SSH_PORT]" [USER]@[REMOTE_ADDRESS]:/path/to/remote/dir/ /path/to/local/dir
</pre>
</pre>
== Arguments ==


* `a` flag: Stands for "archive" and copies recursively, preserving permissions, symbolic links, etc.
* `a` flag: Stands for "archive" and copies recursively, preserving permissions, symbolic links, etc.
Line 9: Line 13:
* `v` flag: Verbose.
* `v` flag: Verbose.
* `e` flag: Method for using a non-standard ssh port if the remote host is configured with a non-standard ssh port.
* `e` flag: Method for using a non-standard ssh port if the remote host is configured with a non-standard ssh port.
The order of remote vs local paths matters. Local path must be on the left in order push files on local to remote. Similarly, remote must be on the left to push files onto local.


* `--exclude` specifies one subdirectory to exclude from the operation. The directory name must be followed with at trailing slash.
* `--exclude` specifies one subdirectory to exclude from the operation. The directory name must be followed with at trailing slash.
* `--delete` option will cause target files and directories to be deleted if they are not found  within the source directory.
* `--delete` option will cause target files and directories to be deleted if they are not found  within the source directory.
== Source and target paths ==
N.B. The trailing slash on the source path is required when copying directories. For the target path, no trailing slash will cause the directory to be the root of where files will be copied. A trailing slash on the target path would cause the source directory to be copied ''into'' the target directory, e.g. `/path/to/local/dir/dir`.
The order of remote vs local paths matters. Local path must be on the left in order push files from local to remote. Similarly, remote must be on the left to push files onto local.


Home directory on remote can be specified with `~` after the semicolon, e.g. `[USER]@[REMOTE_ADDR]:~/path/below/home/`
Home directory on remote can be specified with `~` after the semicolon, e.g. `[USER]@[REMOTE_ADDR]:~/path/below/home/`
=== Whitespaces in paths ===
On linux, whitespace is handled with the `--protect-args` argument. This argument isn't included in the Mac OS distribution of `rsync`.
On Mac, quote the path ''and'' escape white spaces, e.g. `'[USER]@[REMOTE]:~/path/to/directory\ with\ spaces/'`

Revision as of 14:13, 5 December 2021

rsync command

Use rsync on the command line:

$ rsync -av -e "ssh -p [NON_DEFAULT_SSH_PORT]" [USER]@[REMOTE_ADDRESS]:/path/to/remote/dir/ /path/to/local/dir

Arguments

  • a flag: Stands for "archive" and copies recursively, preserving permissions, symbolic links, etc.
  • n flag: "Dry run" option for testing purposes.
  • v flag: Verbose.
  • e flag: Method for using a non-standard ssh port if the remote host is configured with a non-standard ssh port.
  • --exclude specifies one subdirectory to exclude from the operation. The directory name must be followed with at trailing slash.
  • --delete option will cause target files and directories to be deleted if they are not found within the source directory.

Source and target paths

N.B. The trailing slash on the source path is required when copying directories. For the target path, no trailing slash will cause the directory to be the root of where files will be copied. A trailing slash on the target path would cause the source directory to be copied into the target directory, e.g. /path/to/local/dir/dir.

The order of remote vs local paths matters. Local path must be on the left in order push files from local to remote. Similarly, remote must be on the left to push files onto local.

Home directory on remote can be specified with ~ after the semicolon, e.g. [USER]@[REMOTE_ADDR]:~/path/below/home/

Whitespaces in paths

On linux, whitespace is handled with the --protect-args argument. This argument isn't included in the Mac OS distribution of rsync.

On Mac, quote the path and escape white spaces, e.g. '[USER]@[REMOTE]:~/path/to/directory\ with\ spaces/'