Resume aborted scp file transfers

rsync --partial --progress --rsh=ssh SOURCE DESTINATION
Put it into your sh startup script (I use alias scpresume='rsync --partial --progress --rsh=ssh' in bash). When a file transfer via scp has aborted, just use scpresume instead of scp and rsync will copy only the parts of the file that haven't yet been transmitted.
Sample Output
scp file user@somehost:/path
... aborted

scpresume file user@somehost:/path
... resume from  where we left off before

14
By: episodeiv
2009-02-16 16:22:10

What Others Think

good tip, but rsync -P SOURCE DESTINATION is shorter (modern rsyncs default to ssh)
ger · 499 weeks and 1 day ago
What about resuming a recursive transfer of thousands of files when after the first thousand, it was interrupted?
vgm64 · 493 weeks and 1 day ago
i think the best option would be rsync -aP SOURCE DESTINATION to preserve timestamp, user and group, continue, if copy is aborted and go recursively into directories: -a, --archive archive mode; equals -rlptgoD (no -H,-A,-X) -r, --recursive recurse into directories -d, --dirs transfer directories without recursing -l, --links copy symlinks as symlinks -p, --perms preserve permissions -o, --owner preserve owner (super-user only) -g, --group preserve group --devices preserve device files (super-user only) --specials preserve special files -D same as --devices --specials -t, --times preserve modification times --partial keep partially transferred files --progress show progress during transfer -P same as --partial --progress @ vgm64: i thought, thats the "--partial" for
rubo77 · 473 weeks ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Share Your Commands



Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for: