public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: daid kahl <daidxor@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] rsync backup system
Date: Sat, 27 Feb 2010 02:33:49 +0900	[thread overview]
Message-ID: <3ac129341002260933l283bc7ffg3825792302d95f99@mail.gmail.com> (raw)
In-Reply-To: <c1c10dab1002260523h7ca2a09m8b9e4547ca1f7aa1@mail.gmail.com>

On 26 February 2010 22:23, Ward Poelmans <wpoely86@gmail.com> wrote:
> On Thu, Feb 25, 2010 at 18:50, daid kahl <daidxor@gmail.com> wrote:
>
>> As a simple idea, cron task starts rsnapshot configured however.  When
>> this is done, backup is tarballed, and tarball is given as like, say,
>> 440 permissions, where users are in some useful 'backup' group, then
>> while tarball can be read to be passed across server, if tarball is
>> extracted, user has no more privs then they have on the system anyway
>> (I'm not saying chmod -R).  Then local tarball can be removed or
>> whatever.
>
> It's not a bad idea, but you need enough free space on the client to
> backup the entire system (which for me is not the case). Secondly,
> every backup you do is a full backup as rsnapshot needs to access a
> backup todo a incremental backup. You could mess around with something
> like sshfs but's it's not great either. A straight rsync between
> client and server could do it but it would suprise me if this doesn't
> already exist in some form.
>
> Regards,
>
> Ward
>
Thanks for the feedback.  For now, as you may easily guess, this case
does not apply to me personally since I mostly just admin my own
personal machine.  But I think you raise very relevant difficulties
with my suggestion for a practical administrative case for multiple
machines.

~daid



  reply	other threads:[~2010-02-26 17:34 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-19 16:44 [gentoo-user] rsync backup system Grant
2009-11-19 17:25 ` Neil Bothwick
2009-11-19 18:19   ` Grant
2009-11-20 17:05     ` Ward Poelmans
2009-11-20 16:05   ` Grant
2009-11-20 22:08     ` Neil Bothwick
2010-02-24 19:02       ` Grant
2010-02-24 20:51         ` Neil Bothwick
2010-02-25 15:15           ` Ward Poelmans
2010-02-25 15:41             ` Alan McKinnon
2010-02-25 16:11               ` Ward Poelmans
2010-02-25 17:50                 ` daid kahl
2010-02-26 13:23                   ` Ward Poelmans
2010-02-26 17:33                     ` daid kahl [this message]
2010-02-25 17:52                 ` Grant
2010-03-17 15:33                 ` Ward Poelmans
2010-02-25 17:45               ` Neil Bothwick
2010-02-25 16:06             ` Neil Bothwick
2009-11-19 17:58 ` Albert Hopkins
2009-11-19 18:18   ` Albert Hopkins
2009-11-20 16:03     ` Grant
2009-11-20 17:31       ` Albert Hopkins

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=3ac129341002260933l283bc7ffg3825792302d95f99@mail.gmail.com \
    --to=daidxor@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