I usually checkout my configuration for a certain applications, i.e. Asterisk and leave a folder svn/ in the /etc/asterisk directory. I then append the default conf files with .orig and symlink the files in the /etc/asterisk/svn/ direcotry to the /etc/asterisk direcotry. Whenever my configuration improves or i'm about to do something new completely i commit so that i have a snapshot.
This has proven to be a great solution for what to me, to me is one of the harder things to recover after a failure, the configuration file. Other than than that i also use rsync, but i think its worth mentioning that svn is really useful if versioning might be useful to you.
One other thing i've done with svn (although depending on the size of the VM this could take forever) is create file snapshots of my xen vms, either from LVM by dding them to a file or by copying a .disk file, and commiting it. Just make sure you're not making a central point of failure in the process ;)
Hope that was insightful, Dmitry On Aug 10, 2009, at 14:58 , Josh Olson wrote:
On Mon, Aug 10, 2009 at 6:01 AM, Robin Wood<[email protected]> wrote: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, I'm not saying your idea is bad, but I've always liked Jamie Zawinski's idea of rsyncing to a locally attached external disk. One for your nightly backups, and the other (stored remotely) for monthly emergency recovery. http://www.jwz.org/doc/backups.html _______________________________________________ Pauldotcom mailing list [email protected] http://mail.pauldotcom.com/cgi-bin/mailman/listinfo/pauldotcom Main Web Site: http://pauldotcom.com
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ Pauldotcom mailing list [email protected] http://mail.pauldotcom.com/cgi-bin/mailman/listinfo/pauldotcom Main Web Site: http://pauldotcom.com
