From: Grant <emailgrant@gmail.com>
To: Gentoo mailing list <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] Finalizing my backup system
Date: Sun, 26 Sep 2010 12:13:58 -0700 [thread overview]
Message-ID: <AANLkTin2+_h46soxFm7=LuvcSPOC2VFHQ1RzOuCzw-Rx@mail.gmail.com> (raw)
I'm using backupninja to backup data from my laptop, desktop, and
remote server onto a remote desktop system. backupninja is very
simple and is really just an interface to a few other programs
including rdiff-backup. I'm not worried about a good restore method
for now, I want to focus on keeping it simple and protecting my data.
This is the first time I've set up a real backup system and I'd love
to get some advice from you guys. I've got a few questions.
1. This is the first time I've used passwordless SSH keys. root on
each system being backed up logs into the remote desktop as a normal
user to store the backups. Is this pretty safe? I suppose if root is
compromised on any of the three systems being backed up (via physical
access or otherwise), the remote desktop will also be compromised as a
normal user. Maybe that normal user should be extraordinarily
unprivileged?
2. backupninja can email reports. This works on my remote server
which runs postfix, but my laptop and desktop don't run an MTA. Is
there a simple one that would be well-suited to a purpose like this,
or do I need full-blown postfix on my laptop and desktop? Whatever I
choose, I'd also like to use it to send PORTAGE_ELOG messages from
those systems.
3. On each system I back up /etc, /home/user/backup,
/var/lib/portage/world, and /usr/src/linux/.config along with anything
special from that system. Would anyone recommend I back up anything
else? Some of the hidden directories in /home/user might come in
handy, but I think I can rebuild those without too much trouble.
4. I have 600GB of music and photos that I'd like to back up somehow,
but that is too much data to send to my remote desktop over my 20KB/s
upload. How would you handle this? I was thinking maybe two external
USB drives that I switch back and forth between being connected to the
desktop system and being stored in a fireproof/waterproof container
and hidden somewhere in my apartment to hopefully protect against
fire, flood, and theft.
5. Do I have enough redundancy with backups only being stored on one system?
6. Any ideas for backing up the remote desktop which is the system
where all the backups are stored? I can't back it up to my desktop or
laptop because I'm behind some kind of a shared IP address. I also
don't want to back it up to the remote server because that would
require SSH keys on the remote server and if the remote desktop is
compromised I don't want the remote server compromised along with it.
Thanks guys,
Grant
next reply other threads:[~2010-09-26 19:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-26 19:13 Grant [this message]
2010-09-26 20:07 ` [gentoo-user] Re: Finalizing my backup system walt
2010-09-26 21:58 ` [gentoo-user] " Michael Orlitzky
2010-10-06 17:40 ` Grant
2010-10-06 19:46 ` Michael Orlitzky
2010-10-06 21:43 ` Grant
2010-10-07 1:45 ` Michael Orlitzky
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='AANLkTin2+_h46soxFm7=LuvcSPOC2VFHQ1RzOuCzw-Rx@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