public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alejandro <elcorreodeale@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] rsync + tar + bz2 ?
Date: Sun, 8 Mar 2009 16:51:44 -0200	[thread overview]
Message-ID: <60a795cd0903081151s4debc1fah213beb8a9f1f127e@mail.gmail.com> (raw)
In-Reply-To: <200903072201.52132.dirk.heinrichs@online.de>

[-- Attachment #1: Type: text/plain, Size: 1303 bytes --]

2009/3/7 Dirk Heinrichs <dirk.heinrichs@online.de>

> Am Samstag, 7. März 2009 21:13:49 schrieb Dirk Heinrichs:
> > Am Samstag, 7. März 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=NUM    explicitly set compression level
            --skip-compress=LIST    skip compressing files with suffix in
LIST

[-- Attachment #2: Type: text/html, Size: 1756 bytes --]

  reply	other threads:[~2009-03-08 18:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-07 16:04 [gentoo-user] rsync + tar + bz2 ? Grant
2009-03-07 17:42 ` Mike Kazantsev
2009-03-07 18:33   ` Grant
2009-03-07 20:13 ` Dirk Heinrichs
2009-03-07 21:01   ` Dirk Heinrichs
2009-03-08 18:51     ` Alejandro [this message]
2009-03-08 21:48 ` Daniel Troeder
2009-03-09 17:03 ` Dirk Heinrichs
2009-03-09 19:14   ` Hung Dang
2009-03-09 19:33     ` Saphirus Sage
2009-03-13  4:01 ` Enrico Weigelt

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=60a795cd0903081151s4debc1fah213beb8a9f1f127e@mail.gmail.com \
    --to=elcorreodeale@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