[TriLUG] Pony request: Backup Solution

[jason tower]

because with rsyncd i can set up a "user" in rsync.conf for each host, 
chroot them to /backups/$USER/, and chown the resulting files to any uid 
to match the source (gotta preserve ownership).  with ssh as the rsync 
transport i'd have to a) create a local unix user which is undesirable 
and b) that user couldn't chown files.

and this has to be a push system since most of the hosts that we want to 
back up are behind firewalls - they can get out but we can't get in 
(without a lot of firewall trickery).

jason

Matt Pusateri wrote:
> rsnapshot rocks!
> 
> Give us more info:
> 
> 1. Why don't you want to use ssh?,  What transport mechanism do you want 
> to use?
> 2. Why do you want to use rsyncd?
> 
> rsnapshot seems to all your other needs mentioned.  rsnapshot will work 
> with scripts, so you might be able to script around your needs, but for 
> the most part it's a pull method over ssh.
> 
> I can probably give some info of how I implemented it at $work.
> 
> Matt P.
> 
> 
> John Broome wrote:
>> I've been looking at all of the rsync-based backup programs and I
>> haven't found one that does exactly what I need.
>>
>> Here's the wish list:
>>
>> Works with rsyncd, i don't want to use ssh for the transport.
>> I'd like to push the backups offsite.
>> Incremental backups with hard links to save space
>> Backups are kept as live files instead of .tar or .gz
>>
>> I really like rsnapshot, but i haven't seen how to get it to work with rsyncd.
>>
>> I'm open to any suggestions, thanks trilug!
>>
>>   
>