Well, now that I've got my systems cleaned up, and KDE3 removed, I'm tackling
another project I've been meaning to do - backups.
Here's my basic plan:
- I've got a directory on my server that I want to synchronize several systems
with (some linux, and one Windows).
- I want clients to push the backup; and not the server to pull it.
- Clients may backup more than once a month.
- the server will receive an additional backup itself once a month which
includes all the client backups (may be more often, not sure).
At least on the Linux Systems, I've settled to using rsync for the backup -
easy enough to do. I'm already running an rsync server for hosting portage, so
it's relatively trivial to add another rsync module to support that way, though
I'm not sure what the best way is.
rsync in attractive since it will do delta transfers to keep things in sync;
though if I could use scp the same way I probably would since I would just have
to setup appropriate keys.
Any how...I setup the rsync daemon with a read-write section. Tested it, and it
worked. But I'd really like to have it secured - I don't want anyone to be able
to read/write to it. So I tried adding the following:
[backup]
uid = <backup user>
gid = <backup group>
path = /path/to/backup/repo
read only = false
list = false
auth users = <user>
secrets file = /path/to/rsyncd.secrets
The rsyncd.secrets is simple:
<user>:<8 digit password>
If I don't have the last two lines (e.g. auth user, secrets file) then I can
write to it.
Otherwise I get an authentication error:
@ERROR: auth failed on module backup
rsync error: error starting client-server protocol (code 5) at main.c(1503)
[sender=3.0.6]
I'm uploading via:
rsync -a --password-file=rsync.passwd someTestFile
rsync://<user>@host/backup/extra/path/
rsync.passwd contains the same <8 digit password>, nothing else.
I've already checked file permissions - the entire directory structure under
/path/to/backup/repo is owned by <backup user>:<backup group>.
What am I doing wrong?
Is there a better approach?
TIA,
Ben
