From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1LgO6E-0008Nb-Ua for garchives@archives.gentoo.org; Sun, 08 Mar 2009 18:51:47 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DE27FE0789; Sun, 8 Mar 2009 18:51:45 +0000 (UTC) Received: from mail-ew0-f173.google.com (mail-ew0-f173.google.com [209.85.219.173]) by pigeon.gentoo.org (Postfix) with ESMTP id 80D48E0789 for ; Sun, 8 Mar 2009 18:51:45 +0000 (UTC) Received: by ewy21 with SMTP id 21so551825ewy.34 for ; Sun, 08 Mar 2009 11:51:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=3cDHAbIhHIUltECgrfrcbMhobpz0kUGOnny8Sjzv3/A=; b=o7eockp8w6U7FE7lWzJ0id9E87kqdDnQYN6aRKbOVhf4pQoIg2NE4ZBU4Os9jECMWR rL08qFluZMHPAFDZ/eoEAj/oI8bq4x4hJX+WQOPesietE7U1xCbCuLk8u5a8XW+vfEJi fUnFXAJi/eEwmQcQgnoXzog5gP+qPHnIkOnqQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=ot8ZL1yYxkRgpx3drIMzrjSvIH66WfX3k0wg7XoBg5ukyXRHi1ZixAirJotRdyTp2x 2t4pWKEK4R5MWZem2tWmbMJq29I4CE3SE7ALa4GEtz8Ck6aZIzehoKH21gefyhXmX15O H9t0FJRLefSG8PGH5ZRuxG34J3Ta9oCv6NRN0= Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.210.88.3 with SMTP id l3mr2977019ebb.11.1236538304942; Sun, 08 Mar 2009 11:51:44 -0700 (PDT) In-Reply-To: <200903072201.52132.dirk.heinrichs@online.de> References: <49bf44f10903070804h585ffd1agdd88f75bb4c9310@mail.gmail.com> <200903072113.54820.dirk.heinrichs@online.de> <200903072201.52132.dirk.heinrichs@online.de> Date: Sun, 8 Mar 2009 16:51:44 -0200 Message-ID: <60a795cd0903081151s4debc1fah213beb8a9f1f127e@mail.gmail.com> Subject: Re: [gentoo-user] rsync + tar + bz2 ? From: Alejandro To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary=0015174bf1dc6ad2430464a0027b X-Archives-Salt: 83f4597d-572e-4810-9fcb-6956581e767b X-Archives-Hash: 01a04c289ce96e5cf281e0da600ade2f --0015174bf1dc6ad2430464a0027b Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 2009/3/7 Dirk Heinrichs > Am Samstag, 7. M=E4rz 2009 21:13:49 schrieb Dirk Heinrichs: > > Am Samstag, 7. M=E4rz 2009 17:04:17 schrieb Grant: > > > I'm backing up numerous large files on another machine on my local > > > network. I've only been using rsync, but it occured to me that I > > > might be able to save some time and space if I incorporate tar and > > > bzip2. How will rsync interact with those? If I turn the whole > > > backup into a big tar.bz2, would rsync need to redownload the whole > > > thing if I change one file? If so, maybe I should turn different > > > groups of files into tar.bz2 archives so rsync only needs to > > > redownload an archive if one of its files has changed? > > > > By using either rsh or ssh, tar can backup over the net, too. > > OTOH, I think rsync is still the better solution, because even for large > files, > it only sends the deltas. But in the end, you will be doing some time > measurements to find the best solution, anyway ;-) > > Bye... > > Dirk > rsync -z -z, --compress compress file data during the transfer --compress-level=3DNUM explicitly set compression level --skip-compress=3DLIST skip compressing files with suffix in LIST --0015174bf1dc6ad2430464a0027b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

2009/3/7 Dirk Heinrichs <dirk.heinrichs@online.de<= /a>>
Am Samstag, 7. M=E4rz 2009 21:13:49 schrieb Dirk Heinrichs:
> Am Samstag, 7. M=E4rz 2009 17:04:17 = schrieb Grant:
> > I'm backing up numerous large files on another machine on my = local
> > network. =A0I've only been using rsync, but it occured to me = that I
> > might be able to save some time and space if I incorporate tar an= d
> > bzip2. =A0How will rsync interact with those? =A0If I turn the wh= ole
> > backup into a big tar.bz2, would rsync need to redownload the who= le
> > thing if I change one file? =A0If so, maybe I should turn differe= nt
> > groups of files into tar.bz2 archives so rsync only needs to
> > redownload an archive if one of its files has changed?
>
> By using either rsh or ssh, tar can backup over the net, too.

OTOH, I think rsync is still the better solution, because even = for large files,
it only sends the deltas. But in the end, you will be doing some time
measurements to find the best solution, anyway ;-)

Bye...

=A0 =A0 =A0 =A0Dirk

rsync -z

=A0=A0=A0=A0=A0=A0=A0 -z, --c= ompress=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 compress file data during th= e transfer
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 --compress-level=3DNUM=A0= =A0=A0 explicitly set compression level
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0 --skip-compress=3DLIST=A0=A0=A0 skip compressing files with suffix in L= IST

--0015174bf1dc6ad2430464a0027b--