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

Small clarification about server-side copy

Browse Source
This commit is contained in:
Git'Fellow 2022-05-06 10:35:06 +02:00 committed by GitHub
parent a3d4307892
commit 960fb6a616
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/content/docs.md
View File

@ -390,7 +390,7 @@ or
rclone sync -i /full/path/to/sync:me remote:path
Server Side Copy
Server-Side Copy
----------------
Most remotes (but not all - see [the
@ -410,14 +410,20 @@ downloading and re-uploading.
Remotes which don't support server-side copy **will** download and
re-upload in this case.
Server side copies are used with `sync` and `copy` and will be
Server-side copies are used with `sync` and `copy` and will be
identified in the log when using the `-v` flag. The `move` command
may also use them if remote doesn't support server-side move directly.
This is done by issuing a server-side copy then a delete which is much
quicker than a download and re-upload.
Server side copies will only be attempted if the remote names are the
same.
Server-side copies will only be attempted if the remote names are the
same. This will try a server-side copy from A to A:
rclone copy s3-a:oldbucket s3-a:newbucket
This will download and re-upload files from A to B:
rclone copy s3-a:oldbucket s3-b:newbucket
This can be used when scripting to make aged backups efficiently, e.g.