Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 2 Aug 2006 03:16:26 -0500
From:      "Nikolas Britton" <nikolas.britton@gmail.com>
To:        "John Nielsen" <lists@jnielsen.net>
Cc:        David Banning <david+dated+1154886729.6e1beb@skytracker.ca>, freebsd-questions@freebsd.org
Subject:   Re: best way to copy from one fbsd box to another
Message-ID:  <ef10de9a0608020116u4e9e1b66p3b6cd2fa0394ce3c@mail.gmail.com>
In-Reply-To: <200608011431.09443.lists@jnielsen.net>
References:  <20060801175209.GA24100@skytracker.ca> <20060801140433.f27bb1cb.wmoran@collaborativefusion.com> <200608011431.09443.lists@jnielsen.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On 8/1/06, John Nielsen <lists@jnielsen.net> wrote:
> On Tuesday 01 August 2006 14:04, Bill Moran wrote:
> > In response to David Banning <david+dated+1154886729.6e1beb@skytracker.ca>:
> > > I am installing a new server and have to copy many files from old server
> > > to new. I have connected a windows box to each via samba, and am dragging
> > > from one to the other via the windows box.
> > >
> > > This might seem like a silly question, but what is the way to copy
> > > -directly- from one fbsd box to another?
> >
> > Usually NFS or scp.  There are other choices, though.
>
> For many situations my favorite is tar+netcat (w/ optional bzip2 compression).
>
> On the destination host:
>         cd /some/path
>         nc -l 1234 | tar -xjvf -
>
> And on the source host:
>         cd /some/path
>         tar -cjvf - relative/path/to/source/dir | nc destip 1234
>
> If you don't want compression leave out the 'j' flag in both calls to tar.
>
> scp is your best bet if you need encryption though (take note of the -r and -C
> flags).
>

I'll 2nd netcat... one of the most versatile tool I've come across in
UNIX land!

http://www.securitydocs.com/library/3376
http://www.rajeevnet.com/hacks_hints/os_clone/os_cloning.html
http://www.stearns.org/doc/nc-intro.current.html

One thing I'd like to add to Johns comment is to not use compression
if your on a GigE network, The overhead required to do this will max
out the CPU, the net effect being very slow transfer rates. It also
helps to not use tar -v, you will miss error messages if you use -v
because the SNR is very low, it consumes CPU time too.


-- 
BSD Podcasts @:
http://bsdtalk.blogspot.com/
http://freebsdforall.blogspot.com/



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ef10de9a0608020116u4e9e1b66p3b6cd2fa0394ce3c>