From: Grant <emailgrant@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] rsync backup system
Date: Fri, 20 Nov 2009 08:05:27 -0800 [thread overview]
Message-ID: <49bf44f10911200805u55dfe4e1j1a7b61928ea568e5@mail.gmail.com> (raw)
In-Reply-To: <20091119172558.45ac3a44@zaphod.digimed.co.uk>
>> 2. Some of the files I back up only allow root to read. I can run
>> rsync as root on each system, but I don't allow root logins. This
>> means in order to rsync the second "sync" system with the first "sync"
>> system, I must run the rsync command from the first "sync" system.
>> This means I have to run rsyncd on the second "sync" system in
>> addition to the first "sync" system. I'd rather only run one instance
>> of rsyncd. Can anyone think of another option?
>
> Allow root logins only with a key, set up a specific user on the backup
> server to run the backup tasks and add that users key to the
> authorized_users file on the machine to be backed up.
>
>> 3. The rsync process always completes with "rsync error: some
>> files/attrs were not transferred". How can I get more information
>> about which files this pertains to?
>
> Run rsync with the verbose option and direct stdout and stderr to files.
>
>> 5. If I end up with filesystem corruption on the SRC system, will that
>> corruption transfer over to the DST system during an rsync, or will
>> the transfer just fail?
>
> If data is corrupted, that will be backed up. If the filesystem
> corruption causes read errors, rsync will bail out.
>
>> 6. Can I run rsyncd on a system facing the internet without fear?
>
> Yes, as long as the rsync ports are closed in your router.
>
> Instead of all this, I'd recommend BackupPC. It handles all of your
> issues and more and is efficient at backing up multiple machines. You
> could run one BackupPC server and then rsync its store to the backup
> backup server. The latest version in portage is old, get the 3.x ebuild
> from bgo.
How is BackupPC to set up? Is it a whole new world to explore, or can
it be set up quickly and easily?
- Grant
next prev parent reply other threads:[~2009-11-20 16:05 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 [this message]
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
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=49bf44f10911200805u55dfe4e1j1a7b61928ea568e5@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