public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Best way to copy /* ?
Date: Wed, 29 Dec 2010 19:16:05 +0000	[thread overview]
Message-ID: <201012291916.17450.michaelkintzios@gmail.com> (raw)
In-Reply-To: <201012291941.00611.wonko@wonkology.org>

[-- Attachment #1: Type: Text/Plain, Size: 1495 bytes --]

On Wednesday 29 December 2010 18:41:00 Alex Schuster wrote:
> Peter Humphrey writes:
> > On Wednesday 29 December 2010 17:50:08 Alex Schuster wrote:
> > > What Maciej said. Or, for greater security when the destination is
> > > outside the LAN:
> > > 
> > > cd [source] & tar xpf - . | ssh [user]@[host] 'cd [dest] && tar xpf
> > > -'
> > 
> > That's what I was looking for - a single command I can run on the source
> > machine. Thanks Alex.
> > 
> > Just one more thing - what if I only want to store the tar of the source
> > directory as an archive on the remote machine? In that case I'd want to
> > stream the incoming data into a file instead of untarring it.
> 
> Replace the tar by cat, and redirect into a file:
> 
> cd [source] & tar xpf - . | ssh [user]@[host] 'cat > [dest]/[name].tar'

The front part should be tar -cpf not -xpf?

Also, option -S manages sparse files more efficiently.

Finally, if it is a large archive and is going to travel over a slow network 
it would make sense to compress it first locally into a tar file (e.g. using -
j) then verify it (if it is important data that you rely on just add -W) and 
finally ssh the compressed tar file over.

If you are going to use pipes, then dd will also work instead of cat; i.e.

 cd [source] & tar cpvSf - . | ssh [user]@[host] "dd 
of=/backup_storage/mydata.tar.bz2"

I don't think that dd is any different to cat in performance terms (but 
haven't tested it).
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-12-29 19:17 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-27 15:20 [gentoo-user] Best way to copy /* ? Marc Blumentritt
2010-12-27 15:20 ` Etaoin Shrdlu
2010-12-27 16:37   ` Neil Bothwick
2010-12-27 16:52     ` Mark Knecht
2010-12-27 17:05       ` [gentoo-user] " Remy Blank
2010-12-27 20:26         ` Marc Blumentritt
2010-12-27 21:23           ` Remy Blank
2010-12-28  8:56             ` Marc Blumentritt
2010-12-28  9:18               ` Remy Blank
2010-12-28 10:49                 ` Neil Bothwick
2010-12-27 15:30 ` [gentoo-user] " ich bins
2010-12-27 15:34 ` [gentoo-user] " Lubos Kolouch
2010-12-27 15:41 ` [gentoo-user] " Jarry
2010-12-27 15:47 ` Dale
2010-12-29 17:03   ` Peter Humphrey
2010-12-29 17:14     ` Maciej Grela
2010-12-29 17:43       ` Paul Hartman
2010-12-29 17:50     ` Alex Schuster
2010-12-29 18:30       ` Peter Humphrey
2010-12-29 18:41         ` Alex Schuster
2010-12-29 19:16           ` Mick [this message]
2010-12-29 20:24             ` Stefan G. Weichinger
2010-12-27 17:27 ` Volker Armin Hemmann
2010-12-27 17:38   ` Mark Knecht
2010-12-27 17:51     ` Volker Armin Hemmann
2010-12-27 18:01       ` Mark Knecht
2010-12-27 17:45   ` Dale
2010-12-27 18:45     ` Neil Bothwick
2010-12-27 21:35       ` Dale
2010-12-28  5:02 ` Mike Edenfield
2010-12-28 13:20   ` Alex Schuster
2010-12-28 13:32   ` Neil Bothwick
2010-12-28 16:26     ` Joerg Schilling
2010-12-28 18:41       ` Mick
2010-12-29 15:38         ` Joerg Schilling
2010-12-29 16:17           ` Mick
2010-12-28 22:33       ` Neil Bothwick
2010-12-28 23:16         ` Mick
2010-12-28 23:36         ` Joerg Schilling
2010-12-29  0:51           ` Alex Schuster
2010-12-28 23:08       ` Alex Schuster
2010-12-29 14:40 ` [gentoo-user] Re: Best way to copy /* ? [SOLVED] Marc Blumentritt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201012291916.17450.michaelkintzios@gmail.com \
    --to=michaelkintzios@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox