From 960fb6a61692c5f2c3e491aa954b6dbda9070745 Mon Sep 17 00:00:00 2001 From: Git'Fellow Date: Fri, 6 May 2022 10:35:06 +0200 Subject: [PATCH] Small clarification about server-side copy --- docs/content/docs.md | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/docs/content/docs.md b/docs/content/docs.md index 8a072e67a..7417db779 100644 --- a/docs/content/docs.md +++ b/docs/content/docs.md @@ -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.