public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ward Poelmans <wpoely86@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] rsync backup system
Date: Wed, 17 Mar 2010 16:33:38 +0100	[thread overview]
Message-ID: <c1c10dab1003170833i6588ae88g308612b9ec25748b@mail.gmail.com> (raw)
In-Reply-To: <c1c10dab1002250811s18358bb0te145e05d494181@mail.gmail.com>

On Thu, Feb 25, 2010 at 17: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.

If anyone is still interested, i had some time and this is what i did:

On the client:
rsync -a -X -b --backup-dir=../backup.0/ --link-dest=../backup.0/
/home/ward backupserver:Backup-Laptop/backup.cur/
ssh backupserver /home/ward/shiftbackups.sh

This makes a directory backup.cur on the backupserver with a full
backup in it, but it's exactly only a incremental backup as it
hardlinks from backup.0 (the previous backup). The script
shiftbackups.sh moves backup.0 to backup.1 and backup.cur to backup.0
and so on...

This does more or less exactly what i wanted.

Regards,

Ward



  parent reply	other threads:[~2010-03-17 15: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
2010-02-25 17:52                 ` Grant
2010-03-17 15:33                 ` Ward Poelmans [this message]
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=c1c10dab1003170833i6588ae88g308612b9ec25748b@mail.gmail.com \
    --to=wpoely86@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