extern/rclone
1
0
Fork 0
mirror of https://github.com/rclone/rclone.git synced 2024-11-07 09:04:52 +01:00
Code Issues Packages Projects Releases Wiki Activity

docs: add more information about --track-renames

Browse Source 
See: https://forum.rclone.org/t/feature-question-how-does-rclone-track-renames-and-moves/32911/4
This commit is contained in:
Nick Craig-Wood 2022-09-12 11:54:35 +01:00
parent bd787e8f45
commit be53dcc9c9
1 changed files with 19 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

29
docs/content/docs.md
View File

@ -1868,13 +1868,22 @@ By default, rclone doesn't keep track of renamed files, so if you
rename a file locally then sync it to a remote, rclone will delete the rename a file locally then sync it to a remote, rclone will delete the
old file on the remote and upload a new copy. old file on the remote and upload a new copy.
If you use this flag, and the remote supports server-side copy or An rclone sync with `--track-renames` runs like a normal sync, but keeps
server-side move, and the source and destination have a compatible track of objects which exist in the destination but not in the source
hash, then this will track renames during `sync` (which would normally be deleted), and which objects exist in the
operations and perform renaming server-side. source but not the destination (which would normally be transferred).
These objects are then candidates for renaming.
Files will be matched by size and hash - if both match then a rename After the sync, rclone matches up the source only and destination only
will be considered. objects using the `--track-renames-strategy` specified and either
renames the destination object or transfers the source and deletes the
destination object. `--track-renames` is stateless like all of
rclone's syncs.
To use this flag the destination must support server-side copy or
server-side move, and to use a hash based `--track-renames-strategy`
(the default) the source and the destination must have a compatible
hash.
If the destination does not support server-side copy or move, rclone If the destination does not support server-side copy or move, rclone
will fall back to the default behaviour and log an error level message will fall back to the default behaviour and log an error level message
@ -1892,7 +1901,7 @@ Note also that `--track-renames` is incompatible with
### --track-renames-strategy (hash,modtime,leaf,size) ### ### --track-renames-strategy (hash,modtime,leaf,size) ###
This option changes the matching criteria for `--track-renames`. This option changes the file matching criteria for `--track-renames`.
The matching is controlled by a comma separated selection of these tokens: The matching is controlled by a comma separated selection of these tokens:
@ -1901,15 +1910,15 @@ The matching is controlled by a comma separated selection of these tokens:
- `leaf` - the name of the file not including its directory name - `leaf` - the name of the file not including its directory name
- `size` - the size of the file (this is always enabled) - `size` - the size of the file (this is always enabled)
So using `--track-renames-strategy modtime,leaf` would match files The default option is `hash`.
Using `--track-renames-strategy modtime,leaf` would match files
based on modification time, the leaf of the file name and the size based on modification time, the leaf of the file name and the size
only. only.
Using `--track-renames-strategy modtime` or `leaf` can enable Using `--track-renames-strategy modtime` or `leaf` can enable
`--track-renames` support for encrypted destinations. `--track-renames` support for encrypted destinations.
If nothing is specified, the default option is matching by `hash`es.
Note that the `hash` strategy is not supported with encrypted destinations. Note that the `hash` strategy is not supported with encrypted destinations.
### --delete-(before,during,after) ### ### --delete-(before,during,after) ###