On 26 February 2010 22:23, Ward Poelmans <wpoel...@gmail.com> wrote: > On Thu, Feb 25, 2010 at 18:50, daid kahl <daid...@gmail.com> wrote: > >> As a simple idea, cron task starts rsnapshot configured however. When >> this is done, backup is tarballed, and tarball is given as like, say, >> 440 permissions, where users are in some useful 'backup' group, then >> while tarball can be read to be passed across server, if tarball is >> extracted, user has no more privs then they have on the system anyway >> (I'm not saying chmod -R). Then local tarball can be removed or >> whatever. > > It's not a bad idea, but you need enough free space on the client to > backup the entire system (which for me is not the case). Secondly, > every backup you do is a full backup as rsnapshot needs to access a > backup todo a incremental backup. You could mess around with something > like sshfs but's it's not great either. A straight rsync between > client and server could do it but it would suprise me if this doesn't > already exist in some form. > > Regards, > > Ward > Thanks for the feedback. For now, as you may easily guess, this case does not apply to me personally since I mostly just admin my own personal machine. But I think you raise very relevant difficulties with my suggestion for a practical administrative case for multiple machines.
~daid
