NAME
git-annex copy - copy content of files to/from another repository
SYNOPSIS
git annex copy [path ...] [--from=remote|--to=remote]
DESCRIPTION
Copies the content of files from or to another remote.
OPTIONS
--from=remoteCopy the content of files from the specified remote to the local repository.
Any files that are not available on the remote will be silently skipped.
--to=remoteCopy the content of files from the local repository to the specified remote.
--to=hereCopy the content of files from all reachable remotes to the local repository.
--jobs=N-JNEnables parallel transfers with up to the specified number of jobs running at once. For example:
-J10Setting this to "cpus" will run one job per CPU core.
--autoRather than copying all files, only copy files that don't yet have the desired number of copies, or that are preferred content of the destination repository. See git-annex-preferred-content(1)
--fastWhen copying content to a remote, avoid a round trip to check if the remote already has content. This can be faster, but might skip copying content to the remote in some cases.
--all-ARather than specifying a filename or path to copy, this option can be used to copy all available versions of all files.
This is the default behavior when running git-annex in a bare repository.
--branch=refOperate on files in the specified branch or treeish.
--unusedOperate on files found by last run of git-annex unused.
--failedOperate on files that have recently failed to be transferred.
--key=keynameUse this option to copy a specified key.
file matching options
The git-annex-matching-options(1) can be used to specify files to copy.
--batchEnables batch mode, in which lines containing names of files to copy are read from stdin.
As each specified file is processed, the usual progress output is displayed. If a file's content does not need to be copied, or it does not match specified matching options, or it is not an annexed file, a blank line is output in response instead.
Since the usual output while copying a file is verbose and not machine-parseable, you may want to use --json in combination with --batch.
-zMakes the
--batchinput be delimited by nulls instead of the usual newlines.--jsonEnable JSON output. This is intended to be parsed by programs that use git-annex. Each line of output is a JSON object.
--json-progressInclude progress objects in JSON output.
--json-error-messagesMessages that would normally be output to standard error are included in the json instead.
SEE ALSO
git-annex(1)
AUTHOR
Joey Hess id@joeyh.name
Warning: Automatically converted into a man page by mdwn2man. Edit with care.

If you run
git annex copy --from slowremote1in one terminal and at the same time rungit annex copy --from slowremote2in another terminal, the two processes will cooperatively get the files, spreading the load amoung the remotes. This works because git-annex avoids downloading a file if the same file is already being downloaded by a different process.Commenting on a man page is not the right way to report a problem. File a bug report.
FWIW, copy --all works fine in my tests. Of course, there are certianly situations where it copies nothing. Eg, if there are no files with ontents in the repository for it to copy.
Hi,
I want to back up all my files including previous versions on an external drive. I’ve tried these two commands – both of them exited instantly without producing any output: