From: Konstantin Khomoutov <flatworm@users•sourceforge.net>
To: Eric Frederich <eric.frederich@gmail•com>
Cc: git@vger•kernel.org
Subject: Re: Git as a backup system?
Date: Mon, 8 Nov 2010 21:26:12 +0300 [thread overview]
Message-ID: <20101108212612.bb4bfeb8.kostix@domain007.com> (raw)
In-Reply-To: <AANLkTikcBvN+5hkcc9+xt291B4Gm+Yhe53R3qY0PNt97@mail.gmail.com>
On Mon, 8 Nov 2010 13:01:29 -0500
Eric Frederich <eric.frederich@gmail•com> wrote:
> I maintain a corporate MediaWiki installation.
> Currently I have a cron job that runs daily and tar's up the contents
> of the installation directory and runs a mysqldump.
> I keep backups of the past 45 days.
> Each backup is about 200M, so all in all I always have about 9.0G of
> backups. Most of the changes are in the database, so the mysqldump
> file is changed every day.
> Other than that, there can be new files uploaded but they never
> change, just get added.
> All configuration files stay the same.
[...]
> Am I insane? Are there other tools more suited toward this?
> I just thought of using Git since I looked at my 9G worth of data out
> there in my backup directory that is almost exactly the same and said
> "git could handle this well".
>
> Are any of you using git for a backup system? Have any tips, words
> of wisdom?
I suspect the rdiff-backup tool [1] was invented precisely for the setup
like yours: it is able to sync one directory to another + create diffs
between them thus providing for incremental backups.
1. http://www.nongnu.org/rdiff-backup/
next prev parent reply other threads:[~2010-11-08 18:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-08 18:01 Git as a backup system? Eric Frederich
2010-11-08 18:04 ` Jonathan Nieder
2010-11-08 18:26 ` Konstantin Khomoutov [this message]
2010-11-08 20:06 ` Dirk Süsserott
2010-11-08 20:25 ` Ævar Arnfjörð Bjarmason
2010-11-09 0:17 ` Patrick Rouleau
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=20101108212612.bb4bfeb8.kostix@domain007.com \
--to=flatworm@users$(echo .)sourceforge.net \
--cc=eric.frederich@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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