From: Grant <emailgrant@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] {OT} rdiff-backup: push or pull?
Date: Tue, 16 Aug 2011 16:50:40 -0700 [thread overview]
Message-ID: <CAN0CFw1q-GJEVMUPjzOpYYPwu+COt4j_nRX+MiOHOdoDuc8AFg@mail.gmail.com> (raw)
In-Reply-To: <54732072.QyOj10dyxT@eve>
>> I'm setting up an automated rdiff-backup system and I'm stuck between
>> pushing the backups to the backup server, and pulling the backups to
>> the backup server. If I push, I have to allow read/write access of my
>> backups via SSH keys. If I pull, I have to enable root logins on each
>> system to be backed-up, allow root read access of each system via SSH
>> keys, and I have to deal with openvpn or ssh -R so my laptop can back
>> up from behind foreign routers. The conventional wisdom online seems
>> to indicate pulling is better, but pushing seems like it might be
>> better to me. Do you push or pull?
>
> I would push, to be honest.
Me too. The rdiff-backup "UnattendedRdiff" wiki page only has
instructions for pulling but that doesn't seem like the way to go:
http://wiki.rdiff-backup.org/wiki/index.php/UnattendedRdiff
> You can seperate the backups by giving each system a different account where
> to store the backups.
I'm not sure what you mean. The backups are all stored on the backup server.
> This way you can also have better control over when to do the backup. If your
> laptop hooks up via VPN just to quickly check email over an expensive or slow
> link, you might not want the backup to start downloading all the pictures you
> took during the holiday or that 300-page manuscript you wrote for your book.
>
> --
> Joost
Here's what I'm doing. root on 3 machines pushes to non-root on a 4th
machine via rdiff-backup and SSH keys. The SSH keys are restricted
like so (although there is no from= for the laptop's key since it
could be behind any IP):
command="rdiff-backup
--server",from="12.34.56.78",no-port-forwarding,no-X11-forwarding,no-pty
ssh-rsa ... root@machine1
Is this a good arrangement? I think the worst-case scenario
(compromised SSH keys) is read/write access of the non-root user on
the backup server via rdiff-backup.
Additionally, the backups on the 4th machine are pushed to another
machine by root to non-root via rsync and SSH keys. Is there a way to
restrict SSH keys to the rsync command?
Should the non-root backup user have any special configuration?
Can I reserve 0% for root on my USB hard drive which is only used for
backups and does not contain an OS?
- Grant
next prev parent reply other threads:[~2011-08-16 23:51 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-16 4:58 [gentoo-user] {OT} rdiff-backup: push or pull? Grant
2011-08-16 6:35 ` Joost Roeleveld
2011-08-16 23:50 ` Grant [this message]
2011-08-17 6:07 ` Joost Roeleveld
2011-08-17 17:18 ` Grant
2011-08-18 6:13 ` Joost Roeleveld
2011-08-19 1:01 ` Grant
2011-08-19 6:07 ` Joost Roeleveld
2011-08-19 17:13 ` Grant
2011-08-17 6:14 ` Joost Roeleveld
2011-08-17 17:35 ` Grant
2011-08-19 17:14 ` Michael Orlitzky
2011-08-19 18:00 ` Grant
2011-08-19 19:06 ` Michael Orlitzky
2011-08-19 19:58 ` Grant
2011-08-20 8:12 ` Alan McKinnon
2011-08-17 6:15 ` Joost Roeleveld
2011-08-17 17:37 ` Grant
2011-08-17 18:54 ` Alex Schuster
2011-08-17 20:47 ` Grant
2011-08-17 21:49 ` Alex Schuster
2011-08-17 22:03 ` Alan McKinnon
2011-08-18 0:35 ` Peter Humphrey
2011-08-18 6:30 ` Joost Roeleveld
2011-08-19 1:51 ` Grant
2011-08-19 6:13 ` Joost Roeleveld
2011-08-19 17:35 ` Grant
2011-08-21 19:10 ` Joost Roeleveld
2011-08-16 13:39 ` Bill Longman
2011-08-16 14:04 ` Alan McKinnon
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=CAN0CFw1q-GJEVMUPjzOpYYPwu+COt4j_nRX+MiOHOdoDuc8AFg@mail.gmail.com \
--to=emailgrant@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