From: Saphirus Sage <saphirus497@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] rsync + tar + bz2 ?
Date: Mon, 09 Mar 2009 15:33:26 -0400 [thread overview]
Message-ID: <49B56F06.2020101@gmail.com> (raw)
In-Reply-To: <49B56AAA.7040205@gmail.com>
Hung Dang wrote:
> Dirk Heinrichs wrote:
>> 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?
>>>
>>
>> Another way, although a bit more work to setup, whould be to use a
>> "Network block device". Unlike NFS, the server just exports the block
>> device, everything else (mkfs, encryption) can be done on the client.
>>
>> Bye...
>>
>> Dirk
>>
> rsync will download only if source and destination files are different.
> From my experiences using rar is faster and save more space than bz2.
>
> Hung
>
But rar is a proprietary archival format, I'd much sooner go with a tar,
compressed with bzip2 or lzma. If the biggest concern is just getting it
done quickly, gzip it, but for the love of all things free, not rar, I say!
next prev parent reply other threads:[~2009-03-09 19:33 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
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 [this message]
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=49B56F06.2020101@gmail.com \
--to=saphirus497@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