From: Damon Getsman <dgetsman@amirehab.net>
To: git@vger.kernel.org
Subject: Re: git as backup/DRP; also meta-question about Majordomo
Date: Wed, 4 Mar 2009 11:56:54 -0600 [thread overview]
Message-ID: <274eb6f0903040956t36580a8ayd269f74882724637@mail.gmail.com> (raw)
In-Reply-To: <274eb6f0903040951g27cb4956u1d101c84952d0090@mail.gmail.com>
Hello! :) I've got a couple of questions for y'all.
Q1: First of all, I'm being handed a project whereas I am to find and
implement some sort of backup system across a wide range of various
Linux hosts and a couple of windows machines. This backup system is
to basically be a 'pseudo-TimeVault' if you're familiar with Mac
OS/X's current backup system. I need to be able to roll back to any
particular revision.
A few of my first thoughts were pretty primitive, and included
basically doing periodic compressed tarballs with a rotator to make
sure that I don't run out of available space. These would hold the
commonly changing and most important data while a one time master
backup would hold the system configuration, etc, etc, so that
basically I could create a minimal install on a clone of the same
machine, throw on the master backup, then the most recent data, and
call it done. obviously this is an obtuse method for doing so; it is
also the method that we're trying to get away from as my predecessor
was using an even dumber version of the same scheme.
When I started digging, it seemed that 'svn' or 'git' might work
well, if able to handle binaries, and definitely for systemwide
configuration areas such as /etc. Finding git+etckeeper was a
treasure, especially as I realized that svn wasn't able to hold
anything binary at all. I'm working right now on implementing
etckeeper for system configuration repositories, but this still leaves
a large portion of what I'd like to work with to the 'dumb tarball'
scheme.
Since I've come in today I've run across a few blog articles that
seem to indicate that git + some customization might be able to handle
a larger portion of this for me, thus simplifying what I am trying to
do:
* http://eigenclass.org/hiki/gibak-backup-system-introduction <-
this link is a prime example
Does anybody have any resources or personal tips from utilizations
that they're working with to share? I'd be very much appreciative for
anything that can assist me in finding out exactly what I can deploy
and, obviously, the howtos (if they exist) for such a scheme.
Personal experience in the same areas would be great to hear, too.
Thanks in advance on that one!
Q2: I haven't found any way to tell the 'majordomo' mailing list
software running this list that I am not happy receiving 40-60 emails
in my business email inbox per day. Of course I can use google to
filter them, but I'd still rather just get a daily digest if this is
at all possible. Am I missing something obvious?
TIA again.
----------
Damon Getsman
-=-=-=-
ITRx http://www.itrx-nd.com/
Programmer/IT Customer Relations/Sys Admin
-=-=-=-
next parent reply other threads:[~2009-03-04 17:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <274eb6f0903040951g27cb4956u1d101c84952d0090@mail.gmail.com>
2009-03-04 17:56 ` Damon Getsman [this message]
2009-03-04 19:36 ` git as backup/DRP; also meta-question about Majordomo Jay Soffian
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=274eb6f0903040956t36580a8ayd269f74882724637@mail.gmail.com \
--to=dgetsman@amirehab.net \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).