Create a local compressed tarball from remote host directory

ssh user@host "tar -zcf - /path/to/dir" > dir.tar.gz
This improves on #9892 by compressing the directory on the remote machine so that the amount of data transferred over the network is much smaller. The command uses ssh(1) to get to a remote host, uses tar(1) to archive and compress a remote directory, prints the result to STDOUT, which is written to a local file. In other words, we are archiving and compressing a remote directory to our local box.

By: __
2011-12-16 05:48:38

3 Alternatives + Submit Alt

What Others Think

Both solutions get the same result, but the firstone tries to minimize the bandwith usage, which should be an advantage at a slow network connection. The price fro that ist to squeeze out the cpu performance in two ways: ssh encryption and compressing. The second solution needs more bandwith but use less cpu power, because the local host will compress the tarfile. As often this is a tradeof between networkbandwith and cpu power. It depends also on the content of the tarfile, if it's compressable or not. So there is no "better" alternative in any situation at least for me.
f4m8 · 550 weeks ago
Definitely another way to get at the same result. However, OpenSSH (and other SSH implementations) support compression in the SSH connection. So, you can get the benefit of not burning the remote CPU (although you're using compression for the connection, you're not for both the connection and the archive simultaneously), and still minimize data transferred on the wire. Either way works.
atoponce · 550 weeks ago ????? ??? ????? ???? SEO ????? ????? ????? ???? ????? ????? ??? ???? ???? ??????? Search Engine Optimization ??? ????? ??????????? ?? ????? ?????????? ????? ????? ?? ????
seofox · 21 weeks and 5 days ago
seofox · 20 weeks and 3 days 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? 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.


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: