git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avery Pennarun <apenwarr@gmail.com>
To: "Stephen R. van den Berg" <srb@cuci.nl>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [Announce] bup 0.09: git-based backup system for really huge  datasets
Date: Fri, 12 Feb 2010 12:51:35 -0500	[thread overview]
Message-ID: <32541b131002120951h25368812w547e8dcbaf054fa1@mail.gmail.com> (raw)
In-Reply-To: <20100211135129.GA2988@cuci.nl>

On Thu, Feb 11, 2010 at 8:51 AM, Stephen R. van den Berg <srb@cuci.nl> wrote:
> Avery Pennarun wrote:
>>bup is a file backup tool based on the git packfile format.  If you're
>>interested in git, you might find bup interesting because:
>
> Interesting concept.  It has some killer features which make it a good
> competitor to any of the existing solutions.
> The only obvious thing missing for unattended backup-operation is a way
> to purge specific or old backups.

Thanks.  Oddly enough, pruning of old backups hasn't been a really
high priority for me (or apparently any of the other users) because
chunking-based deduplication is so efficient that my backup disk
hasn't filled up yet :)  But it's clear that this will need to be
added eventually.

Unfortunately git's normal pruning and gc stuff is inapplicable since
it dies horribly when faced with hundreds of gigabytes of data.
That's to be expected, but it means I can't just cheat by running 'git
gc' and hoping for magic.

Have fun,

Avery

      reply	other threads:[~2010-02-12 17:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-09 22:48 [Announce] bup 0.09: git-based backup system for really huge datasets Avery Pennarun
2010-02-10  9:54 ` Jakub Narebski
2010-02-10 20:01   ` Avery Pennarun
2010-02-11 13:51 ` Stephen R. van den Berg
2010-02-12 17:51   ` Avery Pennarun [this message]

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=32541b131002120951h25368812w547e8dcbaf054fa1@mail.gmail.com \
    --to=apenwarr@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=srb@cuci.nl \
    /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;
as well as URLs for NNTP newsgroup(s).