Bug 10963 - rsync to multiple destinations
Summary: rsync to multiple destinations
Alias: None
Product: rsync
Classification: Unclassified
Component: core (show other bugs)
Version: 3.0.6
Hardware: All All
: P5 normal (vote)
Target Milestone: ---
Assignee: Wayne Davison
QA Contact: Rsync QA Contact
Depends on:
Reported: 2014-11-25 22:58 UTC by Dave Yost
Modified: 2020-07-26 08:15 UTC (History)
1 user (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Dave Yost 2014-11-25 22:58:55 UTC

Comment 1 Dave Yost 2014-11-25 23:00:36 UTC
Something like this would be useful:
  rsync foo s1: --add-destinations s2:dir s3:dir
  rsync foo s1: --to s1: s2:dir s3:~
Comment 2 Kevin Korb 2014-11-25 23:11:01 UTC
These would be separate rsync (and ssh) connections.  What use case would justify bundling them together into a single rsync session?  The only benefit over multiple exections of rsync would be a lack of per-session error handling.
Comment 3 Dave Yost 2014-11-25 23:28:24 UTC
What I'm after is an argument syntax that supports copying to multiple destinations.

It's fine by me if rsync executes a multiple-destination command via multiple, sequential copies.

I am not advocating an incompatible change that would require a --to argument even for a single destination.
Comment 4 Kevin Korb 2014-11-26 00:35:18 UTC
If you want to run them in parallel then use gnu parallel.  It would keep the specified unmber of jobs running until it runs out of new jobs.
Comment 5 Dave Yost 2014-11-26 02:14:59 UTC
This is not about running them in parallel.
Comment 6 Wayne Davison 2020-07-26 08:15:00 UTC
I'd suggest creating a helper script that then does a loop and runs rsync several times.