forked from TrueCloudLab/rclone
Clarify what happens to files already in the --backup-dir DIR
This commit is contained in:
parent
47ebd0789c
commit
07ebf35987
1 changed files with 5 additions and 1 deletions
|
@ -193,7 +193,8 @@ respectively.
|
|||
|
||||
When using `sync`, `copy` or `move` any files which would have been
|
||||
overwritten or deleted are moved in their original hierarchy into this
|
||||
directory.
|
||||
directory. Files with matching paths already in DIR will be
|
||||
overwritten.
|
||||
|
||||
The remote in use must support server side move or copy and you must
|
||||
use the same remote as the destination of the sync. The backup
|
||||
|
@ -207,6 +208,9 @@ will sync `/path/to/local` to `remote:current`, but for any files
|
|||
which would have been updated or deleted will be stored in
|
||||
`remote:old`.
|
||||
|
||||
If running rclone from a script you might want to use today's date as
|
||||
the directory name passed to `--backup-dir` to store the old files.
|
||||
|
||||
### --bwlimit=BANDWIDTH_SPEC ###
|
||||
|
||||
This option controls the bandwidth limit. Limits can be specified
|
||||
|
|
Loading…
Reference in a new issue