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: Fri, 26 Feb 2010 02:50:08 +0900	[thread overview]
Message-ID: <3ac129341002250950h376f57d5y241e6efeb7080b20@mail.gmail.com> (raw)
In-Reply-To: <c1c10dab1002250811s18358bb0te145e05d494181@mail.gmail.com>

On 26 February 2010 01:11, Ward Poelmans <wpoely86@gmail.com> wrote:
> On Thu, Feb 25, 2010 at 16:41, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
>> A much better way is to run a dedicated agent on the client. If the server
>> needs to schedule backups, it can ask the agent to do so using regular tcp
>> traffic. The client can then do it's backup and rsync it over to the server
>> when it's done, and that push can be done as a regular user on both ends. The
>> actual backing up on the client must be done by root of course, no other user
>> has the necessary access.
>
> Sounds great. Is there any software that works this way?
>
> Ward

Sounds more or less like cron tasks and rsnapshot to me (can use other
rsync scripts of course, but this one is nice to me anyway, and
someone else mentioned it earlier in the thread).  I'm not sure off
hand I have a good way for it to be initialized from the server end,
but if it's a backup, it might as well run on a local cron anyway
rather than needing an external call.

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.

And call me silly for not reading documentation or assuming, but I was
very happy last night when I realized system rescue CD includes
rsnapshot already!

~daid



  reply	other threads:[~2010-02-25 18:16 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 [this message]
2010-02-26 13:23                   ` Ward Poelmans
2010-02-26 17:33                     ` daid kahl
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=3ac129341002250950h376f57d5y241e6efeb7080b20@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