RE: SVN overall.. I like the concept of it. SVN is a pretty powerful tool, and when deployed as you propose IMHO seems to provide a great layer of protection for any DR situation. I personally would not change the username/ownership for the transfer. This can cause issues when restoring it that become a nuisance.
RE: remote root issue How remote is your root access over ssh? The root access over ssh can be configured in such a way that battens it down to only allowing connections from your server/host with original data and always requiring a key to login. If the backup host is dedicated to the one server, a separate nic and lan can be setup to keep the traffic private as well. This limits exposure quite a bit. Just some thoughts... -Kevin On Mon, Aug 10, 2009 at 6:01 AM, Robin Wood <[email protected]> wrote: > Hi > I'm looking at different back up solutions for my server and was > thinking about using subversion. I'd add /etc to a repository and have > it automatically checked in every night. I'd have the repo to be on a > different server and to have the svn traffic tunnel over ssh. > > As some files in /etc are only readable by root, the svn check in must > be done by root. As allowing remote ssh access to root is a bad idea > so the repo must be owned by a non-root user on the other box. Seeing > as I'll have to trust something somewhere I'll assume that I trust the > non-root user on the other box. > > Before the check in all new files must be added to the repo as well. > > Does anyone else have this kind of setup and if so, does it work or > can you point out any alternatives or better ways to do things? > > Robin > _______________________________________________ > Pauldotcom mailing list > [email protected] > http://mail.pauldotcom.com/cgi-bin/mailman/listinfo/pauldotcom > Main Web Site: http://pauldotcom.com >
_______________________________________________ Pauldotcom mailing list [email protected] http://mail.pauldotcom.com/cgi-bin/mailman/listinfo/pauldotcom Main Web Site: http://pauldotcom.com
